It’s been more than a decade since I started writing blogs. Small snippets of code I tried out, turned into blogs. I myself depended on so many sources (including blogs) on the web, so this became both a learning and giving back opportunity for me. Over the years I have hosted my site on Godaddy’s WordPress platform to now managing on AWS Lightsail. It’s definitely been a fun ride. But everything good must have its end or more precisely in this case, a rebirth.
Finding time over a busy work-life schedule has meant less time to research and publish. That is definitely a contributing factor. But the more important reason is AI. AI is your new tutor that can teach you pretty much any topic under the sun. With AI, it’s just a few clicks away to find answers, to research things, to ask stupid questions, to learn how to code (or not now), and so many things. Hallucinations aside, its absolutely true that each of us has our own personal tutor. All you need is a reason to learn.
You want to write a hello world in a new language, spin up Claude and type away “Write me a beginners getting started hello world code sample with C++. Explain the basics and give me clear instructions to setup my environment and run this” . I tried this on Claude of course 🙂 .
Learning has never been easier. If you have a question or need to learn something your own teacher is available 24×7. Since I am in the software engineering space, I will focus on that vs learning about Napoleon or writing poems using AI.
So does the human touch for learning go away. I do not think so. Our abstractions change once again. Instead of code being the focus, we step a level up and instead focus on the problem statement. Good system design is even more important now vs speed to write code. Today if you are an engineer with an architect (from problem formulation to system design to observability) and product mindset, then you are better prepared to build products in this new era.
I do feel that with AI the abstractions will keep moving up faster, eventually reaching a point where there will be Bot Builders that have all the information on what a good enough system design will be for different classes of problems, and given the product ask it can generate the entire system, deploy it , operate it and even have an automated feedback loop back into the pipeline. These Bots will know all about the well-architected architecture principles and know how to spin up a safe environments for your level of availability needs (99 vs 99.9 vs 99.99).
There are already early pieces of this puzzle. On the build side, tools like Lovable, Replit and Bolt can take a prompt and give you a deployed app. On the ops side, agents like Azure SRE Agent, AWS DevOps Agent and PagerDuty’s SRE Agent are starting to triage, and in some cases fix, production incidents. But these are separate islands today, and most teams still need a human approving the risky stuff. Maturity and wide-spread adoption is lagging IMHO — but it feels like a matter of when, not if.
If abstractions keep moving up and code gets cheap, the scarce thing becomes human judgment –Â knowing which trade-off to make, and what breaks when you get it wrong. Additionally, the journey to reinvent ourselves for this new era is also a very human challenge for each of us.
So where does this leave me and my blog? I need to give the future format some more thought, but moving forward I want to lean into sharing personal experiences rather than coding tutorials — some of this I have already started doing. Between that and growing my fledgling new podcast, there’s plenty on the horizon. Signing out for the year—see you on the other side of 2026!