The sad truth about building with AI is that it only works if you're willing to put a lot of effort into planning up front. And planning everything upfront is boring and often simply wrong. As engineers, we learned to use the process of building to steer us.

I am writing a piece on how Wasp's design evolved over time and why it turned out to be more important than we initially thought. Here's the logo evolution, even before we adopted "Wasp" as the name:

People say SaaS is not needed anymore and that LLM chats will soon do everything. In the meantime, real devs are, thanks to AI, building better tools than ever, faster than ever. x.com/MatijaSosic...

The word is spreading quickly. RIP DSL, welcome TypeScript.

El cocinero @_cprecioso is cooking again. Pre-rendering was an appetizer, now for the main dish 🍽️

I'm getting into tmuxmaxxing. Give me your tips and tricks.

Community Day of Wasp Launch Week #12 🐝 Four apps shipping on Wasp right now, across: - video editing (Twitch VOD AI) - UK property tech - Shopify chat - daycare lesson plans Yes, that's the actual lineup. Here's what they built ↓ wasp.sh/blog/2026/0...

GM Wasp nation. It's day #2 of Wasp letting you write your app's spec in TypeScript. We can feel the buzz, but still many more people need to know about it. Time to spread the Waspel.

AI is a crazy, amazingly good autocomplete. And a really bad coworker. The problem is that autocomplete is so good, we keep trying to make it into something more.

As a framework creator & CEO, I'm kinda insulted nobody has slopforked Wasp yet. Cmon its like one prompt. I guess we made it too easy to deploy it anywhere 🤷.

GM Waspeteers. Launch Week opening with TS Spec went great. Super exhausted but also feeling great that it's finally out. Thanks for all the support - we keep going!

Sneak peek 👀

We are live! Join us: discord.gg/kkreB6jP4A?...

You write frontend code. You write backend code. Wasp lets you write a third kind: full-stack code. Pages, routes, auth, jobs, and more, all defined in a single spec that ties your whole app together. And as of today, it's 100% TypeScript. Introducing the Wasp TS Spec. 🐝👇

Prepping the TS Spec launch tweet for Mon. Which one lands the best, A or B?

Old vs new.

"Design your company's culture" they said "It will be fun" they said ( @infomiho testing the new TS Spec on me)

The final days before the launch week are always both stressful and exciting. It's in between "damnit, we should have prepped better" and "can't wait to ship this and see what people think". See you Monday! (event link in comments)

Whoa @martinsos just cooked this one 🥩

Damnit I knew I should have been doing more support myself.

One week from today, Wasp gets iTS new shape (get it?). We said inventing our own DSL was a mistake. Here's what we built instead: Wasp, fully TypeScript-native. Launch Week #12: MeTSamorphosis - kicks off Mon, June 15. See you Monday 👇

Me explaining to my wife why I needed to work late last night: "It's called Telescope, it's a Lua plugin for Neovim, and look what I can do now."

GM. Today we're cooking our next Launch Week. It's been a while. Excited to get it back. Stay tuned.

Just spent two hours testing the final Wasp TypeScript Spec with @infomiho, and I got really excited about it. One of the gamechangers is definitely the ability to split your spec file across multiple files and organize features in vertical units.

Here's my framework for tweeting that got me over 1,000 followers in just 5 years :D. - morning: post about what you're going to do - midday: what you did so far + random thoughts and ramblings - end of day: scramble to finish work and forget to post Full course dropping soon 👀

Wasp's config file is moving from our custom DSL to full TypeScript. What should we call it? If none of these, what's your idea?

For my entire career, the playbook was "ship fast, fix later." Lean Startup. Move fast and break things. Quality was what the "slow" companies did. Now AI can ship in seconds, and suddenly everyone's rediscovering that understanding what you're building matters more than how fast you build it.

GM Waspeteers and fellow hackers. Today on the menu: - Figure out Launch Week 12 deets (very excited about this one, kinda want to make sure we do it right) - Keep plugging away at Wasp rebranding with Martin Let's go!

GM. Rough night, but it happens. Let's build.

I am so back. Thanks, @MartinSosic. Your love letter to Emacs made me rethink my editor (life) choices. Cult > Church.

While the team is plugging away at bringing you Wasp in TypeScript, @MartinSosic and I have more fundamental things to solve. Please help us decide on the future of Wasp:

We have @MartinSosic on design now, too. Amazing how with AI we can finally deliver what we have in our heads. This is gonna look amazing.

Once people start referring to Martin and me as "The Curly Bracket Brothers", I'll know we made it.

Playing around with our new web design. Trying out different options for a subtitle badge --> asked Claude Code to add a picker so I can explore it myself. So cool.

I think it's underappreciated how far simply being nice can go. Everyone wants to work with or just be around people who make them feel good.

Talked to a user. He had an issue, but instead of joining our Discord and asking, he just had Claude Code build a custom script and inject it into his build process. Definitely not the "real" solution, and prob not even needed, but when the solution is so cheap, people will just go for it.

Before and after. It finally feels like we're getting somewhere. Now applying this style to other sections, and polishing the messaging with @MartinSosic further.

Had an issue. Didn't want to explain it to Claude and wait for an answer. Threw a few keywords in google, found a blog post from 2017. Quickly found what I was looking for. Applied it, it works. Felt good.

Logo evolution

GM hackers. I cleared my whole schedule today (almost) so I can grind on Wasp's new design and messaging with Martin for the whole day. I'm super glad we didn't just outsource this part. It takes longer, but feeling it under the fingers and discussing it with the team is so helpful.

Wasp going full-in on TypeScript will make some really cool stuff possible. Stay tuned.

Exploring different positioning options for Wasp. We have both "traditional" engineers and vibe-coders building with Wasp, and we want to make it clear for both audiences. Also, Claude is really cool for building fun stuff like this.

Since we publicly announced that Wasp is moving to TypeScript, we've been getting so much positive feedback. It seems like there are a bunch of folks who've been following Wasp from the start and literally waiting for this moment.

GM. My next thing for the week or so: apply our new design to Wasp's page, and also make it pretty(er). @MartinSosic already put a ton of work into this, especially the messaging part. I will keep you updated.

This is one of the most pivotal moments for Wasp: switching fully to TypeScript instead of our custom config language. It's been a 5-year journey. We kept everything devs came to love about Wasp, while making it look and feel like a regular TS framework.

Homegrown, organic upvotes, $50 only. Open Vibe is currently #2 without any tricks. No thanks.

We launched on @ProductHunt today, and selling has already begun. We do not engage in tactics like these. Check out what we're doing (vibe coding tutor that helps you use real tools and not get stuck - link in comments), and if you like it, support us. That is all.

The best number of followers any programmer can have. Kinda don't want it to go away now.

I often think of Wasp as of Red Hat for web dev. You can always roll your own stack from scratch, the same way you can compile your own Linux kernel. And then maintain it. But when you need to ship for a client, you want the version where someone has already figured out what works together.

I decided to employ an extremely high-tech approach to track my daily tasks. Beats any AI.