Hi ππ», I wrote this article this weekend where I discuss many questions we hit today as software engineers. If you love reading random tech articles, do share your feedback in the comments here https://t.co/iRvgKMeZfc
I have been freelancing for years now; there is still a lot to learn, and one thing I can tell you in the AI era is that you weren't paid for the code.
Clients I worked with tried to hire me for the product I would build. They loved working on their business, not the software.
Because software was not just about writing code. It was about debugging, integration, security, testing, deployment, monitoring and product decisions.
I know one of you would tell me, brother, all these things can be done by AI, and yes, of course, but ownership is something that will always stay with engineers, as understanding these technicalities for the clients will always be the moat. Just because you have machines, you dont start building houses on your own. You might build a small house if you are curious, but that's not always true in large projects.
Today, if you show code you wrote by hand, people start judging your skills or adaptability to tech.
For me, code is an art that gives you indescribable happiness when you execute something on your own, and only developers can understand. I understand AI is the change, but it's okay to sometimes go back and try to find that rhythm.
Hi, it's been a while since I wrote an article, but here I am with something I've been working on for a while. Do share your feedback in the comments. https://t.co/iRvgKMerpE
When I talk to founders today, one consistent theme is that we don't need junior engineers, since AI does that well.
The question here is: who will be the next generation of senior engineers?
I see everyone has their predictions.
Personally, I think we will see more businesses and small teams, so engineering jobs will still exist.
Someone told me that if you focus too much on what will happen in 12 months, you just live today in stress and anxiety. Do the best for today. ππ»
@sxmawl I tried applying a couple of times, but I was barely filtered. But loved the product you guys are building.
Please check my portfolio, https://t.co/ukVW5SWPxK, in case you ever need me, hit me up.
It's been on my plate for a while. I just published an article on Medium. Planning to do this more often.
I was thinking about how AI-driven software automation could take us beyond the debate "AI will replace developers".
The questions are about junior engineers, new roles, the AI economy, and what humans should actually own.
Do check the link in the comments.
Spent my first week in Bengaluru to step out of my comfort zone (I'd been working remotely for a while) and see the difference.
In tech, the energy here feels completely different. Everyone is actively building something, and every single conversation shifts your perspective.
Bengaluru = Builders City
@quionie π₯² Maybe, but maybe not. Once we get computers that can run models natively, we will go open source. We can do that now, but it has limitations for most of the systems out there.
This is for solo engineers and builders spending day and night building something awesome.
You spent a year or two building an AI SaaS. You shipped products, solved real problems, and maybe you don't write much of the code yourself anymore.
Then you decide to go back to a job. π₯²
And suddenly you realise you can still build software, understand architecture and review code (sometimes), but if someone asks you to write code on your own, you are rusty as hell. π
And the interviews have coding rounds.
What do you do?
Asking for a friend π₯²
OpenAI: Let's release a groundbreaking model, Astra GPT -6
Anthropic: Guys, check the warehouse for our next model, Opus 5.5.
Seems Anthropic just waits for OpenAI to tweet first. π
Opus 5.5 is actually the best for tokens and output, I guess.