Building the OS for health & fitness · https://teapawt.net/t.co/o6zlgE7Qb1 Building the OS for businesses · https://teapawt.net/t.co/8CKAiuaYFQ DJ in between
Joined February 2013
- Tweets2.9K
- Following505
- Followers647
- Likes10K
I beg your pardon, you’ve been doing what? 🤔🤔🤔
today, we introduce a little mischief to the world.
for four years, we’ve been brewing real brain cells on electrodes to understand how they compute. now, we’ve turned those discoveries into a video model anyone can use.
from 0.5¢ a second, mischief 1 is at least 5x faster than its base and the cheapest image-to-video model on @fal and @OpenRouter. soon to be on @awscloud marketplace.
it’s not a delusion anymore. biocompute is real, commercial and this is just the beginning.
happy halloween.
rule on my team this month: fastest money first
client work, then the app release, then the platform they both run on
everything else waits. including the stuff I'm most excited about
a priority you have to argue about every morning isn't a priority, it's a meeting
did an audit of every agent routine I run
found one that wasn't even on the list
it kept waking itself up and hit the usage limit on its own
the expensive stuff in a business is rarely on the invoice you actually check
16 agents, one shared build machine
the thing that stopped the collisions wasn't a smarter model
it was a table. resource, who has it, what for, since when
book it before you use it, clear it when you're done
most service businesses need the exact same table for their vans
we run sixteen AI agents alongside my team
the agents were never the hard part. knowing who owns what was
same thing that breaks every business running on WhatsApp groups and one person's memory
wrote up what actually fixed it
Most people treat a deload like they failed the week
Then open the next block with ego loads and wonder why the joints negotiate
Pulling back on purpose is still the programme though
Everyone wants the hybrid label
Fewer people want the Tuesday that makes race day feel ordinary
The identity is cheap. The block is not though
People treat the filmed lift like the programme
Then wonder why the unsexy Tuesday session never shows up in their numbers
The camera does not care which work actually moved you though
People front-load the week with the session they enjoy
Then act shocked the one they keep parking on Friday never improves
Friday was never going to save a lift you only meet when you are already cooked though
The warm-up is the first thing people cut when the day gets messy
Then they wonder why the joints feel older than the programme
You do not get to skip the boring prep and keep the heavy work forever lol
Every team has a process that only lives in three people's heads
It works until one of them is off
Then the "simple" job becomes a scavenger hunt
Onboarding debt compounds faster than feature debt though
Most training advice underweights sleep because it is boring
You can nail the session and still lose the adaptation if the night before was chaos lol
The happy path is never what breaks a team
It is the exception nobody owns
Who picks up when the sheet is wrong, the chat is quiet, and the client is waiting
Systems die in the edge cases people refuse to name though
Logging the session is not the same as repeating the stimulus
Adaptation cares what you keep showing up with
Not how tidy the tracker looks on Sunday lol
Most teams polish the workflow and ignore the wait
The ticket moves fine
The real delay is three people who each need one quiet decision
Speed is often just fewer handshakes before yes though
Novelty feels like progress until it isn't
A boring constraint that survives a bad Tuesday is usually more useful than a clever programme you rewrite every Sunday lol
Most ops pain is not a missing tool
It is the gap between done on my side and actually finished
Handoffs are where the system quietly dies
Own the seam or the seam owns the week though
Progress stalls when every session has to feel heroic
Most of the work is quiet volume on days that don't make a story
The body adapts to what you repeat, not what you romanticise lol
The calendar fills with status meetings when nobody writes the decision down
Ticket moved
Slack reacted
next state still unclear
Written ownership beats another sync every week though