Monthly Archives: March 2018
Some blogs I recommend reading this month…
How to Rands
Setting expectations for those you work with is important, Rands lays out his very clearly. Many ideas can be taken into our work environments to improve interactions with our teams.
A Wake-Up Call For Tech Managers
“Create an environment where your programmers can fully contribute, or else the best ones will leave.” I do find it difficult to understand managers who wouldn’t want to get the best out of engineers. This cannot be done without involving and listening to them. Good advice to change things: Be humble; Listen more, tell less; Ask more often than tell.
The most surprising principle of good leadership? Don’t be busy.
Not being busy is a challenge but I believe it’s more about the signals you send your teams than the actual work you have to do. Visually showing that everything is under… Continue reading
I’ve been a manager for a number of years now but still enjoy getting my hands dirty in the code. There’s a buzz I get from understanding a problem and delivering a solution! Full-time coding is difficult to let go of for many engineers moving into management, the challenges moves into finding the right balance. Staying close to the code is important but there has to be a different mindset, especially for the sake of the team!
There’s a simple rule I follow – don’t take on feature stories. Feature stories are a business priority so the risk is too big if I cannot give them my full attention because of other commitments. These stories must stay with engineers, but managers can still remain close to the code with code reviews, refactoring, bug investigation, etc.
Work on tech stories
Non-blocking tech stories are a lower priority than feature stories, usually,… Continue reading