3 ms·
I think there's a number of hours a week I want to spend writing code, but while it's more than 10 it's less than 40. Above and beyond that, I love software, b
by strken 3y ago
I think there's a number of hours a week I want to spend writing code, but while it's more than 10 it's less than 40.
Above and beyond that, I love software, but I don't love Zoom calls, on-call shifts, unnecessarily annoying processes that I'm not allowed to automate, Slack messages, KPIs, objectives that combine vagueness about what we're doing with strict rules about what we're not allowed to touch, horrific dynamically typed JS code where half the arguments to a function are obscure mashed-together objects, over-specified tickets that leave no room for creativity, trying to jam my code into a service where it doesn't fit because leadership wants to encourage code reuse but doesn't understand DRY, or anything else that makes up the actual profession of software engineering.
- sawyna 3y agoThat's all not programming. I absolutely hate the corporate working style. The programming part in itself is always interesting to me, because regardless of who sets the constraints (me in a hobby project or the leadership in a company), they are what make the problem challenging and exciting.
- nly 3y agoI work for 40 hours a week but I'm pretty sure only 2 are writing code. That's the problem. I'd happily write code for more hours
- turdprincess 3y agoI think in this career it’s possible to optimize for 3 levers - WLB, money, and fun work. If you truly want to code a lot, a startup is the place, but you will earn less money and work more hours. Big tech offers big money and good WLB but often at the sacrifice of interesting work.