Did some digging as I was curious about the security implications with respect to utilizing MCP. Made some interesting findings! What are your personal takes? Is it `MCP to the moon!` or do you guys think users should be pumping the brakes?

Opus 5.5, Sol 6, fable 5.1, Astra 6. Models are being released now faster than anyone can keep up. The online dialogue gets all excited every few weeks when a new one is announced, but the reality is we’re several generations deep into models that can already reliably do almost anything you can think of. The beauty of ICM is that you aren’t tied to any model but I’m wondering how folks are navigating having so many options at their fingertips. I’ve started letting my sessions decide what to use as I can’t keep up anymore. How are you choosing what to use? Leave a comment below 👇

Finally giving my view on JEV in my classic history and fundamentals fashion but... This one is a little different. It's my first time making a fully animated, pixel art video, and I'd honestly love to know what you think of the style. Should I make more like this? I made an ICM that fully automates most of the process i was able to get this video built in about three or four hours. Talk about a fun animation style right? Might redo a bunch of the videos in the classroom with this.

This is the fear every builder carries around right now, and in some ways it’s earned but in other ways, it just means you were building at the wrong abstraction. In most fields, once you get past the entry level, there is no such thing as "best". There’s no data sheet for it. Ask ten senior engineers to name the best code and you get ten answers, and every one of them will be right by their own lights. A guy named Gerald Weinberg wrote a whole book about this in 1971, The Psychology of Computer Programming. Programming was never really a technical activity. It’s a human one. What counts as good code gets decided by people, arguing, reading each other’s work, carrying their scars from the last project into the next one. The machine ran either version fine. The “best” part happened entirely inside someone’s head. And that’s true up and down every high level field I’ve worked in or near. The best compliance review, the best sales call, the best way to structure a deal. None of it sits in a manual because none of it is a fact. It’s a position, formed by one person, over years, out of everything that went wrong in front of them. Which is exactly why a model can’t converge on it. You can train on every line of public code ever written and you still won’t get Weinberg’s room full of engineers to agree, because there was never an answer to find. There were only people, each with a working theory of good that they’d bet their name on. So when a member in this community sits down and writes their package, they aren’t transcribing the industry standard, although many may do that in the first pass. They’re publishing their opinion of best, the one they built by doing the job, and a company that licenses it is buying that opinion on purpose just like you would a salary. That’s what hiring always was, if you look at it straight. You never paid a person for the facts they knew. You paid for their particular theory of how the work should go, and now that theory has a format it can live in.

I kept trying to figure out the right folders, files, agents, and structure first. Now I think the better starting point is: What is something I already do repeatedly that I wish worked the same way every time? Once I understand the actual work, what goes in, what decisions happen, and what "done" looks like, the structure gets much easier. New rule for myself: Don't start by designing an ICM. Start with a real piece of work that already hurts. What was the first workflow where ICM finally clicked for you?