Clay Tech

"clay-works make things real"

translated from clazytech.com

Experience Builds Crisis Management Ability, Not Just Years Coding

If I had to single out just one thing, it would be crisis management ability.

This is the ability to detect potential risks, correctly assess their probability and severity, and put countermeasures in place beforehand or have them ready — all to a high standard. Inexperienced developers have none of this, and it’s a wall that’s very hard to break through with experience. Note that “experience” here doesn’t mean years of development. It means how many challenges you’ve taken on, and how many failures and successes you’ve lived through.

Crises can be either externally or internally caused.

Externally caused ones are extremely hard to control. A delay in parts delivery that affects the schedule, a sudden spec change from a client, a move by a competitor — your own effort alone can’t fix these. What you can do as crisis management is build in margin: in the schedule, in the budget, in the room for spec changes.

Build in too much margin and you strangle yourself. Projects get shelved, you lose out to competitors, costs never come down. But nothing is more naive or reckless than running a project with no margin at all. A delicate sense of balance is needed here, and that’s something rooted mostly in experience.

Internally caused crises, meanwhile, essentially mean bugs. These ought to be controllable in principle. But I have to add “ideally.” No one embeds bugs on purpose, and most developers release believing “surely there are no bugs.” They release after thoroughly reviewing the spec internally, conducting reviews, and running sufficient testing. And yet bugs still occur. I don’t know a way to get this to zero. No matter how carefully you prepare, some kind of mistake will occur.

Whether you understand that, whether you’ve fallen into idealism, whether you’ve built the habit of always looking at things with a skeptical eye — these things, too, undeniably depend on the degree of your experience.

Incidentally, I don’t trust my own design ability. I’m sure I’ll embed bugs, I’m sure I’ll get some circuit wrong somewhere, and there are surely inconsistencies I’ve overlooked or specs I forgot to pin down in the first place. Because I assume these things will surely happen, I put various measures in place in advance, so that if such a mistake does occur, I can recover with minimal loss.

Because of this, if you look at my schematics, an inexperienced designer will see redundant-looking parts and mechanisms that seem to make no sense, scattered everywhere. Those are my safeguards. And it’s this total ability of mine to keep a project moving forward that I trust.

The content of this post is an excerpt (original text) from the following book. If you’re interested, please get a copy.

The Shape of a Happy IoT Startup

The Shape of a Happy IoT Startup


Originally published in Japanese at https://clazytech.com/2022/09/1143/. Translated with LLM assistance and reviewed before publication.