X : What's the best way of writing a specification for a commodity?
Me : Your test suite.
X : Eh?
Me : Every novel thing starts with a few basic tests, as it evolves it gains more, your product should be built on those test and eventually they should help define the commodity.
X : What if we don't have tests?
Me : Does not compute.
X : Eh?
Me : Fzzz, whrr, fzzz, whrr ...
Me : Your business, hardware and software should have test driven development baked in throughout wherever possible. How do you change anything in a complicated environment without it. Every single line on a map is a relationship, an interface for which there should be tests ...
... those tests define the operation of the interface, they are the specification you hand to another, that you check a product against, that you test a commodity with and then determine the trades you wish to make. Those test should expand and evolve with the thing itself.
X : Yep, but we don't have any. We just test against the specification.
Me : What do you build the specification with?
X : By asking people what they need.
Me : Those are tests, they should be codified, monitored, adjusted and retired.
X : How are they tests?
Me : Build a test for that need, which you will fail because you're not meeting it and build according to those tests.
X : What if they have more needs?
Me : More tests. That's exploration. Is it a planet? Can I breathe on it? etc etc
X : We're in manufacturing.
Me : So is Tesla -
As @djwork77 would say, testing is the core part of what is corporate IP and he is not wrong.
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.