Things I learned this month.

1. Do not reference your solution as a hack. As in "I can make a hack to get around that" management actually views the solution as bad. But present the same solution with "I have this idea to get around that" then they love it and think you're great.

2. Management has no idea the difference between ML and if/else statements. If you can mimick ML with if/else then do it. Takes a lot less time and resources.

3. Don't enter a video meeting in just your skivvies, management views this as bad and HR will release a bunch of work-from-home policies in retaliation.

4. When explaining things to management don't try to explain the technical stuff. Is a waste of time and breath. All they really want to know is when you will be done. They don't care the difficulty level of the code involved.

I'm sure next month I'll learn more things.

  • 59
    Me to another dev I trust: Yeah I fixed it, it works but man it's really hacky, I don't like it.

    Non technical guy walks in: Working great boss! Will last 10,000 years!!! We'll never see that error message again!*

    -Another dev I trust looks at me nervously-

    Me to another dev I trust (whispering): I changed the error message....

  • 4
  • 17
    That about right.

    Also - male sure to talk about how great another team member is, before talking about how bad another team member is.
  • 5
    BTW, part 3 is pretty obvious. If it's a video meeting it does not matter where are you. You should look the same as if the meeting was in person. And being just in your underwear isn't a choice.
  • 3
    @F1973 yup, I am upper management, and before that I was a senior dev. Not saying this shit don't fly everywhere, but it is a sweeping generalization
  • 8
    If your management is like that you should probably hit the road as soon as you financially can.

    ANY good manager should know shit about code. Yes they shouldn’t be the architecture and cybersec expert but at least know how it’s done.

    In most small and middle-sized Russian IT companies they understood that managers and programmers don’t work well together so teamlead acts as a proxy. You only communicate with your teamlead and occasionally communicate with other experts, for example the copywriters, designers and translators. Teamlead is granted some additional decision making privileges. Works fine.
  • 5
    I wish people actually listened to me when I call something a "hack." I could say something like "this is a temporary, hackish solution that will probably break every three months and should be replaced with a proper and robust solution as possible," and suddenly it's the standard, company-approved, me-approved solution and every time it breaks I have to remind people that it was never intended for production.
  • 3
    Communication is definitely an important key to "survive" in office politics. Noted from your post. :D
  • 0
    @EmberQuill for folks who don't understand it's all about trial and error to find the language and such to get the point across.

    Granted some folks don't really want it know.
  • 0
Add Comment