3 ms·
Great article. This is something I've said pertaining to interviews for years. There has to be advancement in the skills. Doing something every day is not an in
by JeremyMorgan 12y ago
Great article. This is something I've said pertaining to interviews for years. There has to be advancement in the skills. Doing something every day is not an indicator of improvement.
In fact, sometimes it can be worse. When someone says "Call this person now! he/she has been writing C# for 10 years!". That's great and all but have they been improving their craft over that 10 years, or getting enough work to not get fired? There's an enormous difference. And many times I would run into folks who sunk into a rut and did the same thing for 10 years basically "coasting". They make small incremental changes in what they do every day, but weren't out seeking ways to drastically improve.
Programming is different than many other fields simply because it requires passion to survive. If you look at learning new things like "Ugh, I have to learn ___", eventually you'll start slipping and end up hacking PHP Wordpress installs somewhere for subpar wages if you're employed at all. If you seek out new things to push yourself because it's enjoyable keeping up is intuitive and easy. Even stuff you may never use for your job can teach you new ways of thinking.
Now if you'll excuse me I need to go back to playing with RUST.
- guelo 12y agoWith the speed of technology changes I think it's pretty hard for programmers to get stuck in the exact same rut for 10 years. Using your example of C#, there has been huge changes in the last 10 years to the point that it's barely the same language. Even if you imagine the most staid company that refuses to upgrade their tech stack, the last 10 years has seen so many changes in the web and mobile that it's hard to imagine that there hasn't been some pressure on even the most unmotivated programmer to learn new skills.
- JeremyMorgan 12y agoThat's why I mentioned iterative changes, such as the changes to C# over the last 10 years. Just because they started using generics at some point doesn't mean they've been learning anything to drastically improve their code. It's very easy to sit at a company building calendar apps for ten years and fall behind the rest of the world. I see it every day.