alt Hacker News> How is this not a skill issue and why would one conclude that you need to stop learning if this is the case?
It's not the skill I'm interested in learning nor is it the same skill I spent my career building
My problem also is not just to do with "My future learning" it is also about the value and opportunity to use the skilled I already spent decades on. Which are now devalued heavily or will be in the very near future
I wouldn't be so negative.
Maybe to cheer you up: we're doing a few tests at our org, and we found that product-minded engineers still have a tremendous leg-up compared to other people when it comes to actually shipping products. It's not even a race.
It's not just quality of code, it's also speed of execution, maintainability. Why? Because we're not building 200 database tables + 200 endpoints when 1 table + enum suffices. Yes that happened. There was also one feature that I can't comment much on because it would doxx but: a PR from non-dev took months, was 100k LOC and rejected by product and engineering as low-quality. The same feature built by my team was 900 LOC, feature complete, shipped.
Nothing beats the combination of domain expertise and expertise in the medium.