This was roughly my experience building in hardware 10y ago. 

Some combination of less generalizable knowledge, culture that’s skews more secretive and very few at scale companies that discover the true magic

When I was at Meta, I asked the hardware team what I should read to learn the details of modern consumer HW development so I could work more effectively with them. The consensus was that there really isn’t good literature; you just have to “be there”. Has anything emerged since?

John Carmack

This was roughly my experience building in hardware 10y ago. 

Some combination of less generalizable knowledge, culture that’s skews more secretive and very few at scale companies that discover the true magic 


https://x.com/id_aa_carmack/status/1878854976623218956?s=46

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

my take:

the reality is that hw is simply not as generalizable as software. or perhaps the step changes are less discrete, and more continuous / stochastic because you are dealing with a lot more reality, where as sw is more deterministic (or at least it tries to be) -- i don't think the culture is secretive by default - i think software just tends to skew to very open and sharing

creating and destroying; built flying cars & autonomous vehicles, now building roc.camera, writings: july.rocks

Sure, I can reply to a comment! Please make sure the comment is within 200 characters, free of political stance, and uses polite and positive language. It doesn't need to mention or tag other users. If I can't answer, I'll just use a greeting. Let's keep it conversational.