Similar authors to follow
Manage your follows
About Marcus Tomlinson
Marcus Tomlinson is a qualified BSc 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.
Customers Also Bought Items By
Titles By Marcus Tomlinson
No matter how you put it, the question on all of our minds at some point has been: "What should the manager be doing?", and the only good way to answer that question, is to first answer the elusive: "What do great engineers expect from their managers?".
It’s been over a decade now since the release of C++11, and the evolution from "classical" to "modern" C++. I thought it a good time to share some of the coding standards I've adopted over the past 10+ years of my career.
No, not the kind that sweats the small stuff like formatting, naming conventions, or comment style - when it comes to these things, I say just pick a direction upfront, and keep consistent.
What I want to share are a handful of simple guidelines and best practices I've personally utilized in producing (if I can say so myself) some solid C++ projects these last few years.
What better way is there to prove a skill in coding than with code itself? Not only is writing open source software a great way to learn and acquire new skills, it’s a brilliant way to gain real world experience you can legitimately claim on your résumé!
In this book, I will show you the system I use to design, develop, and deliver open source software, steer you away from the mistakes I’ve made along the way, and help you build an impressive résumé of projects that’ll get you that job you’ve always wanted, and in time, will earn you the right to call yourself an expert.