It's 2026, this is being built, rather than being filed under 'what if?'.
It's 2026, this is being built, rather than being filed under 'what if?'.
I have got a plan for this. I'm building something personal which happens to expose API access with the express purpose of enabling bots to play a game with restrictions. If I had a network at all, I'd release the design spec for the bots and give everybody 24 hours to build it and battle for Elo.
'Are there any gotchas we're missing here?' seems to work for me at almost every stage from planning to review. Opus 4.6 at least seems to have a pathological fear of missing gotchas. It's magic.
'Enranging a relationship' is pure linkedin speak, it's just from next year.
It's never been quicker to ship a money-hole than in 2026! Jump in now, before it gets even faster!!
Ha. That's a much more organic version of a concept I was playing with in therapy earlier late last year.
For me, 'Where is my mind' is usually a vector. I only have cognitive space for that.
Maybe what your graph gets comfortingly wrong is assuming that reality has any place at all on the graph.
'No need to show me the weights when I can see your biases in that navbar. We are *not* aligned.'
We are in the era of Software-as-a-Snack.
ASCII-formatted text explaining Markdown structure. Text and source follows: ``` rules/ ├── core/ # Always loaded (10 files, ~10K tokens) │ ├── hard-walls.md # Never-violate constraints │ ├── user-profile.md # Proficiency, preferences, pacing │ ├── intent-interpretation.md │ ├── thinking-partner.md │ ├── writing-style.md │ ├── session-protocol.md # Start/end behavior, memory updates │ ├── work-state.md # Live project status │ ├── memory.md # Decisions, patterns, open threads │ └── ... ├── shared/ # Project-wide patterns (9 files) │ ├── file-management.md │ ├── prd-conventions.md │ ├── summarization.md │ └── ... ├── client-a/ # Loads only for Client A files │ ├── context.md # Industry, org, stakeholder patterns │ ├── collaborators.md # People, communication styles │ └── portfolio.md # Products, positioning └── client-b/ # Loads only for Client B files ├── context.md ├── collaborators.md └── ... ``` from Reddit https://www.reddit.com/r/ClaudeCode/comments/1rhe89z/i_split_my_claudemd_into_27_files_heres_the/
Hierarchical .md files: Better than one flat file, but I don't think this will scale well, and I suspect we will soon think (this example is from a Reddit) these files would benefit from runtime interpretation before exposing to an LMM.
I go 'everything in a VM and who cares if it burns down the building'. I have a project built that can spin up arbitrary VMs, and host a basic git server on my dev machine so they can communicate meaningfully.
If that's the sort of sandboxing you're talking about?
2026
Fantastic, actually. Surprising, too.
What's screaming at me though is the feeling that 'I bet language/LMM fit depends strongly (if not oddly) on the project.' and also 'I bet with Opus 4.6 it probably doesn't matter.'
Always has been. There just used to be so much admin that it was difficult to see it.
(thinking in the board game sense of 'there's a good game in here, but there a LOT of admin in the way of it.')
...and in doing so, to....oooh....I remember why I left that one open now!
PoV: It's 20 minutes and 27 open tabs later and you're reaching for a new tab...
🎈
I guess what I'm saying is while we're all 'we've seen the future!', but ever since we got the steam engine, the future's been really quite short.
Obviously, that could have been 'and then someone invented the telegraph'.
Looking at these charts, AI's like railways in the 19th Century. The tech is good. We need more of it. Everyone's raised a bunch of cash. Some people will lose their shirts. Some other people will flat-out *own* the main national comms links. Game over. And then someone will invent cars.
Claudes can state but can’t argue. Unlike like my youngest (real) child, who once claimed he was calling the police to send me to prison because I offered him supper instead of yoghurt.
...or they do, but they don't think they do. So, OK, I'm not a programmer, I'm a parent.
The Claudes don't need me anymore.
instinctively agree, but can I understand at what level you’re talking about? I think there are plenty of reasonable ‘do not give toddlers guns’ rules out there, for instance.
Given he's so prickly on language, he *must* know that by definition it's not abortion after a child is born, so this *must* be a joke.
It's a bad one.
I've probably made worse.
So, it may not be 'big R' Reality, but it's also real for me right now.
Macro, sure, but it's literally what I'm doing this week as opposed to what I was doing last year.
'Now I get to build a whole software ecosystem around a tiny problem, and, actually, what *do* I want to do tomorrow?' is so much better than 'Sorry, I can't play right now, I'm debugging Fourier transforms'
Coding in 2026.
*Buy in* matters so much more than *structure*, because there are many ways to learn a thing, but if you can achieve buy-in by letting the structure be to design a structure we can buy in to…that’s a risk.
The story is good because life’s about the shapes of the risks we take.
Get out of his head, you're flirting with Chaos!
This is the British Way.
Thank you. ❤️