Foolish is he who builds his house on an outdated tech stack

This was originally scribbled, in haste, in April 2015, where it has sat, to be published now without change.

Production works.

Production pays your wage.

Don’t fuck with Production.

In recent months I’ve been noticing that what I thought to be true is not necessarily the case. There is a certain belief within our industry that while ‘new is awesome’ new should also be feared, new is unknown, new is untested, whereas Live is – that – Live. We know what it does, we know its problems and its limitations, and more importantly it’s been proven and is currently responsible for everything that is going on.

Burning it all and starting again is simple when you have no vested interests, when you’re not making money, when you’re still looking for that breakthrough. But, once that has happened, you can’t be scared to re-write, to re-build, to retread old ground, and potentially kill the goose.

We work in an industry that proclaims desires to fail-fast, to pivot, to constantly improve, but is also terrified of bucking the tread due to our continual reliance, nay – obsession, with hockey sticks. We tweak, we change, we iterate, and we lurch based on hunches and hopes, on superstitions and gut-instincts towards what we believe will work, and if we’re fortunate enough to get the right thing at the right time we end up being one of the ten percent that ‘succeed’ we probably didn’t get there by a single plan, an single vision, and a single tech view that took us from launch to exit in 19 months.

Most of us have changed; most of us have had bad ideas; have wasted time, effort, and development resource; we’ve wasted money, hardware, Clouds, and careers on foolish notions and frankly terrible thoughts (I’d in fact put a serious amount of cash on the claim that virtually no one has ever got it right first time) and if, when, we do finally gain traction, we need to – eventually – undo all the errors we made.

A tech stack is exactly that, a stack.

Stacks are inherently disorganised, messy,

Fuck Your Good Idea

This was originally scribbled, in haste, in May 2015, where it has sat, to be published now without change.

The road to hell is paved with good intentions, or so the saying goes, and never has this been truer than in software development. Everyone knows best, everyone fights their corner, and everyone stops anything actually being achieved. The irony of this post is not lost on me, my intent is something different, I’ll concede judgement to the reader, but I’m likely to fail.

Clarity in vision, with the supporting determination and stubbornness, is what is required to inform people that their idea is not just misinformed, it’s actually detrimental to the continuation of the company.

Everyone champions ‘fail fast’ and in the very next breath caveat its rules, instead of really trying and failing, we continually tinker and delay for months until we have a perfect test and so we have too much invested to allow ourselves to objectively fail. We lose our vision, we lose our sense, we don’t want to watch our baby suffer. We shield ourselves from our possible failure, only to fail even harder.

We are human, we think emotionally – and that is why we are ineffective.

If only we could burn it all and start again.

Baggage is a part of life, it’s a part of love, and it’s part of creation – you will be bias to your own opinions, dismissive of others, and, well, we’ve all heard of “it’s not a bug, it’s a feature”.