3 ms·
I find this to be true even just entering my 30s. I've made a few slips here and there, but it appears that there's a shift from mastering a skill to having dec
by ljm 8y ago
I find this to be true even just entering my 30s. I've made a few slips here and there, but it appears that there's a shift from mastering a skill to having decent domain knowledge for a specific tech.
So, you're not hired on how to solve a problem now, you're hired on how much you know their desired solution. This isn't engineering, you're not helping desig action, you're implementing it.
One of the huge failures in this sense is that tech has assumed priority over user value. Like your users give a shit about microservices, React, Vue, etc. etc. when you're using more of your runway on the infrastructure and not on the solution they want.
Most of this stuff has little value to most businesses. So if you push back you don't get hired; you have to find the places mature enough to understand why you would push back at all.
- tabtab 8y agoI wish domain knowledge was valued more in tech staff, but I've just found that's often not the case. I'm not entirely sure why, and my theories (okay, guesses) would take a while to explain. Further, if people don't see the "latest" UI on their screen, they become afraid that the underlying technology is "behind" even if it technically satisfies a business goal. Books are judged by covers.
- mason55 8y agoThere are a bunch of different things wrapped up in your post and I won’t address them all. One thing though is that we don’t separate a technician vs an engineering in computing. Think about a plumber vs a water systems engineer. Both are valuable and paid well but they have very different roles. Lots of people can be trained to be implementers and do valuable work. But we also don’t have stable best practices so that makes it harder. The line between engineer and implementer is blurred because an implementer constantly has to evaluate which new things should really be best practices.