There’s a guy at work I hate so much. He doesn’t know when a problem shouldn’t exist, he never checks to see if there is a better more maintainable and efficient way to solve a problem, lacks attention to detail, has the attention span of a goldfish, writes shitty overly complicated code, fuuuck

If you talked to this guy in person, you’d think he’s a genius who has it all figured out, but he’s just a professional bullshitter

that's all meaningless shit. the only thing that matters is that everyone has a job that earns them money, and they don't have to sell drugs

everything else is bullshit

no one cares about “better solutions”

@kiki Though it is an audacious proposition, I am still confident we can neatly accomodate "legalization of slanging dope" into such an argument.

@kiki I mean I care about a better solution

better solution means less work for everyone else

it's not just about getting paid but also the quality of your experience while you're getting paid

@jestdotty Yes, and it's absolutely okay to hold yourself to high standards, but enforcing it on other people is kind of silly. As long as the code works, does so with at least medium efficiency, and doesn't introduce obvious bugs — the sad truth is it's fine enough for production. Making it subjectively better is extra work.

@jestdotty by making it less work, you eliminate workplaces and job opportunities

what do you think frontend frameworks are for? they're good for the economy!

@cprn I didn't say subjectively better

@kiki your boss doesn't know what work you do, so no need to torture yourself. they can't tell how much work goes into anything you make, so you can make any impression you want and they can't validate it

@jestdotty you don't know me, my boss or my work

@jestdotty Yeah, but it's very, very hard to make the code that meets the above requirements objectively better. Usually it boils down to performance vs maintainability tradeoff. The code that doesn't meet those expectations — sure. But that kind of improvement happens during the code review, right?

In my experience, people who shout the loudest about how their colleagues write bad code, are the ones with least understanding of what that code does and why it does it in that particular way.

@cprn I am not competing on subjectivity. that would be illogical

in my original message where it hints the exclusion of that is when I said "less work for everyone else". this means if they feel like what I'm doing causes more work for them I would be going against my goal of making less work for everyone else

when people compete on subjectivity they create more work for others. because then they're playing tug of war with each other's subjectivity

@jestdotty I think you took my comment too personally. 😆

@cprn no? I took it lazily. was too lazy to explain it at first

I mean I've literally done this. I know people disagree with it because there's people that run around saying it's best for everyone but they speak on others' behalf as an excuse to push their own agenda

like the ad-reel of "this software/framework will save us time!" but then it doesn't meme

and I didn't nitpick people's style in pull requests. that sounds like a waste of time. you can't defend that point and all you'll do is make team members feel at odds with you. degrades the quality by which you're achieving said money

Professional bullshitting is a difficult art to master