Swizec's profile picture. Writing Scaling Fast,a book on lessons learned from ~15 years of engineering in tech startups. blog ⏵ http://swizec.com latest book ⏵ http://SeniorMindset.com

Swizec Teller

@Swizec

Writing Scaling Fast,a book on lessons learned from ~15 years of engineering in tech startups. blog ⏵ http://swizec.com latest book ⏵ http://SeniorMindset.com

Pinned

Ignore the framework wars, learn: - data modeling - domain modeling - system design - managing complexity - syncing state - teamwork swizec.com/blog/reader-qu…


90% of production code is just JSON bureaucracy driving crud but to do that reliably at scale takes 400k/year engineers

Bruh 400k/year software engineers don’t get paid to build simple crud apps They build the software that you use that abstracts all the stuff most vibe coders don’t want to deal with You couldn’t vibe code your db, sync engine etc



Wish I was at the remix 3 party today


check this out, live interactive demos of our DNA analysis tools right on the new homepage 🤘 thanks TanStack/Start


wow imagine using a default email marketing template to do a phishing attack

Swizec's tweet image. wow imagine using a default email marketing template to do a phishing attack

Swizec Teller reposted

I really don't think most people appreciate the difference between shipping something in 6 weeks, beating the global competition (first to offer an agent workflow builder!), then fixing up small issues in 6 more weeks. Vs building for 6 months, and no one cares by launch...

OpenAI says that Codex wrote most of the UI code for their their new agent builder the ui is a hot garbage fire. it makes sense now.

benhylak's tweet image. OpenAI says that Codex wrote most of the UI code for their their new agent builder

the ui is a hot garbage fire. it makes sense now.


vibe coding is a tech lead job

If you want your vibe coding to be better, all you have to do is - write detailed specs and technical documents - create tons of automated tests - use old industry standard technologies - code review a lot more - manually QA every detail …maybe I’ll stick to writing code



After DevDay yesterday I am convinced that any smol startup going against OpenAI or building on top of their APIs is doomed. Deadass watched Cursor announce cool stuff coming soon followed by OpenAI going "And today we launched all those same features yay!!" This is a partner…


Me, doing a quarter review: wow I feel so tired what’s going on Me, planning the quarter 3 months ago: I’m so gonna burn out lol this book will kill me 😂


Oh cool with gpt-oss you can run OpenAI models on your own infra. This is huge

Swizec's tweet image. Oh cool with gpt-oss you can run OpenAI models on your own infra. This is huge

"Codex feels more like a true software engineer because it gives so few compliments" 🔥

Swizec's tweet image. "Codex feels more like a true software engineer because it gives so few compliments"

🔥

“A world where building software doesn’t feel like toil” he said to a room full of professional nerds


Bulking and distance are so hard to combine. Heart rate up to 190 (avg 150) and still I’m slow … but I can squat 200 so that’s nice

Swizec's tweet image. Bulking and distance are so hard to combine. Heart rate up to 190 (avg 150) and still I’m slow … but I can squat 200 so that’s nice

I once built trinary logic with meaningful nulls. It was actually pretty good

I trust you more if you use string enums, e.g. `status: 'enabled'`, unless you are 100000% sure that it will only ever be two boolean states



First batch of pre-print copies sent 🤘

Swizec's tweet image. First batch of pre-print copies sent 🤘

Don't grind on something the company doesn't value. Hard work is not rewarded. Outcomes are rewarded swizec.com/blog/the-grind…


“The true productivity gains are the better code quality we made along the way preparing for AI”


Loading...

Something went wrong.


Something went wrong.