Whats so broken about how we currently do code and design reviews? Which form of review is right when?
An opinion column for developers. Brutally honest, no pulled punches.
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?
Should you keep work and home separate? How do you achieve balance without imploding your career?
What causes a death march to fail? How do you escape a death march?
How do you break the cycle of habitual poor performance? What can you say that is caring and respectful but will still ensure resolution?
What are the major sources of wasted effort? How can you be more efficient and less frustrated?
What makes a good code question? How do you get recruiters to setup loops quickly?