How does responding immediately provide you with essential slack time? How can eschewing prioritization help you prioritize?
An opinion column for developers. Brutally honest, no pulled punches.
How does responding immediately provide you with essential slack time? How can eschewing prioritization help you prioritize?
When a project has multiple leaders, how do you quickly make aligned decisions that stick? Who has final say without abusing that power?
How do you pay off technical debt before a catastrophic failure? How do you convince management to invest the time?
How do you expand and utilize your network to land a new role you love? Why is applying online so unlikely to succeed for an experienced engineer?
What skills should engineers develop? How should hiring manager prioritize candidates?
How do you estimate deliverables, prioritize assignments, design solutions, choose implementations, and verify requirements when there’s no authoritative source to tell you the right thing to do and the right way to do it? What do you do when the experts disagree?
How do you engage with your manager and peers when you’re no longer the boss? Should you be the boss again?
Is getting an advanced degree worth the time, effort, and cost? Does the university you choose matter?
As a middle manager, how do you create a plan in a week that pleases the management chain above you (and partners), the staff below you (including multiple teams), and your own desires for influence and impact? When are three plans better than one?
What is matrix management? Given its awful track record, why does it persist and how can you avoid it?