Sample 2 is not a failure

Sample 2 is not a failure.

Sample 2 is usually exactly the reason you built sample 1.

Hardware development is still a bit odd sometimes.

We draw a schematic and a PCB.

We check everything. We review. We simulate.

And then it can go to production.

Somewhere in the back of our minds we hope it will be perfect straight away.

But that is not how development usually works.

In software we are used to iterating: build → test → change → again.

With hardware, every iteration costs more time and more money.

So we sometimes turn it into one big moment instead: "This has to be right immediately."

While you often develop faster by doing the opposite.

Build sample 1.

Test it.

Look at what actually happens.

Write the findings down in a List of Changes.

And build sample 2.

Not as a copy of sample 1.

But as the physical version of everything you learned from sample 1.

That is why at DeltaProto we do not really believe in:

"Get it right the first time."

But in:

"Learn fast. Change fast. Build again."

Because hardware is hard.

But your development cycle does not have to be.