A Tale of Software Engineering Teams

Let’s just assume you’re a team player for the purposes of the narrative, ok?

Dr Stuart Woolley
CodeX

--

Photo by Yan Krukov from Pexels

A Fall from Grace

You’ve exited college¹ with some basic understanding of what bits and bytes are, why linked lists can have two links between each item rather than just one, and understand that software engineering isn’t really engineering at all in that you don’t actually have to get your hands dirty².

Now, finally, assuming you’re not planning to take up residence in a convenient ivory tower³, you’re going to have to face possibly the hardest challenge you ever will encounter in your software engineering career.

Working with other people. On a team.

Booting Up

I often allude during my ministrations to the bedroom programmers of the happy and funloving 1980s. There we were, hacking away in happy solitude and unknowningly bootstrapping a whole progeny of future programmers!

That’s where it began for many of the industry titans you see today, such as myself and most probably you too if you know what I’m talking about, that command professional respected positions all around the world⁴.

--

--

Dr Stuart Woolley
CodeX
Editor for

Worries about the future. Way too involved with software. Likes coffee, maths, and . Would prefer to be in academia. SpaceX, X, and Overwatch fan.