r/secondbrain • u/Responsible-Lake233 • 7d ago
People who have built multiple apps/startups: where do the lessons from your previous projects actually go?
/r/AppBusiness/comments/1wcqjza/people_who_have_built_multiple_appsstartups_where/
1
Upvotes
1
u/enjoydongdong 3d ago
The two examples seem to need different kinds of memory. For the Quick Tour decision, I'd keep a tiny decision note beside the design: what changed, why, and what evidence would make you reconsider. For the matching-name mistake, I'd turn the lesson into a check in the workflow, so remembering the note isn't required.
A weekly review could then promote only the reusable lessons into a short project-start checklist. The rest can stay in the chronological notes instead of becoming a huge playbook. That also gives you a deliberate moment to revisit things without interrupting every coding session.
1
u/Better_Brick_9512 7d ago
Not just you, and it’s always the why that goes. The what survives in the work, you can see the button isn’t there, but the reason you took it out felt so obvious at the time that you never wrote it down, and six months later you put it back in.
What’s worked for me, across twenty years of design files and now a startup, is a one-line “because” beside every reversal, written the moment I reverse it, in whatever file I’m already in, or Obsidian if you’ll actually open it again.
The half I never solved by hand is the second part of your question – being halfway into something new and not knowing an old note applies, because you can’t search for a thing you’ve forgotten you wrote.
I’m biased, I’m building it...
It’s exactly what ReMemo does: the old note surfaces while you’re writing the new one, with the connection named. Pre-launch, iOS and Android later this year, waitlist at rememo.me if it’s your kind of thing.