42

Those developers working under non-technical bosses, i understand your pain.

1. Pain when they don't realise that output != number of hours put in. Aaaaaaand that acting busy doesn't mean someone's working.
2. Pain when chilling out in office is necessary, because mind jobs don't work same as other jobs. Wherein if you don't vent it out you're gonna screw up the code. Them not getting that.
3. Pain of "meetings".
4. Pain of changing the feature when you're done, and them acting as if its a minor change.
5. Pain of vague requirements.
6. Pain of a product not thought through, and them trying to blame the implementation.

Comments
  • 2
    For sure! If people could be much more understanding in general... 👌🏿
  • 1
    For sure! If people could be much more understanding in general... 👌🏿
  • 1
    The pain of vague requirements is anoying. Even some techical project leaders give requirements that are to vague.

    I try to read between the lines and asking again the same thing.
  • 2
    The pain of dealing with code written by monkeys who somehow hold the title "Senior Developer"
  • 2
Add Comment