Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I know a lot of developers who have learned their skillset by rote from the early 2010s and have not progressed in competency (they still write code with the same issues as they did a decade ago) or technology (haven't been able to pick up technologies that they lacked when they started).

That puts them in a precarious place since the organization that downsizes would be looking at them first ... and that they haven't been able to attain any mastery of the newer technologies that are coming into play in the system.

For many of them, they're finding themselves leaning on AI to make up for the lack of learning new things (and without learning those new things). They're also realizing that any candidate who is more skilled than they are would be a stronger candidate (and that their job is increasingly becoming entering prompts into an LLM that is easily replaced).

Why they got to that spot and stopped? That's an open question. Some might have gotten comfortable at that spot. Others forcefully reject the idea that continuous learning outside of the 9-5 is needed (spend 40 hours a year learning a new technology). Others may lack the problem solving capabilities to go beyond that spot. I know I've seen all three of those. There are probably other reasons too.

 help



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: