Log inSign up
Unlearn
4,685 posts
Unlearn profile banner
@UnlearnDev

Unlearn

@UnlearnDev
Built for developers who want to unlearn outdated defaults and start building engineering judgment. Powered by @Bitter_Brains
unlearn.dev
Joined March 2017
165
Following
44.6K
Followers
RepliesRepliesRepostsRepostsMediaMediaArticlesArticles

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • @UnlearnDev
    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 '^$'
  • @UnlearnDev
    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.
  • @UnlearnDev
    Unlearn
    @UnlearnDev
    Aug 24
    Spec-driven development is pretty simple: write down what the change is and how it should behave before the agent writes any of it. 🧵
    1
  • @UnlearnDev
    Unlearn
    @UnlearnDev
    Aug 21
    Most people write an agent skill for a topic they think is important. A better starting point is something your agent keeps getting wrong.
    1
  • @UnlearnDev
    Unlearn
    @UnlearnDev
    Aug 19
    Most of the time you spend on a bug isn't spent fixing it. It's spent working out what's actually wrong in the first place. That's the part we hand over to an AI agent in Workflow 6 (Debugging and Performance). Learn more 👇 app.unlearn.dev/workflows/fixi…
Advertisement
Advertisement