As an engineer, ever found yourself asking the “What the heck is my manager doing?!”. I have, many times. Perhaps you’re on your way to becoming a manager yourself, in which case you might be “What the heck am I getting myself into?!”. Of course, if you’re a manager already, chances are you’ve asked yourself at least “What the heck am I doing wrong?!”.
No matter how you put it, the question on all of our minds at some point has “What should the manager be doing?”, and the only good way to answer that question, is to first answer the “What do great engineers expect from their managers?”.
Marcus Tomlinson is a software engineer and author with well over a decade’s experience in both closed- and open-source, cross-platform software development.
Immediately following his university career, Marcus landed his first job at Africa's leading manufacturer of electronic security products: IDS, where at the age of 21, he co-created a modular test jig system to help the company keep up with its rapidly growing product demand (A system that is still in effect today).
At 25, he went on to land his first senior role at the world's largest supplier of military and mining simulators: ThoroughTec, making him the youngest employee to hold the position. During his time there, Marcus completely overhauled the company's internal audio engine, as well as created a data-flow framework to modularise and simulate complex vehicle control systems.
In late 2013, Marcus landed a job at the open-source software giant: Canonical, designing and developing the Ubuntu Unity Shell. From 2013 to 2016, he rose up the ranks from Engineer to Technical Lead on the Ubuntu Personal team, and presented at a number of open-source developer summits.
Marcus has since served as Committee Chairman at The Computer Science Association of South Africa, developed software for the UK Government, worked with the Flutter team at Google, and written multiple critically acclaimed publications on programming, career development, and engineering management.
Most books have a lot of fluff and very little content, they can be often condensed to an article. This book has the opposite problem. It has some great points, but most points could do with a little explanation. It reads like the sub-headings or summary of a book.
I'd suggest the author write another book with a little more explanation. A few stories where appropriate doesn't hurt. Don't pad, but add useful explanations.
Ready, set, and go! The book is direct without the “nuts and bolts” that keep you thinking about what was said and why, but rather informs the reader of whats expected.
I'd nickname this book "The 150+ Commandments of Software Management". Right to the point (literally!). LOADS of great advice for managers, new and seasoned!