I m deciding how long a free trial should last, and I keep coming back to how often someone actually needs the product.

Seven days can mean seven chances to get value from a daily tool. For something used in a weekly meeting, it might mean just one.

My background is in sales management. When you agree on a coaching action with someone, the value doesn t end with that conversation. You need to follow up the next week and see whether anything changed.

That s why I m leaning toward 30 days for the product I m building. It gives people a chance to experience several weekly cycles.

The AI gold rush feels like it rewards teams who ship fast. Many teams are working on a 9-9-6 (9am-9pm, 6 days a week) schedule to keep up with the state of the art breakthroughs and features. Does this give teams an edge against their competition or is this slowly burning teams out.
If you're building in the AI space, I would love to hear what your take is:

• What works for your team and do you follow the 996 schedule?

• Did following a 996 culture create more bugs or actually lead to breakthroughs and push you ahead of your competition?

• How would you balance your life outside of work if you followed this schedule?

Making this post to raise awareness and ideally find a middle ground for teams that are currently growing and trying to keep up with the competition

As developers, it s easy to fall into the I could just code this in a weekend mindset.

But I ve realized time, maintenance, and support often cost way more than the price of the tool.

Still, sometimes I just can t justify paying for something I know I could make.

Hello friends, and welcome back to the changelog. The devs have been running on a balanced diet of espresso shots and questionable amounts of energy drinks, which means you guessed it: fresh updates are here. From saying goodbye to Coming Soon, to giving you a shiny red self-destruct button, to sprucing up Alternatives, and a shiny new footer, we ve packed a lot into this round.

Coming Soon Forum Threads

The old Coming Soon pages have officially retired (and you lot noticed). From now on, every new product you create gets its own forum thread. It is your place to share updates, drop teasers, or just shout into the void while you wait for launch day. People can still follow from your forum page to get notified when you go live, but now you can actually start the conversation early.

I m restyling a live app screen by screen, with Claude Code doing the edits. My test suite has 262 tests and all of them pass, but none of them check how a page looks. So a change to shared styles could break a screen and nothing would tell me.

Before each change, I have the agent screenshot every screen I m not supposed to touch, using a fake signed-in session and mocked API responses so no real data is involved. After the change, it captures them again and compares them pixel by pixel. Anything that differs has to be explained.

That caught something I would never have seen. 34 screens matched exactly. One modal didn t: 1,334 of about 215,000 pixels were different. To my eye, before and after looked identical. The cause was that my first version moved the page into a new wrapper, and the old container had been quietly centering the modal s heading. The new one didn t. No test would have complained.

It also showed that a modal kept outside the new wrapper still changed colour, because my theme variables are set on the whole page, not just the wrapper. I had to re-scope the old colours around the modal.