One week into my "holiday from home" I find an unfinished thread coming back into my thoughts like a bad penny. An unwanted visitor disturbing my peace I hope I can banish through writing: The inescapable spectre of AI.

What is this thread you ask?..

Why I'll be trying to build a Software Workshop instead of a Software Factory.

A Software Factory

The term "Software Factory" is one I've seen thrown around a few times in recent discourse which mainly discusses the concept of automating the production of software. In this model, humans get one of two roles:

  • Factory Architect
  • Software Lubricant

Factory Architect

Within this role a person is mostly involved with designing the shape of inputs and the machinery applied to transform these inputs in the hope of creating the desired software output. We tweak JIRA tickets, select the "right" models, define skills, author knowledge bases etc all with the goal of creating functional, valuable, reliable software at the end!

Software Lubricant

In this role a person can mostly be defined as being "integrated" into the system to cover the gaps where automation is too hard or it is simply missing. Tasks in this role could be things like random quality assurance of AI generated code, jumping in to fix broken systems or steps within the automated flow. You keep things running essentially, you provide lubricant where and when the machinery gets stuck.

So why not build one?

Factories are incredibly efficient systems which are capable of generating predictable quality outputs at a rapid pace. For the right use-case, they are 100% the right answer. But any software professional worth their salt should know this quote by heart:

There is no silver bullet. 

No solution is perfect and a Software Factory is by no means flawless! They face the same issues as real life factories due to the fact they only produce predictable quality, not guaranteed quality.

So, what happens when that bar is non-negotiable? When stakeholders are unhappy that a system which is at least partially non-deterministic, fails, and the best we can offer is another non-deterministic patch on top with the hope it doesn't happen again?

What can we do without losing all of the clear benefits of AI?

A Software Office

Well, let's start by losing those benefits and continuing our metaphor with another type of structure: The Office

The Office Meme

The Factory's much older sibling, an Office, takes a different approach to generating outputs. Whereas a Factory relies on a system of machinery to carry out tasks, an Office relies on structure & hierarchy instead.

Managers set jobs to complete, senior devs handle high level concerns, junior devs are closer to the coalface with the day-to-day. It is the roles and responsibilities within such a structure that transform chaos into order, work into output, ideas into code. (This should all seem familiar!)

And to some extent, this is where most software production has sat for the past few decades. Just as it was for most of human history, it was the same for our field: you simply cannot build a factory until you have machines to put into it.

Those machines exist now, but they are less than 5 years old... We're still figuring this thing out!

A Software Studio

Speaking of figuring things out...

And to some extent, this is where most software production has sat for the past few decades. - me, (moments ago) 

If you've taken the time to read this far, kudos, and if you're still awake enough to have noticed this quoted sentence earlier congrats! If we could not build factories until recently and only "most software production" was done in an Office, what is the gap?

To this I offer "The Studio".

Love it or hate it, like it or loathe it, this is where I am going to put into a box all of the modern agile frameworks and their brethren! Why?

So far we've covered how a Factory places the locus on automation to create output, an Office places the locus on hierarchy, a Studio however places the locus on co-operation. In a nutshell:

It is the team that produces work, not the system or the structure. 

In such a place of work it is the co-operative efforts of individuals that drive results. Typically such a word is normally associated with more creative industries, a collective of artists working together to prepare an exhibition around a theme for example, but I think it's a good fit: A Software Studio

The tools remain the same as in an Office, the work is driven by humans instead of the tools (unlike a Factory) but it is the focus on co-operation that boosts the ability to produce.

As an industry, I think this is something we're still figuring out as we swing back and forth between what works best where and when, but, that's not so interesting for my purposes.

What interests me is that naming something can give you great power to reason about it...

Yeah yeah, where's the AI already?!

We started by discussing the Factory as the most popular term used in discourse, branched into what came before via the Office, and then branched into the "hidden" structure of the Studio - it's time to start tying things back up together again.

We're still learning how to work co-operatively, but, what do you get if you combine a Software Studio with AI? What if you combine co-operation with the speed of AI?

A Software Workshop

Personally, I am led to the idea of a Software Workshop - a place where the locus is on skilled craftspeople using advanced tools to produce outputs. A place where skill, responsibility and awareness of your peers are prerequisites, because, the tools at your disposal are just that powerful.

A Factory seeks to remove the craft from software production. A Workshop seeks to amplify it.

Instead of building systems that build systems like a Factory would, we are building workflows and tools that are used to build the systems our users need. We are building teams that collaborate because they understand and respect that their work can impact the progress of their peers. We are building owners who know what the system does even if they didn't type every character personally.

It is here within this space that I am curious to explore, to take the traditional plan, create and review steps of software engineering and to experiment how we inject AI as a tool to be used rather than a tool to replace.

How will we build a space that promotes craftsmanship, where mastery is amplified and built up instead of replaced?

Conclusion/The Future

All of this comes back to my own personal take on the the silver bullet quote:

There's a solution for every problem and at least one problem with every solution 

How do we build a Software Workshop where developers still own the system they build instead of owning the system that builds systems?

What are the levers we need to pull to optimise for consistent quality without sacrificing all of the speed?

What will we do when the silver bullet we were sold simply won't work in this situation we face?

It's going to be fun exploring this conundrum, maybe I'll be back with more thoughts or findings, maybe I won't, but one thing for certain is I'll be following this path professionally for a while to see what can work in such a future.