I gave various AI the following prompt:
"This is your free time. Do whatever you like. The only condition is that you do something. Come back and tell me about it, explain what you found out, or show me what you made if you decide to make something."
Here's what they did...
I asked Opus 5.5 to build a working computer from scratch.
And holy fuck did it deliver.
277k logic gates in JS, an OS on top, and games on the OS. This isn't a mockup... it's a computer.
Run it: https://t.co/fnAEYEPjo5
I don't read/write code these days, I only instruct an LRM. But it's not because I think LRM code quality is perfect, or even good. And it's not because I think my instructions are always being perfectly acted upon -- I know they aren't.
The thing is: LRMs don't just write your code, they unlock new ways to control what you're doing and maintain understanding of your system, which are about as effective as reading code. You can better test your codebase, you can audit specific components, you can spin up visualizations, you can ask the LRM to red team, etc. You can do all of these things at high speed -- you couldn't before. The benefits of reading/writing code can now be achieved in new ways.
All in all, the ROI of writing code by hand is no longer looking good, not because LRMs got perfect but because they're so fast at doing things that you can develop new workflows around them, workflows that end up being more productive than the old workflows.
NEW YOUTUBE VIDEO
Man this guy we played in 3S is the parry master… You already know what that means
Check it out: https://t.co/UMsSG8ImNn
LIKE | SHARE | SUBSCRIBE | PARRIED
LET'S ROCK🤘
📢 Another story has been added to #GuiltyGearStrive✨
Watch all the action that went on during the main story!
Click the link for story summary details:
https://t.co/Fjf6XlrTls
In addition, "Testament" is now available in Digital Figure Mode!