I can call myself an average senior engineer. Cannot really pass the DSA rounds at Tier 1/Tier 2.
Somehow was able to keep the jobs I had so far via pure bruteforce and hard work.
These days I am pair programming with AI to write a lot of code. Probably checking in about 10 to 15k lines of code per month on average. I know it may not be a good metric, but if I compare myself to an earlier verision of me, that person would be checking in a 2 or 3 k lines of code at best per month.
I can get the work done, probably can do a bit of good judgement when AI writes sloppy code.
But, I am not sure till when these skills will be relevant
Like what if that judgement is not needed anymore, like 2-3 years down the line?
Is anyone else in the same boat? How are you dealing with this?
vinibrito•4h ago
That's us, developers. That will never change. We're the ones dedicated to it.
Execs, managers, HR, salesmen, designers etc won't suddenly want to spend their whole days, not even half of their time, tinkering with a computer so it can do what they want.
Else Basic and Fortran would have made everyone software developers.
Do you feel calmer now? (:
fragmede•4h ago
My Claude Code usage is through the roof, however.
funnyfoobar•4h ago
But my question is "how many of those will be needed", because I am not saying that programmers are not needed.
When less numbers are needed, there will be so much competition in finding those jobs, esentially would also mean not able to find the work, as there will be always someone who would be willing to the job at lower wage and come to work with more youthful energy.
Just speaking out loud.
bruce511•2h ago
I've lived through two software "explosions" where minimal skills lead to large output. The first was web sites and the second was mobile.
Web sites are (even now) pretty easy. In the late 90's though, and early 2000's there was tremendous demand for web site creation. (Every business everywhere suddenly needed a web presence.) This lead to a massive surge in building-web-site training. No time for 3 year degree, barely time for 90 days of "click here, drag that".
So there was this huge percentage of "programmers" that had a very shallow skill set. When the bubble burst it was this group that bore the brunt.
Fast forward to 2007, and mobile apps become a "thing". Same pattern evolves, fast training, shallow understanding, apps do very little (most of the heavy lifting, if it exists at all, is on the backend.) Not a lot of time spent on UI or app flow etc.
This time around the work is also likely to be done offshore. Turns out simple skills can be taught anywhere, tiny programs can be built anywhere.
Worse, management typically didn't understand the importance of foundations like good database design, coherent code, forward thinking, maintainence etc. Programs are 10% creation, 90% maintainence (adding stuff, fixing stuff etc.) From a management point of view (and indeed from those swathes of shallow practioners) the only goal is "it works."
AI is this new (but really old) idea that shallowness is sufficient. And just like before it first replaces people who themselves have only shallow skills; who see "coding" as the goal of their job.
We are far from the end of this cycle, and who knows where it will go, but yes, those with shallow skills are likely to be first on the chopping block.
Those with better foundations (a better understanding of good and bad, perhaps with a deeper education, or deeper experience) and the ability to communicate that value to management are positioned well.
In other words, yes the demand for "lite" developers will implode. But at the same time demand for quality devs, who can tell good from bad (design, code, ui etc) goes up.
If you are a young graduate, you're going to be light on experience. If you're and older person, but had very shallow (or no) training you're easily replaced. If you think development is code, you're not gonna do well.
In truth development is not about code (and never has been). It's about all the processes that lead up to the code. Where possible (even at college level) try and focus on upskilling on "big picture" - understanding the needs of a business, the needs of the customer, the architecture and design that results in "good" or "bad".
AI is a tool. It's important to understand when it's doing good, but also when it's doing bad.
exitb•6m ago
That’s not the whole story and certainly not the core concern, which is more about developers who already have deep experience, using AI to multiply their output.