Okay I’ve got another hard problem: marinate on this...
How would you solve Conways law for all the open source computing projects?
I talk to a lot of engineers in different layers of the stack and we all know vulnerabilities and bugs happen in between the layers. These are the worst offenders. How do we make our platforms better enable communication between layers of the stack while doing code review?
I’m not just talking for one project, I’m talking from the CPU vendor, firmware all the way up the stack to where your application runs...
So think conways law for the entire open source computing stack... solve that :)
Oh and try to automate, the answer is not simply communicate or docs :)
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to jessie frazelle 👩🏼‍🚀
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!