Eva Stratt from Project Hail Mary. Sandra Hüller walking toward camera through an institutional corridor, expression calm and certain. © Amazon MGM Studios.
she saved earth by not asking permission.
i named my prompt library after her.
STRATT.
The #1 beginner mistake: not starting.
You spend all day thinking, perfecting your offer, rewriting cold emails. Mostly you worry what people will think.
But you have no reputation to defend because you have no clients yet.
A young man sitting on a set of brick stairs, holding a Chocomel carton - unbothered, unhurried, already thinking three moves ahead.
the best DX still comes in a yellow carton
#buildinpublic
www.youtube.com/watch?v=nt9j...
www.youtube.com/watch?v=_IK1...
youre already thinking like a systems architect.
you just keep interrupting yourself to write the code.
stop being the bottleneck.
#buildinpublic
Some personal news: I’m transitioning from CEO to a new role as Bluesky’s Chief Innovation Officer! I’m excited to welcome @toni.bsky.team as our interim CEO.
More here: bsky.social/about/blog/0...
The hidden burden of undiagnosed ADHD is constantly inventing excuses in an attempt to explain behavior that you don’t even understand yourself.
PostHog care package on desk with t-shirt, socks, and stickers. Coffee cup in background. First day in the office.
office keys in hand. @posthog.com swag on the desk. jitter juice ready.
this is real now.
#buildinpublic
current project is still in stealth, but it seems the public GitHub history is what got me here somehow. almost feels too lucky.
go with fromstr, it gives you .parse() for free and that’s what people expect. add tryfrom<&str> later if you want .try_into() to work too.
happy new year folks
also ForrestKnight dropped this summary of CLI tools that every linux dev should know.
starts the video saying "about 40 commands", ends it with "actually like 30, cut some in the moment".
that's the kind of unfiltered content i respect.
www.youtube.com/watch?v=XhLM...
Custom-built PC running a fresh Arch Linux installation. My new dev setup for 2026.
treated myself to a new rig over xmas. spent ~3 hours exorcising haunted spanish windows bootloaders.
arch is running. rust and go installed before i even saw the desktop.
we are so back.
Screenshot of an email from startup cofounders explaining how they found me by scraping GitHub profiles for specific technical skills. Key details redacted.
Claude Code analytics dashboard showing approximately 500,000 lines of code generated in the past month.
got an email last year that changed my life.
"we scraped github looking for [X]. your profile came up."
500k lines of code later, i finally understand what 'locked in' means.
2026 is going to be different.
#buildinpublic
The more social media you read, the less attention you have for long form (whether articles or books).
The more short videos you watch, the less attention you have for long videos and podcasts.
Be mindful if you're spending time wisely for all your waking hours.
screenshot of claudecode generating a full ai engine with imports, security models, and near-complete test coverage.
pov: its 2025 and your ai is busy building its replacement
code first, words later.
#buildinpublic
masters nationals this weekend.
PB in almost every event. wanted sub-27 for 50 free, got exactly 27.00 (lane 8). swimming gods have a sense of humour.
months of training done while building in silence. time to ship the ecosystem.
watch this wave.
#buildinpublic #swimming
failed another coding interview last week.
im so bored of hour-long leetcode marathons that reward speed over sense.
so ill keep building this orchestrator for my entire SaaS ecosystem. traceability all green so far.
at least something actually passed.
#buildinpublic
p.s.
SYS-CTL = system controller (whatever you're building - script, component, hook, schema, endpoint etc)
SYS-REQ = specific system requirements (expected behaviour you need to deliver)
helps you identify edge cases at any scale.
save for your next debug #buildinpublic
{SYS-CTL}
{SYS-REQ}
what key architecture mistakes + corrections should be identified to fulfil the requirements outlined above? your design should be driven by clarity, precision, and implementation discipline, producing scalable and verifiable outputs
lol exactly. summers the og chaos monkey. each year seems to slap me with a fresh stress test.
exactly, the stage totally shifts intent.
tofus like “morning routine” build the vibe, mofu/bofu are where the decisions happen. like “best grinder under $100” or “aeropress vs chemex”
a decent mix should keep the journey smooth ;)
still feels like cheating but im not complaining. literally saves me hours on the daily.
@joshwcomeau.com has a gift for making frontend click. his keyframe post (#5) is a perfect example.
as a python/go dev, i love how he makes frontend feel logical. his deep dives + interactive bits really help neurospicy folks like me.
👉 www.joshwcomeau.com/animation/ke...
dev maturity is unlocked when you realise:
1. everything is just JSON
2. github copilot is a goat
3. django is insanely powerful
4. refactor = distractor, fix the bottlenecks
5. keyframes are easy, youre just impatient
4 is a life lesson. 5 hit different.
#buildinpublic
feel you on this. cursor just doesnt fit how i work.
i prefer short lightweight chats with specific context drops. dragging subsystems in one by one, improving consecutively.
while its super convenient just accepting the magic i just enjoy poking at the system until it make sense.
I've been playing with cursor a bit and find it frustrating, even though I only gave it very simple tasks.
It hallucinates icons, doesn't correct them when I tell it to use the real ones & messes up functionality when I just ask it to change UI colors.
How to work smoothly with it?
#buildinpublic
morning espresso for thought ☕
keywords = what people search for: "best coffee grinder"
tags = how your content connects internally: "kitchen/morning-routine/daily-grind"
one targets discovery, the other builds relationships.
completely different jobs.
#buildinpublic #seo
