mikewittie

4 ms·

1. 1.▲
   by mikewittie 6mo ago

   I’m thinking about building a literate documentation system to address some of the gaps mentioned here. For those who’ve run into similar issues, what gaps did I miss? And what features would you need to see to actually give something like
2. 2.▲
   Literate documentation: treating docs as contracts over system behavior(mwittie.io)

   2 points by mikewittie 6mo ago|1 comments
3. 3.▲
   by mikewittie 6mo ago

   "What the field actually needs is a robust data provenance infrastructure. We need to know where training data came from, how it was generated, and whether it’s been through a model already. That’s a hard systems problem, and it’s not
4. 4.▲
   by mikewittie 7mo ago

   More code written probably does means less understanding per line (or per a more germane metric), statistically speaking. More dilute understanding probably does lead to more failures and longer recovery times. This feels like something bet
5. 5.▲
   by mikewittie 8mo ago

   We seem to think that Genie is good at the creative part, but bad at the consistency and performance part. How hard would it be to take 60 seconds of Genie output and pipe it into a model that generates a consistent and performant 3D enviro