What are some easy-to-follow tips and tricks for organizations and leaders to avoid demotivating programmers? Share your personal experiences or observations on what works best in maintaining a motivated and productive programming team.
Follow the DEVteam for more discussions and online camaraderie!
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (7)
My primary rule is that a team should be "unafraid". Fear breeds negative behaviours and causes stress. We all make mistakes, we all fail at things, we can all be late delivering a project because something unexpected cropped up. Not creating a sense of fear when things go wrong means people surface their problems much more frequently and have support in finding the answer, rather than anger or mockery.
My second rule is that I expect all team members to be "kind" to each other. For example, a standard that says code reviews and general commentary must not be passive-aggressive and should focus on functionality, rather than the reviewer's preferred method of solving a problem.
This is such a key thing, and props to you for recognizing that. Shame it's not more common in many work environments.
Nice rules 👍
Only one: Be empathetic to everyone.
One big issue I had was that whatever I'm doing wasn't "perfect". Sometimes it doesn't have to! Just make it work, you can improve it later.
Something that applies even beyond software development.
That depends, if we talk about code it is always good that it works well, I don't mean to over engineer, but in case something doesn't work well it is always good to ask for a second point of view so you avoid to improve it later and work twice 👌
I dig