by octo-andrero on 11/13/24, 12:09 PM
Because it's interesting and, probably, the easiest way to bring significant business value. Most of the problems and opportunities I saw lies somewhere on the border of different departments, technology stacks and abstraction layers. And so little people want to dive into this mess, because it requires knowledge from other domains to solve.
by Ocerge on 11/13/24, 6:54 PM
I've wavered on whether being a generalist/"full stack" person is good or not 10+ years into my career, but I think at this point I'm convinced 90%+ of work is just tying libraries together across presentation boundaries, and you should be able to solve problems end-to-end. It's not that hard, I (and the vast majority of people I imagine) aren't working on anything particularly complicated; drawing domain boundaries seems silly.
by yen223 on 11/12/24, 11:38 PM
Because I lack the ability to focus on any one programming domain. I find them all too interesting to ignore.
by gregjor on 11/13/24, 12:37 AM
Curiosity, career flexibility, and necessity from four decades in the business. I think of over-specialized and narrow skills as fragile, and broader more generalized skills as anti-fragile.
by runjake on 11/13/24, 7:29 PM
Because I'm both interested in, and need to do a lot of different things. I enjoy being self-reliant.
by joshagilend on 11/13/24, 12:55 AM
AI