Archives

2018

June 17 - Advice from a stranger on a boat: the zen of engineering management
May 23 - Five lessons for aspiring engineering managers
May 1 - Relating Ed Sheeran’s Photograph to coaching junior engineers
April 22 - We only need to be as clever as we need to be
March 5 - Echoes of a downpour
March 3 - The incredible machine
February 5 - The three questions – more management advice from an Uber driver
January 31 - Play with the hand you are dealt with

2017

December 19 - Endless improvement
December 8 - Building confidence for presentations
December 5 - A moment’s peace
November 27 - Another approach to reading business books
October 17 - Use vacations to improve your team
September 25 - Explaining the difference between strategy and tactics with RPGs
September 17 - You won’t be like any other manager
August 11 - Maintain the ability to read code
July 23 - Ernesto with gusto
July 9 - Handling your team emotions as a new manager
June 26 - 85 slots a week
April 5 - Career advice for junior engineers – don’t end up like me
March 18 - Always extend into unknown sectors of code
February 24 - What do you wish for the team?
January 3 - Feedback for yourself

2016

December 24 - Crawling through plumbing to glamour
December 17 - Triforce of engineering management, a developing philosophy
December 10 - Bus factor trends to zero
November 28 - Requirements lawyering with specs
October 16 - Management and life lessons from an Uber driver
October 14 - Document every glitch
September 18 - How many developer weeks (dukes) will that take?
September 15 - Staying technical by reading research papers
August 29 - Shadows over the replacement
August 27 - What’s everyone doing? (or Black Sheep Wall)
August 14 - Binary status, done when it’s done
July 29 - Skimping on equipment
July 6 - If you want to be a senior engineer, be visible
June 5 - Reflections of a new engineering manager part 2
May 22 - Three men make a tiger
May 12 - Boxed in part 2
February 6 - Encouraging the team to clean the espresso machine

2015

December 16 - Landing your first job as a junior engineer
November 18 - Me friendly metrics
October 21 - Saved $1660 with a $40 experiment
October 10 - Suman growing Rockstor to 10 paid users
September 30 - How does your team handle a stolen laptop?
August 27 - First day of a new hire
August 19 - Flabby coding muscles
August 18 - Backend is my darling
August 15 - Shadow teacher
August 12 - Managing with only your voice
July 31 - Don’t harp on code style when asked for help
July 30 - Evolving your tech stack
June 16 - Code dilution
June 15 - Time cost of a simple feature
June 14 - Zorb not umbrella
May 21 - Light production in red
May 12 - Remaining Technical by Writing Tests
May 6 - Defeating Captain Hindsight
May 3 - Don’t ask for daily status – talk to a stuffed bear
April 28 - Managing something you didn’t create
April 25 - Rockstor – managing an open source community
April 23 - Reflections of a new engineering manager part 1
April 6 - Did the junior engineer speak?
March 23 - Creating presence – keep that green light on
March 22 - Stay healthy
February 15 - Nudged towards management
January 20 - Staying technical part 2
January 15 - Every bug drains one day
January 13 - The enhancer
January 9 - When do you automate?
January 5 - Start with two and a half percent time to stay technical
January 4 - Boxed in

2014

October 24 - What do I do if someone on my team gets hit by a bus?
September 25 - Explore to improve your technical common sense
August 8 - Adopting new technology – moving from Ruby to Go