398
Anon tries to figure out his coworker
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Feb 2024
398 points (97.8% liked)
Greentext
4570 readers
1012 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 1 year ago
MODERATORS
I used to curse to myself while reading code at work. Maybe I thought it demonstrated that I was really working; look how furrowed my brow is, how forceful and heated my mouse clicks!
After being enlightened however, I realize that the only perfectly implemented, bug-free code is no code at all. The app didn't ask to exist, certainly not in the state it's in. It too deserves the compassionate understanding that all beings suffer to exist.
Plus I work remotely now so no one can hear me yelling at the computer anyway!
Man I curse looking at my own shitty code.
I'm pretty sure whatever gods created me cursed a hell of a lot while doing it. I know the surgeons did. And since I exist to suffer I give my code no such leniency like this SuFfEr TO exISt bullshit.
I guess I haven't ascended. I've been a SW dev for many years (def >10, probably 15 at this point), I lead a team, and I still curse to myself while working in our codebase. I think it's because I spend like half my time in meetings so I take half the technical work my reports do, so it bothers me more when I finally try to get something done.
Occasionally I'll rage-refactor something and submit a massive PR that fixes a bunch of annoying stuff (currently sitting on ~1k changes stashed), but I only send those in just after a release (don't want to get yelled at for missing a deadline). Or we'll take too long to make a decision on new dependency, so I'll just build it in an afternoon (just did that last week; 300-400 LOC).
I'm no rockstar dev, but I can crank out the work when sufficiently pissed off. Otherwise, I just coast a bit like the rest of the team. So if my boss wants me to be productive, he just needs to delay until I get fed up and just do it.