Member-only story

The Ten Commandments of an Engineering Manager

#4 No-deploy Fridays are to be kept holy

Fernando Doglio
Better Programming
Silhouette of a child reading with text reading, “#4 thou shalt not deploy on a Friday”
Original Photo by Aaron Burden on Unsplash, edits by Author

You’re the engineering manager (or one of them) for your company — congrats! You’ve made it!

But do you realize the responsibility that lies in your hands? You’re not just “the boss” for all those developers whaling away at their keywords like there’s no tomorrow — you have obligations towards them and the company you work for.

So here are the 10 commandments you shall follow from now on, based on my own experience as a manager and as a developer who loved some of his managers and hated a lot of others.

I hope it helps!

Thou Shalt Let Your Devs Do Their Own Work

There are two types of Engineering Managers, those who understand they’ve chosen a path that takes them away from writing code and those who are just thick-headed.

Look I get it, I also like to code, but do it on your own time. You probably have other responsibilities day-to-day, instead of putting on the developer hat because you think your team is not cutting it.

If you’re really having problems with your deliverables, tackle them directly. Understand what’s missing. Is it that some of the devs are too inexperienced? Then train them…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Responses (3)

What are your thoughts?