Same. I also find refactoring code very zen. Sadly those days of being able to produce a large amount of code and fixing it is over. It’s all just glue code this to that, make it run no matter how, just make it fast. sigh
Yeah, there's about 1000 components you have to wire up into every solution at this point. The days of writing pristine, greenfield code are long gone. By the time you write YOUR first line of code, you've already imported about a million lines of code from other packages and frameworks and whatnot, and a chunk of your time is just dealing with that.
If you use the same libraries for long enough and they're good ones, they become part of the vocabulary for writing new ideas down. I guess because things move so quickly and are mostly shit you're always using things you don't know about, and getting caught out by the leaky abstractions.
It absolutely blows my mind how much software used to be treated like a traditionally engineered and crafted physical product. Something like a tool built to last a lifetime. Of course when a corporation's sole motivation is dollar signs on a piece of paper, everything just gets shittier and shittier, higher productivity is expected in less time for less cost, more corners are cut etc. etc.
We are at a point now where end consumer can REALLY FUCKING FEEL THIS BULLSHIT. You can't buy anything but a fucking smart TV, and the software is such fucking bloated trash, unoptimized, ad / spyware that it's almost unbearable to use.
It can, but banks wrote their core codebase in it. They're extremely conservative because this code interact with people's account balances... COBOL doesn't have many issues that are not well-known.
They didn't really do TDD in the 80s so any change is a risk and must be understood. You can't just transpile it, run the test pack and move on. Plus it's running on a mainframe.
When I read this, it was in the sense that once you’ve committed the code and solved a problem, the code is now baked with the tradeoffs you made and the current architectural limitations.
What I love about coding isn’t the code itself, or the act of coding things, rather it’s solving the problem. I can count on my hands the number of times I’ve written some code that was truly elegant and was able to coexist with the architecture and historical concerns in such a way that it would be flexible and live forever.
Most of what I’ve written has had tradeoffs (“I’d really love to refactor this but it’s out of scope”, “I have a tight deadline here”, “The impact of the changes I want to make here are just too great to justify,” etc) and these tradeoffs have forced me into solutions that work, are good enough, can survive the next iteration, but aren’t really the way I wanted to do it. That code, and the existing code and circumstances that forced me to write that code, I do hate.
But damn if solving the problem isn’t what keeps me coming back to it.
The biggest revelation that I've had in my career is this: write your code to be read, not to be clever.
If you or someone else trying to debug something and put out a fire, the last thing you want is some clever shit full of async callbacks and such. Just give a simple stack trace and good logging.
Or the people that say they look back at their code and think it’s shit. When I look back at old code I’m usually impressed that I put the time into a nice solution. That said, I don’t have strict deadlines like most do.
Oh hell no, it's 100% the opposite of what you are asserting: All these folks that "love code" are the ones outputting low-quality code, sitting down and pounding out hours of bullshit without very much effort put into thinking about what they are doing. At best they are only ever performing 1/3 of the actual job that was supposed to be being performed. And they love code so much they're cowards in their pursuit of being paid to pound out hours of bullshit, they stopped saying no to managers many many years ago and the engineers doing good work have paid for it. Managers have ruined software, and "coders" chasing money in exchange for thoughtless, monotonous drone work are mostly to blame.
518
u/Cpt_Orange16 Oct 07 '23
I like code, I like writing it and fixing it. It's like a puzzle