I've been talking (with my friends) about how all development is 'fear driven development' for quite a while now.
Of course I don't mean just software development, but the way it manifests in software is instructive.
The different fear responses range from formal methods to FOMO but in general we latch onto something as a source of comfort.
Conway's law expanded to how you communicate with yourself.
Frankly, I'd be outright horrified if say the people responsible for autonomous driving weren't anxious about mistakes, since I'd either have to assume that they just didn't care or - perhaps even worse - do not realize the potential consequences of their actions.
Do you have examples of fear-driven and non-fear development approaches? And what flavors of "non-fear" development are possible?
Look at all the early software pioneers do they look like they were suffering from constant anxiety vis how productive they have been for decades?
Can you please clarify?
Conway's law is an adage stating that organizations design systems that mirror their own communication structure.
In a sense, your own self is an organisation whereby we communicate with ourselves in fearful and anxious ways, so the systems we build can only be a reflection of that fear and anxiety.