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
-
@iiii @Sid2006 The technical managers are all “former developers”
The VP of engineering, too (or whatever his shiny new title is). He even brags about it, despite that the last time he wrote code was in the 80s, maybe 90s. -
@Root but it's still not their job to look into the code and evaluate it in any manner whatsoever
-
@iiii Oh, but it is!
They do many of the code reviews. -
@Root weird... Very weird
-
You could be 100% right that they're just idiots.
But, consider the possibility that they actually know what they're talking about better than your co-workers do. After all, IN THEORY, they wouldn't have gotten promoted if they didn't prove themselves over a period of time.
Yes, some people get promoted despite their incompetence and because they know how to play the game well... and some get promoted because they're much better at a management role than a technical role so that's where they go and perform better.
But that's not every manager out there. Some actually are very good technically and it's just a natural progression to move into management at some point.
Hey, I'm not there, so I don't know. You could just have all idiot managers, absolutely possible. But don't ASSUME that's the case and don't assume everyone BUT them know what they're talking about. -
@fzammetti I venture to say that op knows the environment, knows the people and therefore is aware that they are morons due to first hand experience. We ain't there, op is, and it is because of the legendary janky devs that I suffer a fuckload at work, had it not been for people actively making better code it would have been different.
-
I felt this in my soul, I had once an entire room of executives shit on the timeline I gave for a project because it would include proper architecture, unit testing the whole works.
"<X> never did this to us, he would just comply and finish the task!" I legitimatedly told them that the reason why it would take longer was because I had to include a proper solution into the GARBAGE software <X> had built, and that they thought that they had some good will hunting shit by hiring the janitor-turned-dev (that was his story) but just had an incompetent moron riddling the place with systemic issues and security issues.
I feel you, next beer is to ya -
@AleCx04 she have shared so much about her job that we know those morons are real 😂😂😂
-
@fzammetti Totally fair and valid points …were this not the second worst codebase I’ve seen in the past twenty+ years, and the second worst management.
The company cares more about diversity and inclusion than skills, and promotes the same, so the quality of employees has been dropping continuously. As an example of the management… my previous manager was a vindictive micromanager who told me weekly that nobody in the company trusted me or wanted to work with me, and wanted twice-daily updates on my tickets (in addition to daily standup) plus a weekly summary at 4pm sharp, and dictated changes after every update. My other manager was better, but still a micromanager who complained about most of what I mentioned — with a few odd compliments thrown in. The managers at $work are shit, no exaggeration.
Regardless, it’s good to see some counter points / outside perspective :) -
@AleCx04 🍻
-
@Root Totally cool, you're the one there so I gotta accede to your judgement. Just wanted to offer a potential alternate perspective in case you hadn't considered it. Sounds like you have, so carry on - with my sympathies :)
-
@Root
Tech managers are usually bad developers who failed upwards.
They can stick their code reviews where it don't shine. Idc that you were a programmer decades ago. Idc that you say my code is bad cause you dont understand what actually is good code today.
Be a manager you fucking cunts and let the actual programmers worry about the code.
Now go sniff some glue ya fucking mental case and let us code.
When managers look at my code, it’s shit, it’s over complicated, it’s overly difficult to read, it took too long, it’s too much for a simple ticket, i handled too many edge cases, we’ll never need most of it, why did I bother making it extensible when it’ll never need to change, how dare I use “unless”, why did I bother writing all these comments, why did I update the documentation that nobody reads because it’s outdated, etc. They say I should be more like the legendary devs and push janky code quickly, and complain that I don’t have any flops (problems in prod) like those are a good thing.
When my coworkers look at my code, they say it’s clean, amazingly easy to read, a monster feature that’s somehow still a joy to review and work on, it makes their lives easier, that it does exactly what it should in all cases, that they learned something from reading it, and thank me for the comments and documentation. And marvel that I finished it so well in so little time.
Am I bragging? Not intentionally; I’ve heard these things repeatedly since I started here, and the contrast between the above is so stark.
In reality, the managers are just idiots who were promoted far above their competence, and make everything worse. (Gee, who woulda thought?) It’s just so frustrating.
rant
dumbasses
mirror talk
phb
special olympics retard race finalists