Beautiful. Love it Such a thorough explanation of why AGI is not here, and organized in such a way that I can easily share with colleagues when hype interferes with reason. A comment I once saw (on Twitter) was that, we don't need AI to actually do these things, we just need it to be convincing enough to be useful (i.e. Turing test you already mentioned, but rates against each item you listed). Do you think a "convincing enough" AGI is in the future?

Interesting. Would love to hear your perspective on how engineers can add value in light of AI becoming more advanced over time.

This is so cool!!! I was introduced to the concept of honeypots at an internship at a tax software company - I just think the concept of studying your attackers is so fascinating. I don't work in this field, but it seems so fascinating - it would be cool to get a future update to see if you've had any attacks and information you were able to learn about them!

Interesting, thanks for sharing! While I personally feel more comfortable learning by writing code myself, I'm excited about using tools like Copilot for rubber ducking. I can see it allowing me to work more independently, and allowing more senior engineers on my team to do more focused work (without me always asking for help in reviewing my code).

Thanks for reading!

Hey, Brian - thanks for reading, and congratulations on getting close to the finish line!

Thanks, Serdar! I used to be a "my way is the right way" person, but over time I realized my way was the right way for me because of my unique strengths and experiences. For example, a bootcamp wasn't right for me but I know quite a few people who found great career success through bootcamps. They were able to succeed in ways my strengths weren't suited for, and that's great! Thanks for reading!

Of course! I'm also new to the field, so your blog post interested me :-)

Oh interesting - never realized git uses LCS to find differences, but it totally makes sense.

This sounds like a very interesting way of jumpstarting a software engineering immersive. My number one takeaway is to take one incredibly small step at a time and test that step before I move on. Right now, I'm at year 4 of my software engineering program, and even now I have to remind myself of this. I think it's great that you're learning this lessons firsthand now!