Round 1 sold out, Round 2 just opened  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏  ͏ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ ­ 

Hi there,

Yesterday I bet our CEO, Alex K the 150 seats wouldn't sell out before midnight. They were gone before ten, so coffee's on me. Round 1 is closed, and $199 is the rate now.

Get access to Unlearn.dev →

Every launch we've done for Unlearn has moved faster than we expected, and yesterday was no exception. We always end up asking ourselves the same question after one of these...

What is it about Unlearn that keeps doing this?

We don't have one clean answer, but we have a few things that keep coming up when we talk about it.

The first one is that this is a really weird moment in our industry... it's loud in the wrong way.

Half the takes say developers are finished. The other half says prompt-craft is the whole game. Neither matches what developers actually feel. The work that's left is the senior work, the judgment calls and the architecture reads, the feel for when AI sounds confident but something's still off.

Maybe that's why most current developer training feels strange to us. It either pretends AI doesn't exist, or it acts like prompts are everything you need to learn. Two different doors, same dead end. Neither one is what you'd want for the developer planning to do this for years.

So we built the third door, and this is the part we actually love talking about.

The eight workflows are almost all in. They teach how you spec, build, review, and ship with AI without it falling apart. And that's only the foundation.

Screenshot of the first Workflow in Unlearndev

Beyond the workflows, we're building the rest of what makes a great developer now, the architecture taste, the product judgment, the calls about what to build and what to skip, the leadership instincts when AI's doing half the work.

And not as theory, but as practical lessons, skills, prompts, MCP servers, and templates that install into your stack the same week you pick them up. As paths that personalize to your context instead of someone else's. As content that meets you between commits, not a four-hour course you'd have to block your weekend for.

That's the version of the developer the next ten years belong to, whether you're already there or quietly worried you're slipping. The hundreds of developers who joined so far saw it, and we'd love you to walk this with us.

Get access to Unlearn.dev →

Alex GS
Tech Education Lead

Unlearn.dev is proudly part of BitterBrains - Making Developers’ Lives Easier

You are currently subscribed to the email address adam@podam.pl
Unsubscribe from this topic | Manage Subscription Preferences

2093 Philadelphia Pike #9442, Claymont, Delaware 19703, United States