Why is programming so captivating, yet so agonizing?(elsewhere.news) |
Why is programming so captivating, yet so agonizing?(elsewhere.news) |
1. unrealistic time frames and expectations from non-technical managers, and
2. leetcode
Everything else is awesome.
Never some intractable bug, that didn't seem to have any relation to the source code you're reading?
I derive zero enjoyment from Kubernetes configs, or Terraform, or fucking around with log settings, or screwing around with all the knobs for Kafka. That stuff is agonizing.
The click for me was thinking in terms of outcomes and system dynamics. So I make sure to get a good understanding of the final state. Tweaking without a goal is just playing around, or joyless work if you do not enjoy the process.
But seriously, sometimes its not the code, it's the human factor that's painful, other times, well it's JavaScript.
I love writing JavaScript. I like React well enough. I'm not sold on NodeJS, though I'll accept that its struggles are no different than any other package manager.
I just wish the whole thing would stand still for a minute. It's seriously exhausting to keep up with all of the deprecations, rewrites, new "best" frameworks, etc.
I guess programming to me was always an excuse to do math, not necessarily to build products.
Programming is my way to create something. It's like drawing or woodworking. It is creative and logical. That's why I don't mind or even like sysadmin stuff. But I know a lot of coworkers that don't like ops and in my company you don't have to do that. We have teams for that.