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
-
@retoor And what if I say "I'm going to implement Y because X." and management says "Just do Z for now and put Y in the backlog for later." in which case that literally never happens? Or when I put up a merge request and it gets ignored for over a year until someone questions why something is still broken?
-
If you start all your arguments with "Listen bitch..." then you are guaranteed to get more attention.
Otherwise, dunno. You just need to be really sure what you're talking about, exert confidence and demand to get answers or actions on your concerns. It's a plus if you ask specific people by name. You should also make sure you get a specific slot to speak up and then say what you need to while people are listening.
I'm not exactly sure why people listen to me, but more often than not I don't really give them an option to ignore my requests. Especially naming specific people or asking "what do you guys think" can prompt answers or sub-questions like "sorry, I wasn't listening, what are we talking about?" :D -
@torbuntu Ah yeah current client is like that thanks to PM(S) who can only think in micro short term. Unfortunately can't give you much advice because they don't actually care it's broken until someone with a bigger dick can slap them. Once made his boss slap him, he was well behaved for a little bit
WHEN YOU DON’T LISTEN TO THE PROGRAMMER...
The transition from developer to manager.
How can one phrase things in a way that they won't be ignored? As in how to ask questions that will lead to actual answers and a path forward instead of being ignored or dismissed as "not enough"? Too frequently everywhere I work I've experienced the pattern that I'll be close to identifying a problem/solution but my mentions are often dismissed, and then months later when things are really bad someone else, usually a manager or higher ranking engineer, says the same exact thing and it is suddenly this huge revelation. Of course I can share links to previous meetings about the topic where I tried suggesting whatever this is, but it again goes ignored as "contextually invalid" or something similar.
Is this normal? Do I just need to wait until I'm a higher ranking engineer to earn this respect of opinions?
question
credit
ignored
management