Just when I think I cannot see more emdashes, there are more emdashes.
Moving fast in hardware: lessons from lab to $100M ARR
11–20 of 31 posts
Re: Moving fast in hardware: lessons from lab to $100M ARR
#12Re: Moving fast in hardware: lessons from lab to $100M ARR
#13Optimizing for learning/iteration speed is a solid approach that applies just as much to software development.
Re: Moving fast in hardware: lessons from lab to $100M ARR
#14Depends on how much funding you have, your target audience, target vertical, and how custom your hardware is, no? There can only be so many things you can cut and optimize.
Re: Moving fast in hardware: lessons from lab to $100M ARR
#15Fun read but a bit too much fluff? I was a design MechE for about a decade and I’m by no means as successful as the OP. But I have worked on a 5 person design team that had an annual net revenue of 30M and another job where I worked on 25M+ contract with just a team of 2, me and my mentor at the time. End of the day, hardware execution is hard and there’s a ton of product development cycle theories, you just need a c…
[flagged]
Re: Moving fast in hardware: lessons from lab to $100M ARR
#16Fun read but a bit too much fluff? I was a design MechE for about a decade and I’m by no means as successful as the OP. But I have worked on a 5 person design team that had an annual net revenue of 30M and another job where I worked on 25M+ contract with just a team of 2, me and my mentor at the time. End of the day, hardware execution is hard and there’s a ton of product development cycle theories, you just need a c…
[flagged]
That’s why I’m a huge proponent of pushing the idea of engineering discipline. And like any organization, discipline comes from the top to bottom. Coming from bottom to top is just a recipe for disaster and clear tell sign of misaligned objectives between management and the engineers.
Re: Moving fast in hardware: lessons from lab to $100M ARR
#17Can someone in plain English please tell us what this company does? I just see one anecdote after another that’s scattered with feel-good whodathunkit babble. I was anticipating the airplane holes analogy, but maybe I got lucky and missed it.
Re: Moving fast in hardware: lessons from lab to $100M ARR
#18Nice read but falls into a vast reductionist trap, a lot of survivorship bias dressed up as design philosophy or strategic bets. The context of decisions made decades ago != now, people were working under different constraints etc. Trying to frame the avionics example as the "subtractive" innovation is the most egregious, transistors were over 1000x times smaller, weight wasn't even a consideration.
> a lot of survivorship bias dressed up as design philosophy or strategic bets
I wish more people realized this
Re: Moving fast in hardware: lessons from lab to $100M ARR
#19Can someone in plain English please tell us what this company does? I just see one anecdote after another that’s scattered with feel-good whodathunkit babble. I was anticipating the airplane holes analogy, but maybe I got lucky and missed it.
"ClearMotion, a company developing automotive robotics that stabilize vehicle ride and handling"
Re: Moving fast in hardware: lessons from lab to $100M ARR
#20Can someone in plain English please tell us what this company does? I just see one anecdote after another that’s scattered with feel-good whodathunkit babble. I was anticipating the airplane holes analogy, but maybe I got lucky and missed it.
"ClearMotion, a company developing automotive robotics that stabilize vehicle ride and handling"
Thank you!