Tweet
Back at work after a trip through France! Excited to get back to #buildinpublic.

80daystartup.com/day-61/enjoyin…
As the traffic for your #startup grows you'll have to relent and add caching layers eventually. But you can do without caching for much longer than you'd think.

Our #saas Thymer.com we #buildinpublic, and we blog about our design choices, our mistakes and our wins.
We're high conviction on product, but low conviction on marketing and our business model. We know what we want to build, but everything else we'll figure out as we go. My Sunday morning musings:

80daystartup.com/day-50/high-co…

#buildinpublic #startup #saas
I wrote about wild features we won't add to Thymer anytime soon.

When making something new it's easy to come up with cool and totally unrealistic feature ideas. But first we have to make a simple V1. #buildinpublic #saas #startup

80daystartup.com/day-48/wild-id…
Day 40/80 of our #80daystartup

This is our process for working on our startup. It’s super simple, as it should be #buildinpublic
I’ve been under the weather almost all week and productivity has been low. 🤒

Hopefully I’ll be able to catch up some next week. We have a mountain of work ahead of us to get the first version of thymer.com going

#buildinpublic
I wrote about #SaaS pricing, and about one trick in particular: Start with a revenue goal, and then calculate backwards. Compare different revenue models and ask yourself what has a better chance of working.

80daystartup.com/day-38/calcula…

#buildinpublic #startup
Day 31/80. Working on the editor. Experimenting with different ways to add/change tags.

We're probably going for an autocomplete approach where you can type freely or select an option from a dropdown.

#buildinpublic #saas #startup
Day 26/80. Refactoring work on the thymer.com editor mostly. Deleted a lot of code and fixed bugs. Getting the code ready for undo/redo. Must be resilient because we want to allow collaborative editing. #buildinpublic #indiedev
Wrote a blogpost where I argue that tech debt should contain all design choices that create future obligations, not just sloppy code.

Packages. Unnecessary features. Integrations with 3rd parties that break. It's all debt.

80daystartup.com/day-26/thinkin…

#buildinpublic #startups #saas
Day 24 of 80. It's been a long day, but very productive. Some days your code only gets messier and more complicated, other days you find ways to reduce greatly complexity. Still much cleanup work to do. #buildinpublic
Day 24 of #80daystartup. Time flies, we're already at 30%! Our scope has gotten -- surprising nobody -- completely out of hand again.

The editor (no contenteditable, 100% JS!) is really starting to take shape. Going to do a full tech writeup soon. #buildinpublic #saas
It's not overengineering if you need the tech to make your app work. Sometimes the simplest approach is still complicated.

Sync without glitches? Conflict-free Replicated Data Types (CRDTs) will do that

Editor that works? Reject contenteditable and build your own #buildinpublic
Day 19 of #80daystartup

Making a great app is hard. Design. Throw away. Repeat. If you want really passionate users and the growth that comes with it then your app has to be great. No way around it.

80daystartup.com/day-19/your-ap…

#startup #saas #buildinpublic
Day 18 of #80daystartup

Feature list of what we're planning to include in the MVP of our task/planning IDE Thymer. Unrealistic or wildly unrealistic? Time will tell!

#buildinpublic #saas

80daystartup.com/day-18/thymer-…
My coffee break musing.

When you have strong software skills but are weak at marketing and sales let your product do the talking.

When you're good at marketing just use #nocode and launch in days instead of months.

#buildinpublic #saas #startupidea
It's so much more work to actually get something out there than you'd think. When you're 90% done you still have the last 90% left to do.

Kudos to those who launch, even when it doesn't work out! #buildinpublic