3 ms·

but demanding to be behind the wheel and understand all the code will affect velocity compared to other teams that are utilizing AI to the max

• Moonye666 6mo ago
  [flagged]
• hgomersall 6mo ago
  Well yes, if a team doesn't bother to understand the code, that's certainly quicker.
  • LeCompteSftware 6mo ago
    "Yes they crashed into a wall and all died, whereas you steered around it, but you must acknowledge that they crashed twice as quickly as you didn't crash. If you were driving their car, you would have just slowed them down." People should have read to the end of "Building a C compiler with a team of parallel Claudes"[1]: The resulting compiler has nearly reached the limits of Opus [4.6]’s abilities. I tried (hard!) to fix several of the above limitations but wasn’t fully successful. New features and bugfixes frequently broke existing functionality. "tried (hard!)" is very ominous. I wonder how Mythos would fare. Presumably it would get further, maybe much further. But I strongly doubt the "frequently broke existing functionality" problem was solved. Eventually humans have to understand the most difficult parts of the code. Good luck with that! [1] https://www.anthropic.com/engineering/building-c-compiler https://www.anthropic.com/engineering/building-c-compiler
• neonstatic 6mo ago
  What good is "velocity" if no-one understands the direction we are going and how we are going? Sounds like a recipe for disaster.