Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
jestdotty621210hI can play with both as long as people actually answer questions
but if things are fucked up I'll refactor to make them less fucked up. cuz I don't like extra work. they might say no though. which is fine but I won't be doing overtime in that case
I like quick wins though ngl. they make me HAPPY -
jestdotty621210halso I have a feeling people were depressed before the job so made the job atmosphere depressing for everyone else. it's like a psychological tug of war
some people take "pride" in their depression, so walk around wanting the world to burn and harbour "fuck you" attitudes
I seem to get mistaken for that sometimes which confuses me. like if I wanna make things better and people say no they think I'm gonna be malicious but I'm not. I'm just gonna protect my energy and it has nothing to do with malice. it's just boundaries so I don't get involved in stuff that will total me -
whimsical22010hGood devs go to heaven, bad devs go everywhere. The 'good dev' way actually makes you not wanting to finish personal projects. It's just not fun. And not finishing, is even a worse dev.
-
CaptainRant430939m@jestdotty I find it brings down morale if people answer questions in a flat and careless way, but it's better than not answering.
So you are a refactoring genius, hm? Companies definitely need someone who's good at that.
Quick wins are one step closer to happiness? Heheh. -
CaptainRant430935m@BordedDev Of course I can't magically explain why someone gets fired, but a common thread is:
* Management doesn't like you and conspires against you to make sure you will get fired. They will always smile in your face, you will never suspect it so much until it's too late, but you already knew because they started treating you like you literally stink. Output won't have to do with it; it'll just be their excuse to fire you. The true.. true reason is they don't like you.
Usually the good dev in this case has no problems and will usually thrive if he has a good fit with the team and keeps outputting enough. Of course, it will get problematic when output isn't enough, but some companies will be understanding and try to coach you through it, while others won't care and will just kick you out, security included. -
CaptainRant430928m@jestdotty Yes, I know people were depressed before the job; you can see it in their faces of despair and yes, it doesn't help morale. They have that "I'm barely making enough money and I don't care about the job or the politics, please just let me enjoy my life" face.
Yeah, the pride depression ones are very contagious...
I also get mistaken for that and people told me it's because I don't smile. lol. It's admirable you have your boundaries. People definitely need boundaries.
Good dev: test suites, documentation, tracking
results: decent coverage, more predictable, more maintainable, saves time and money, accountable to stakeholders, happier team thanks to transparency
environment: matured middle-sized to bigger company who takes things seriously (because they usually have to if they work in a heavily regulated sector)
Bad dev: idgaf attitude, let's just run with it and see what happens flow, go for bare minimum happy path
results: a new bug at every possible situation, mystery bugs, an endlessly-growing backlog where people in the team are so depressed no one cares what ticket to take on, morale goes down crapshoot and so does code
environment: start-ups who want quick wins and make money-based decisions only and whose budget is being guarded by the higher-ups
I've worked with a bad dev before and also with a good dev and I appreciate the difference. lol. Nightmare.
rant
ilities
good-vs-bad-dev