Sometimes my hatred for code is so.. overwhelming that I think I need a sabbatical or should even stop altogether.

Let's face it. All code sucks. Just on different levels.
Want to go all bare metal? Love low level bit fiddling. Well, have fun searching for concurrency, memory corruption bugs. Still feel confident? Get ulcers from large C/C++ code base already in production, where something in the shared memory, function pointer magic is not totally right?
So you strive for more clean abstractions, fancy the high level stuff? Well, can you make sense of gcc's template error messages, are you ready for the monad, leaving behind the mundane everyday programmers, who still wonders about the scope of x and xs?

Wherever you go. Isn't it a stinking shit pile of entropy, arbitrary human made conventions? You're just getting more familiar with them, so you don't question them, they become your second skin, you become proficient - congrats you're a member of the 1337.

  • 2
    ...and then there are the great artists
  • 1
    @phorkyas A great businessman, nothing more
  • 0
    @Mr-Myrk it's a different topic. But have you seen an interview with him? Just take the one with Everyday astronaut/Tim Dodd: https://youtube.com/watch/...
    To me he seems to be a great project manager, lead engineer with _almost artistic sensitivity_.
    (maybe I'm biased, because he's also a physicist, ..and also I'm basing it on not so much data either, but on what do you base your dismission?)
  • 5
    I prefer the low level shit every time, and for my projects, I choose the simplest tech stack that will reasonably do the job.

    More shit means just more moving parts, more that goes wrong, and if it goes wrong, you have to sift through layers upon layers of abstraction only to find out that you actually can't fix it, you have to work around. Especially when what you are facing isn't even a bug, but a leaky abstractions, and they always leak at some point.

    I mean yeah some degree of abstraction is useful because raw hex machine code just isn't maintainable nor portable, but that doesn't mean ever more abstraction is always better.

    It's a shame that the sound engineering principle of KISS is a mostly lost art these days.
  • 2
    I'm always missing out on something another language or feature has
  • 5
    Everything sucks because people half-ass everything. Everywhere you look, things are crap. The further you dig, the more crap you'll find.

    It isn't computers that are the problem because you'll find the same issues literally everywhere you look. It's the people that designed them. "Good enough," "but I have a deadline," "this is how we've always done it," "not my job," "that's too much work," "they're paying me to build it like this," "just do it," "don't worry about it," etc. Phrases/mindsets like this are why everything sucks.
  • 2
    @Root agree, very much. - We've come to hate that phrase muttered far too often: "We have no time for that!" - Yeah, release is pressuring, so we can't do it properly? Just the minimal change, not the larger refactoring that's so much needed.
Add Comment