Andrei Roman

I don't want to make fun of Anthropic on account of how they vibe coded themselves into this situation... I just want to make a few points: - AI models still have limited context - We still have limited tools - There is no magic blog.bijup.com/missing-links-…

Anthropic accidentally leaked their entire source code yesterday. What happened next is one of the most insane stories in tech history. > Anthropic pushed a software update for Claude Code at 4AM. > A debugging file was accidentally bundled inside it. > That file contained 512,000 lines of their proprietary source code. > A researcher named Chaofan Shou spotted it within minutes and posted the download link on X. > 21 million people have seen the thread. > The entire codebase was downloaded, copied and mirrored across GitHub before Anthropic's team had even woken up. > Anthropic pulled the package and started firing DMCA takedowns at every repo hosting it. > That's when a Korean developer named Sigrid Jin woke up at 4AM to his phone blowing up. > He is the most active Claude Code user in the world with the Wall Street Journal reporting he personally used 25 billion tokens last year. > His girlfriend was worried he'd get sued just for having the code on his machine. > So he did what any engineer would do. > He rewrote the entire thing in Python from scratch before sunrise. > Called it claw-code and Pushed it to GitHub. > A Python rewrite is a new creative work. DMCA can't touch it. > The repo hit 30,000 stars faster than any repository in GitHub history. > He wasn't satisfied. He started rewriting it again in Rust. > It now has 49,000 stars and 56,000 forks. > Someone mirrored the original to a decentralised platform with one message, "will never be taken down." > The code is now permanent. Anthropic cannot get it back. Anthropic built a system called Undercover Mode specifically to stop Claude from leaking internal secrets. Then they leaked their own source code themselves. You cannot make this up.

Which direction should I take this game engine? zapengine.bijup.com Make an educational games platform for kids with sims for their classes? Or an arcade games platform to compete with Apple Arcade?

@Dexerto So they want to compete with ME? They don't know what's coming :-) I even have running demos zapengine.bijup.com They run fine on rpi5 but really shine on a MacBook with EDR display

Toyota's own video game engine is officially in development The open-source “console-grade” engine 'Flourite' is being produced by their subsidiary Toyota Connected North America

@ryolu_ Ai solves writing code fast and proves this was never the problem - it was just the bottleneck. The real problem was always systems thinking. good professionals were developing systems thinking during writing code. And some people learned it without writing code

software is still about thinking software has always been about taking ambiguous human needs and crystallizing them into precise, interlocking systems. the craft is in the breakdown: which abstractions to create, where boundaries should live, how pieces communicate. coding with ai today creates a new trap: the illusion of speed without structure. you can generate code fast, but without clear system architecture – the real boundaries, the actual invariants, the core abstractions – you end up with a pile that works until it doesn't. it's slop because there's no coherent mental model underneath. ai doesn't replace systems thinking – it amplifies the cost of not doing it. if you don't know what you want structurally, ai fills gaps with whatever pattern it's seen most. you get generic solutions to specific problems. coupled code where you needed clean boundaries. three different ways of doing the same thing because you never specified the one way. as Cursor handles longer tasks, the gap between "vaguely right direction" and "precisely understood system" compounds exponentially. when agents execute 100 steps instead of 10, your role becomes more important, not less. the skill shifts from "writing every line" to "holding the system in your head and communicating its essence": - define boundaries – what are the core abstractions? what should this component know? where does state live? - specify invariants – what must always be true? what are the constants and defaults that make the system work? - guide decomposition – how should this break down? what's the natural structure? what's stable vs likely to change? - maintain coherence – as ai generates more code, you ensure it fits the mental model, follows patterns, respects boundaries. this is what great architects and designers do: they don't write every line, but they hold the system design and guide toward coherence. agents are just very fast, very literal team members. the danger is skipping the thinking because ai makes it feel optional. people prompt their way into codebases they don't understand. can't debug because they never designed it. can't extend because there's no structure, just accumulated features. people who think deeply about systems can now move 100x faster. you spend time on the hard problem – understanding what you're building and why – and ai handles mechanical translation. you're not bogged down in syntax, so you stay in the architectural layer longer. the future isn't "ai replaces programmers" or "everyone can code now." it's "people who think clearly about systems build incredibly fast, and people who don't generate slop at scale." the skill becomes: holding complexity, breaking it down cleanly, communicating structure precisely. less syntax, more systems. less implementation, more architecture. less writing code, more designing coherence. humans are great at seeing patterns, understanding tradeoffs, making judgment calls about how things should fit together. ai can't save you from unclear thinking – it just makes unclear thinking run faster.

@ryancarson After a month using claude code on 4 separate projects I was becoming the bottleneck and I was thinking of using @official_taches 's GSD. I will compare your approaches. I also made use of @Steve_Yegge 's beads and trying to integrate my own github.com/andreirx/FRAKT… for context.

I’m open-sourcing the core. I believe technical agencies should own their infrastructure, not rent it. If you are tired of the WordPress roadblock and want to see what a Serverless CMS / Agency OS looks like, check it out: amodx.net hosted on AMODX

It is going better than expected. The friction is gone. We aren't fighting the tool anymore; the tool is doing the heavy lifting. The "Context Engine" holds our strategy, and the AI Agents execute the grunt work. We just steer.

WordPress is dead to me. If it works for you, more power to you. Keep shipping. But when I started building my own marketing engine from scratch, I found the legacy stack was a roadblock, not an enabler. I needed speed. I got plugins. So I decided to build my own way out. 🧵

Perfect for: ✓ Technical agency owners managing 5+ sites ✓ Developers tired of WordPress maintenance hell ✓ Teams wanting infrastructure ownership, not rental ✓ Projects where security is non-negotiable ✓ Anyone who codes and values architecture over plugins

Every AMODX deployment = 99 client sites per shard. One DynamoDB table (single-table design). One Lambda function (tenant ID routing). One CloudFront distribution (domain mapping). Deploy once, onboard clients via admin panel. No new infrastructure per client.

Spent a day scanning WordPress discussions on Reddit. Three recurring questions: "Why does every security plugin still leave us vulnerable?" "What CMS works for clients who refuse WordPress?" "How do I scale 10+ client sites without maintenance hell?" The answers reveal...