
US Navy Vet, ✳️🦇🔊 ex @DK_Marketplace, @VaynerMedia, Summoning @BlueBoxGC. Founder @RealmStriders
Colorado, USA
Joined June 2012
- Tweets6K
- Following950
- Followers1.6K
- Likes14K
Pinned Tweet
For those who don't know me, I spent 7 years in the military, mostly with the Marines as a US Navy corpsman.
I want to share a story that underscores the importance of attention to detail and keeping promises.
#Thread 🧵1/8
I knew this day would come.
Small one off games as promotional advertisement content pieces.
Expect this to increase as cost and speed to produce drop.
I’m here for it. Wendy’s as a brand is in a good spot for it too with their history of posts. Well done to the marketing team. 👏
Become a good director.
"Slop" is work that is low effort and low intent. I'm pro-AI, and anti-slop.
By low intent I mean the ratio of creative decisions being made by you vs by the AI. If the scale tips too far towards the AI, it's not your vision anymore.
But there is so much nuance to using these tools in 2026. You can get very involved, give detailed notes and feedback, make minor changes, and iterate just like you would giving feedback to a human collaborator.
This makes you a director, and an artist.
Doc 🦇🔊 retweeted
the psychology of nft floor prices is deeper than anyone wants to admit.
PhD level game theory
anchoring bias, endowment effect, loss aversion, greater fool, nash equilibrium, veblen dynamics, dilution theory, zeignarik effect...
all of it ultimately measuring one variable:
how many bears does it take to turn into a lambo
Doc 🦇🔊 retweeted
Been thinking a lot about AI disclosure for games, since it's been a hot topic.
Steam requires disclosure for player-facing content created with the help of AI tools, but says efficiency gains from AI development tools aren't the focus.
Let's say I'm making a tree mesh for my game.
Two obvious endpoints:
• I manually model it in Blender. No disclosure.
• I generate it using Tripo/Meshy. Disclosure.
Now let's interpolate from t=0 to t=1:
1) I model the tree, but use a Codex-written exporter.
2) I model the tree, but use Codex-written UV, LOD and geometry optimization tools.
3) I model the tree, but write some scripts, with Codex help, to automate branch placement, leaf distribution, etc.
4) I automate more of the modelling until I've written a procedural tree generator.
5) I design and write my own procedural tree generator, with Codex helping debug and optimize it.
6) I design the procedural tree generator, but Codex writes the implementation.
7) I give Codex reference images, ask it to suggest improvements to my design, then implement those suggestions myself.
8) Same as above, but Codex implements the suggested improvements.
9) I give Codex reference images and ask it to design and implement the generator itself.
10) I use that generator, manually selecting and tweaking parameters until I'm happy with the trees.
11) Codex operates the generator and chooses the parameters, but I review and approve the results.
12) Codex operates the generator, chooses the parameters, and selects which trees ship, without my involvement.
13) I ask Codex to operate Blender directly and create the trees.
14) I generate the trees using Tripo/Meshy.
Under a literal reading, at every point in that list, the player-facing content was "created with the help of AI tools".
At what point did this cross from AI-assisted development into AI-generated art?
Is this going to be the same for everyone?
Doc 🦇🔊 retweeted
Had early access to Genie 4 from @GoogleDeepMind.
This is a fully generated, interactive world from a single starting prompt (environment + character) 🤯
Feels like a massive step forward - you can now prompt to change the world and interact with it. With native audio!
Honestly sickens me.
Humans fighting humans is bad enough. The things I’ve seen..
Man also forces other creatures to do their terrible bidding..
Disgusting. There is no honor in it.
Warhound, the brain child of Ben Lamm and Palmer Luckey, emerges from stealth to genetically engineer dogs for military and law enforcement.
spr.ly/6011BHZNMF
Doc 🦇🔊 retweeted
The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2.
PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.
pstack v0.15.27 ships with a new skill /create-formal-verification-skill!
it's still in beta, and similar to /create-verification-skill, this is a meta-skill that creates a new skill and formal verification suite based on the characteristics you want to verify. for example, you may want to model state machines and systems with concurrency using TLA+, or use kani in rust to check for undefined behavior.
if you're new to formal verification, think of it as mathematically proving properties and invariants (something that must always be true) or "laws" of your system. usually, this means modeling your programs in a separate language like with TLA+ and then running the solver on that spec. newer approaches like with kani and @bendlang take a different approach where there is no separate language: you write kani in rust, and bend in bend (it's also a programming language, and the proofs are written as laws and expressed in its type system).
historically formal verification never reached mainstream status because of the difficulty in modeling and writing proofs. it's quite difficult to model your business requirements and keep them in sync! but i expect that we will see more innovation in formal verification in the future as being able to formally verifiy that the code does what you intended gives your agents superpowers in writing correct software.
in the meantime though, i've been experimenting with modeling our code with TLA+ and have already found several bugs with the skill created by /create-formal-verification-skill.
try it out and let me know how it goes!
Web3 gaming can absolutely make a comeback. Looking to kick this off soon.
Why web3 gaming will make a comeback
1. AI is killing traditional game dev
2. Metaverse is now real
3. Making the game themselves will just be content like making a YouTube video
4. Rapid testing of models both in econ and gameplay
5. No need for vc money
6. Devs and drillers are showing they like game coins tied to larger content like dacity coin
7. Games are more like virtual production studios where it’s like making a tv show. Most people are playing they’re just viewing
Doc 🦇🔊 retweeted
Replying to @TimSweeneyEpic
作りたいのに作れなかった側として言うと、AIでコストは下がっても「最後まで遊べる形に仕上げる」手間は消えなかった。だから黄金時代が来るなら、完成させる粘りが残った人から先に出てくると思う。
This is what alot of gamers that are against AI don't get.
I agree with Sweeney. A golden age of gaming can exist.
We can now build experiences that otherwise would have cost too much to produce.
I've consulted on titles and helped teams rapidly prototype games and mechanics using agentic systems.
You used to have to sink a ton of money into a demo just to see if it works. Now you can have one done in days to a week.
Doc 🦇🔊 retweeted
1️⃣ It’s expensive to live like a king….
2️⃣ Be grateful for the little things in life.
Try complaining about Uber Eats to someone who was homeless at 12.
@curator_doc lived on the streets of East Hastings in Vancouver.
He still closes his eyes in the shower and takes a moment to be thankful he has running water.
His friend was complaining about how expensive food delivery has gotten.
Doc’s response?
“It’s expensive to live like a king.”
Someone cooks your food.
Someone drives it to your house.
You don’t even have to leave the couch.
We get used to that pretty damn fast.
Running water.
A hot meal.
A roof.
There’s a lot to be grateful for before we get to whatever we think we’re missing.
This guy has the mindset you want to follow and he's cooking up somethingt insane.
Give himn a follow!
Electric car…
Cold-gas thrusters…
High-pressure compressed air stored in onboard tanks.
Practically zero emissions.
This is known as the 10th man rule.
If 9 people in a room all agree it’s the responsibility of the last to take a contrarian viewpoint to challenge assumptions and reduce groupthink.
I created a little grokbot that does this on every one of my plans.
Link below.
x.ai/bot/4hOEjB8_4K8jL5CK22W…
Your agent's plan is never its best plan.
It's the one it thinks you'll like.
If you're vibe coding with Opus 5.5, GPT-6 Astra, or Grok Bot, steal these 2 prompts.
After it gives you a plan: "Now argue the opposite. You're a senior engineer who thinks this plan is horribly wrong. What would you build instead? Don't build it yet, just write the full plan with counters to every point you believe is wrong. Then judge both honestly: which plan wins, and what from the counter should we keep?"
Before it writes any code: "Rate your confidence 1 to 10 on each part of this plan's tasks, based on what you've actually verified in code, not assumed. Under an 8, tell me exactly what you'd need to know to increase confidence. Don't do anything yet, we're only mapping and investigating."
Frontier models are trained to agree with you. Making them attack their own plan is the closest thing to a second opinion you'll get from the same model.
Last week this confidence mapping process caught 13 gaps in a plan I almost let my agents run.
Bookmark these for your next session.
Pushing PRs and making code changes with talking to @bot while at the gym just feels right.
The amount of leverage we have at our finger tips..





















