4 ms·
it depends what skills you're talking about. when i see people complaining about always having to learn new things, it's related to new libraries, frameworks, t
by willsmith72 3y ago
it depends what skills you're talking about. when i see people complaining about always having to learn new things, it's related to new libraries, frameworks, technologies (e.g. now i have to learn graphql, now i have to learn to make things cloud-native, now i have to learn go because it's cooler than java).
this stuff in my experience is either taught badly or not at all in universities, and i don't even mind that. the institution can stick to fundamentals applicable across the given hot tech on any day
personally i don't agree with the sentiment. constant learning is something i love about the industry. for one it's interesting, but it also means there are always opportunities to prove yourself by being interested in learning
- tharkun__ 3y agoThat would be OK if they actually let you learn while doing, which is my preferred way of learning. But they ask you to give ironclad estimates for how long it's going to take to implement <insert completely unclear requirement in one sentence> in <technology nobody has heard of so far>. They can go do whatever they want to themselves. Either tell me what cool new tech you want me to try out and what problems we might want to solve soonish and I'll see which of those and how it might be applicable to or you tell me you want to build <whatever it is> in whatever tech I think will get me there best and fastest. If you know so much, do it yourself. Oh you can't? Well then STFU (not you you but that proverbial manager type above you that seems to know so much)
- not_the_fda 3y agoNone of its "new", its simply repackaged and slightly different, not really any better. Its just constant churn of frameworks, languages, and libraries.