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
-
At my old company I had the same problem, PM's were making terrible architectural decisions all the time.
I tried to fix them but once I fixed one two more appeared..
Sadly my solution ended up going to a different company, and my new PM is way better - why?
Because he is also a developer and works on the project with us any chance he gets, this simple change forces them to think a lot more about their new ideas as if decision turns out to be terrible they will see it same way as other devs -
What I've just is experienced is the complete opposite. I got to make the decisn decisions, demonstrated what I had done to the head of engineering and had it signed off. Now a few months down the road, he forgot about it and is now talking like he's never seen it before. He doesn't think that it should be done the way that it was done - after it went live a week ago!
-
Glad to see I am not alone.
Here even a good solution will have a go and later the senior plans a meeting to discus the solution.
In the end, we now know that he didn't like the solution. But why or proposing an other solution or both still a mystery until today.
(And the original solution was also already in production) 🤷♂️ -
@electrineer and when you ask why its like how it is the answer is "that's just how it was when I joined"
-
@cmarshall10450 I know not to ask
how often does it happen that you have to prevent terrible architectural decisions from being made, because people who are in charge but obviously have no clue, make really weird suggestions and are really confident that this is a good idea?
PM: so please analyze functionalities X with dev Y, since module Y that dev Y develops shall provide these functionalities.
me: as i said yesterday, module Y will use my module X and shouldn't care about how this is going to be implemented.
PM: yeah, but module Y shall be able to... (lists some functionalities)
me: yes, that's what i'm currently working on in module X. my current state of the API can be used in a way that... (lists different low level functions and how a combination of them can be used to provide these functionalities)
PM: okay, hmm... i just realize that module Y will actually be a user of module X...
well.... yeah?!!
i always thought that was crystal clear?? 🤦♀️
rant
antipattern
daily scum
🤡