Where do managers go wrong? What two simple things can you do to become a good manager?
An opinion column for developers. Brutally honest, no pulled punches.
Where do managers go wrong? What two simple things can you do to become a good manager?
Why dont all engineers just do whatever is necessary? Is there a level of abstraction that requires specialization?
Why do people lie and what can you learn from it? How do you refute and resolve common deceptions?
How do you grow your team with flat headcount? What can you do to avoid chaos when senior people transfer?
Whats the difference between you and someone with power? How do you get your boss to listen to you?
Whats so broken about how we currently do code and design reviews? Which form of review is right when?
How do you cut down on all forms of interruptions? What is the right way to delegate and select feature work?
How do you drive improvements in tools, processes, and projects when your manager is afraid? What do you need to do differently in order to work with some managers, PMs, and customers?
Whats the biggest problem preventing customer satisfaction? How do we detect what will confound our customers, before we hit code complete?
When is setting strategy not enough? How and why should your PUM avoid micromanagement?