Maik Schreiber retweeted
"Why should I use T3 Code instead of Claude Code or Codex?"
Short answer: T3 Code is way better for developers.
Long answer:
Maik Schreiber retweeted
SIR PATRICK STEWART (1940-2026)
Before everything else, Patrick was defined by being born and bred in Yorkshire, the proud county in the north of England which he loved to the end. You could hear it in his accented voice and in the stern honesty with which he told you what he thought and felt. Yorkshiremen have no truck with half-truths or avoidance of big issues. He wore his heart on his sleeve, which made him a man to rely on, to admire and in my case, love.
We first met as ambitious young actors with the Royal Shakespeare Company half a century ago but we weren’t in the same productions. My first strong memory was a few years later, meeting him in the street in central London when he told me about an offer to take over a leading part in 'Star Trek'. “But Patrick think of your stage career in the UK. Do you really want to risk—getting lost in Hollywood for years and years?”. Well, he took the risk and thank goodness for us all that he did for not just his devoted Trekkies but film and theatre audiences, who marvelled at his using international celebrity to star in a string of cinema successes ('X-Men' of course) and in great classical plays by Shakespeare, Ibsen, Arthur Miller, Peter Shaffer, Pinter and Beckett at Stratford-upon-Avon, in London’s West End and on Broadway.
America was his adopted home, where he met his adored Sunny who has cared for him through sickness and health, through thick and thin. But he never forsook his origins: and the proudest achievement of the most respected and beloved actor of his generation on either side of the Atlantic, was his appointment as Chancellor of Huddersfield University in Yorkshire.
His farewell performance in 'Avengers: Doomsday' is yet to be seen.
Ian McKellen 29 October 2026
Photo: University of Huddersfield
Maik Schreiber retweeted
All of us at Marvel Studios are deeply saddened by the passing of Sir Patrick Stewart. Sir Patrick brought Professor Charles Xavier to life with extraordinary grace, intelligence, and humanity, defining the character for generations of fans, from "X-Men" to "Logan" to "Avengers: Doomsday." He was a singular talent, a generous collaborator, and a true gentleman. Our hearts go out to his wife Sunny, his children, his friends, and the countless fans around the world whose lives he touched with his art.
Maik Schreiber retweeted
I see a lot of people expressing shock and sadness over BioWare shutting down. And I get it.
But here's the uncomfortable truth:
The BioWare that made Baldur's Gate, Neverwinter Nights, KOTOR, Dragon Age: Origins and the original Mass Effect trilogy had largely ceased to exist long before yesterday's announcement.
BioWare's decline began around the time the doctors left and much like what happened at Blizzard, most of the original talent responsible for building those legendary franchises had moved on years ago.
What remained was the brand. The IP. Basically just the name on the building.
But a studio's name doesn't make great games. Insanely talented people do.
And that's the lesson our industry somehow keeps refusing to learn.
The people who built those studios, who poured their blood, sweat and tears into establishing their creative identities were the actual assets. Their experience, their taste, their leadership, their ability to recognize what made a game special in the first place was always the thing that mattered, not the brand.
You can't simply replace those people, keep the logo on the door and expect the magic to continue.
Yet, that's precisely what publishers have been doing for the past 10-20 years.
They've spent billions acquiring studios and IPs, seemingly under the assumption that the creative output would continue regardless of who was actually making the games.
And when the original talent inevitably left, the remaining teams were expected to fill shoes that were often impossibly large, without necessarily having the experience, leadership or creative vision required to do so.
And... the results speak for themselves.
I think we'll eventually look back at the COVID-era acquisition frenzy as one of the most destructive periods in the history of our industry.
Publishers were buying studios left and right, paying absurd valuations mostly just to secure IPs... and developers were often all too happy to cash out.
At Moon Studios, we got quite a bit of crap for refusing to sell when seemingly everyone else was getting acquired.
I remember telling our team back then that I'd seen this movie before.
The exact same thing happened in the 90s, when EA went on its acquisition spree.
Studios were bought, their founders and creative leaders gradually lost the freedom to make the games they believed in, the original talent became frustrated and left and eventually the studios all became a Ship of Theseus.
History doesn't repeat itself perfectly, but it sure as hell rhymes, and that's exactly why I never wanted Moon to end up in that position.
And I don't think we're even halfway through the ultimate fallout of the latest acquisition frenzy.
There's going to be a very rude awakening for quite a few publishers when they discover that the studios they acquired for billions are worth a fraction of what they paid. And that shoving ideology down peoples throats ultimately came at a cost that they didn't quite grasp.
They didn't actually buy the creative vision, the institutional knowledge or the culture responsible for making those studios successful.
They bought the names, the buildings, the IPs and whatever teams happened to be there at the time.
But those things don't matter at all.
You can buy a studio. You can buy its IP. You can even buy its entire back catalogue.
But you can't buy the magic that made those games special in the first place.
And the sooner our industry understands that, the better.
Maik Schreiber retweeted
The number of times I’ve seen software engineering being discounted is insane. Every time a new technology comes around, some people say programming is over. AI is just the latest chapter of that story.
But software engineers have been adapting to technological shifts for their entire careers ( unlike many other industries).
The tech stack we use today looks almost nothing like what it was when we first started programming.
AI agents fundamentally change how we build software. But we’ve been making that adjustment forever, and this is not that much different.
At the same time, the fundamentals of software remain relevant and critical.
In 1994, software was dead. People told me programming was for nerds and that I should become a doctor or a lawyer instead.
In 2004, software was dead. People told me that someone from India would take my job for $5/hour.
In 2014, software was dead. People told me that no-code was going to kill every job and doom my career.
In 2024, software was dead with Devin, Windsurf, Copilot, and OpenAI o1.
We kill software every 10 years, and yet the demand for good Software Engineers has never been higher.
Maik Schreiber retweeted
I’m tired of worthless stand up meetings. Most people share useless info.
“I’m working ticket 123”.
That’s what the Kanban board is for.
Standup is for *novel* info.
Maik Schreiber retweeted
Replying to @LeoBuilds_
Software engineers are supposed to do exactly what we’ve always done. Ensure that the composition and structure of the system is robust and maintainable and that the behavior of the system properly serves the needs of our users.
This requires engineering discipline. It need not require detailed reading of the code; just as using compilers does not require detailed reading of the binary.
Maik Schreiber retweeted
What is the value of a software engineer anymore?
Many new grads and juniors ask me how my work has changed as an engineer.
What is the difference between what I did in 2021 and what I do today?
Here is what changed.
Assume all the planning is done and I know exactly what I need to build.
In 2021
60% of my work was spent coding.
Pressing one letter at a time on the keyboard with my little fingers, one after another, for hours straight.
Like a caveman.
20% was spent researching.
Googling things about the language, framework, patterns, and protocols, and reading other parts of the codebase to understand how things worked.
20% was spent testing and reviewing.
This was easier because I typed every letter by hand, so I already knew almost everything that had changed.
In 2026
5% planning the overall design and structure before agents start writing.
40% reviewing agents’ code and comparing it against the design.
5% requesting design and code changes from the agents.
40% understanding and validating the implementation, making sure the code actually does what I think it does.
5% talking to other people about related changes.
5% testing and doing final reviews.
Conclusion
I’m no longer a coder or programmer.
I’m more of a code reviewer and designer.
The value I brought to the table in 2021 was the code.
I was one of the few people who could write it.
If you brought a random stranger in off the street, gave them the requirements, and asked them to build what you wanted, they couldn’t do it.
In 2026, I’m no longer doing coding.
If you bring a random stranger in off the street, give them the requirements and Codex, they can produce “working” code.
So what is my value?
Why would you pay me thousands of dollars?
I have been asking myself that question a lot recently.
And here it is.
Think about a company that pays for a piece of software.
They pay because that software does something valuable for their business.
In some ways, their business depends on it. And that dependence rests on two claims:
1: Behavior: What the software claims to do and actually does.
2: Potential: What it will continue to be able to do in the future through upgrades, vulnerability fixes, new features, and changes.
If that software doesn’t do what it claims, you can’t depend on it.
You need guarantees. You need a solid foundation you can trust and build your business on.
On the other side, if you sell software, you need those same two things from your engineers.
1: Behavior: You need them to guarantee, as far as reasonably possible, that the software behaves the way it is supposed to.
2: Potential: You need them to ensure that the software remains flexible enough to improve, change, stay maintainable, and stay secure.
This is where I come in as an engineer.
That stranger off the street who can “build” using Codex isn’t capable of guaranteeing what they built.
I can.
No guarantee is 100%, but we want to get as close as reasonably possible.
Engineering is the process of increasing that confidence. Good engineers can guarantee more.
The reason I spend most of my time reviewing agents’ code and design is to understand what the system actually does and change it when it does something wrong.
Because I understand it, I know what can happen, what will not happen, and what may happen. I can communicate that, and you can depend on what I tell you.
Hence, my value is that I can take responsibility for what I build.
I can tell you what it will do, what it can do, and stand behind those claims.
And you can go ahead and tell your customers what our product can do.
Maik Schreiber retweeted
“Oh you’re having trouble with Claude, you must not be pure of heart”
This is like literally Calvinism and the concept of the elect
And it is also bullshit
AI is a tool to be used by humans, and if the human has to contort themselves into some weird shape to use it, then it is not a good tool
The AI should adapt to the human, not the other way around
Maik Schreiber retweeted
Replying to @mattpocockuk @unclebobmartin
The bathrobe, its owner, and their interviewer:
youtube.com/live/zcLPGC-tvgk
Maik Schreiber retweeted
mattpocock/skills v1.2 is out!
We're now the 19th most-starred repo of all time. 13.5m downloads on skills.sh. Thanks for your support!
Here's what's new:
- Docs: the community's biggest ask. Every skill documented, with explanations of the main flows + troubleshooting
- Claude Plugin: install via Claude's official marketplace
- Codex Support: full Codex support via agents/openai.yaml files
Updated Skills:
- /grilling now asks you questions in rounds, not one-by-one
- /prototype now uses HTML instead of a TUI for building logic prototypes - easier to share and far richer
- /writing-for-agents renamed from /writing-great-skills, use it for ANYTHING your agents read (AGENTS.md, system prompts, docs)
New Skills:
- /wizard: tired of provisioning infra? Get your agent to build you a TUI to walk you through it
- /to-questionnaire: hit a grilling question you can't answer? Turn the session into a doc you can walk through on a call with a colleague
- /wait-what: no idea what the model said? Refocus it in your domain language and simplify with ASD-STE100
Full changelog + docs below. Video soon!
Took us a minute, but stacked PRs are now on GitHub 🥞
github.blog/changelog/2026-0…
We are committed to pushing the model frontier across cost efficiency, capability, and speed.
Starting today, we are reducing prices for GPT-5.6 Luna by 80% and GPT-5.6 Terra by 20% , and offering a faster option for GPT-5.6 Sol in the API.
Luna and Terra’s lower prices are reflected in how usage is counted in Codex and ChatGPT Work, so your usage goes further.
Maik Schreiber retweeted
/wayfinder lets you plan your most ambitious projects ever
You can give it a destination and it will:
- Figure out the frontier of things that can be decided now
- Uncover the route ahead as you go
- Research, prototype, and discuss with you
- Maintain a map in an issue tracker of your choice (GitHub, Linear, etc.)
It's revolutionised how I plan coding work - and I'm even using it outside of coding.
Get it for free:
npx skills add mattpocock/skills
Here's the breakdown:
Maik Schreiber retweeted
Some people seem to be surprised that an old geezer like me could adapt so quickly to the newest tech.
The thing is, I've been a programmer for over 60 years. And every single year brings another adaptation to new tech. Adapting to new tech is what we programmers do on a regular basis. Why would I stop now?
Maik Schreiber retweeted
📣 The moment is here. 📣
TypeScript 7 is officially released! 7️⃣
devblogs.microsoft.com/types…



























