The home of SaaS builders.

People think it records the screen. It takes stills for a docs page. I can live with explaining it, or I can change it before more pages quote the name.

The picture on the homepage shows a button I have been meaning to move. I delayed the fix so the site would not be wrong. That is an absurd dependency. The fix ships tomorrow. The picture can be stale for a day.

Previously it failed with a generic message and I had to ask for the file. The row number will not delight anyone. It will make the next email shorter.

I ship the interface, then I mean to update the article, then a ticket quotes the old screenshot. I need a smaller ritual than 'rewrite the docs.'

My CSV is tidy. Theirs has a blank line, a second header, and a date format I did not consider. I am rewriting the parser around the bad file, not the demo file.

I swing between a joke and a manual. The joke does not help at the step that fails. The manual sounds like I dislike the reader. There is a middle and I have not found the sentence.

The app is a form, a job, and an email. I added a queue because it felt grown up. Failures are now harder to see, and I am the only person on call.

Volume spiked. The messages are not their customers, they are junk going out through me. I have a rate limit now. I am deciding how loud the warning should be.

I left it until it was large. A smaller change would have been easier to explain to a friend. Next time I will ask before the branch has a personality.

I like the issues. They are also a second inbox. The hosted product is what pays for the week, and it is getting the leftovers.

Developers arrive from search, read the example, and try the hosted version. The marketing site talks about the vision. The README talks about the command. I am considering making the site more like the README.