Timeline for How to tell your boss that his programming style is really bad?
Current License: CC BY-SA 2.5
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 10, 2022 at 15:55 | comment | added | Rachel | @DanielKaplan 100% agree with that! Starting the conversation with curiosity instead of immediately trying to push an agenda is the way to go. The whole "focus on why your way is good over why their way is bad" is only advice for once you've already established that their code is poor in the first place, and you are trying to convince them that there are better ways to accomplish it. | |
| Mar 9, 2022 at 21:24 | comment | added | Daniel Kaplan | I agree with what you're saying, but this part stood out to me: "focus on why your method is best" Maybe this is a personal issue, but I've found that approaching a conversation this way is less likely to persuade someone. What works better for me is to approach the conversation with genuine curiosity. This is a million times easier said than done, but try to make it a collaboration where you're both trying to learn. | |
| Aug 20, 2019 at 8:28 | comment | added | KolA | Why not just say it. The fact that he's the boss shouldn't change anything in a healthy team (I assume there's no problems to share negative feedback with peers). Especially if YesOrNo vs boolean is a real situation and not just some grotesque imaginary example. Seriously, in my opinion one doesn't even have to be super polite in such extreme cases of incompetence. | |
| Feb 13, 2011 at 23:34 | vote | accept | RoflcoptrException | ||
| Feb 13, 2011 at 10:49 | vote | accept | RoflcoptrException | ||
| Feb 13, 2011 at 10:49 | |||||
| Feb 10, 2011 at 10:36 | history | made wiki | Post Made Community Wiki | ||
| Feb 10, 2011 at 4:25 | comment | added | Cody Gray | About the only time I keep up with Programmers is when I see an interesting question linked from the Stack Overflow homepage. Most of the time, it's an outstanding question or answer from you. Not sure I understand why you might ever have cause to be worried about such things as not being respected by your colleagues, even those older or with more experience. I'm consistently impressed by your professionalism, outlook, and ability to articulate your opinions; another +1 from me. | |
| Feb 10, 2011 at 0:59 | comment | added | Jim Schubert | Whenever another dev does something strangely on my team, I ask for their reasoning because it could possibly be performance or business rules related. Its hard as a developer to admit there are some things you don't know and that there is no universally correct solution. | |
| Feb 9, 2011 at 15:46 | comment | added | Arjun J Rao | Good idea +1 from me | |
| Feb 9, 2011 at 15:34 | history | answered | Rachel | CC BY-SA 2.5 |