Unlearn

@UnlearnDev

Built for developers who want to unlearn outdated defaults and start building engineering judgment. Powered by @Bitter_Brains

Pinned
Unlearn
@UnlearnDev
Sep 9
A one-line bug report, no repro steps. You guess, poke around, hope it sticks. Half the time it doesn't, because you never proved you had the actual bug. Workflow 06: Debugging and Performance fixes that. Live now on Unlearn - learn more: unlearn.dev
00:00
Unlearn
@UnlearnDev
Sep 16
In the age of agentic engineering, refactoring is disappearing from git history. GitClear's latest report puts moved lines at 3.8% of code changes so far this year, down from 21% in 2022. Agents write a lot of code, but they don't go back and tidy up unless you ask them to.
Unlearn
@UnlearnDev
Sep 11
Your tests can stay green while your app breaks. Ask an agent to tidy up a file with no rules in place, and it'll happily change behaviour. We show exactly this at the start of Workflow 7 (Refactoring with an AI Agent), then spend the rest of the workflow making sure it doesn't
Developer Education for the AI Era | Unlearn.dev
From unlearn.dev
Unlearn
@UnlearnDev
Sep 3
Most people decide what to refactor by opening a file and not liking how it looks. 💡 A better starting point? Files you or your agent have to keep going back into. They cost time and money. Use this to find them: git log --name-only --pretty=format: -- 'app/*' | grep -v '^$'
Unlearn
@UnlearnDev
Aug 31
AI writes race conditions all the time. They’re some of the hardest bugs to spot in review because the code often looks perfectly reasonable.