Lee Watkins

Emotionally preparing myself for the #Shipaton...

What are folks building for #shipaton? Keen to see what y'all are up to!

Why did the React Native developer cross the road?
To prove they could run on both sides!

Current state of my latest app: ReadyFreddy.dev

PMF is when:
✅ Customers love it
✅ Users pay for it
✅ Your mum says “That's nice, dear.”

Ready Freddy is pretty much built...at least far-enough to get some early testers.

Next job: find users!

How do I do that? 😅

The quality of the dictation from Wispr Flow is amazing. I'm loathed to type anything anymore. And the fact that it learns your vocab is delightful 👌🏻

I'm going to spend a little more time with it, and build a few more features/products using it to see how things go. But it might be worth the extra cost and reduced pace for an overall better end-product.

4. The overall solution feels far more robust and production-ready. There are details that TM included that I've never seen in CC's plan mode (eg: analytics, monitoring, caching)

3. There seem to be fewer build errors because the tasks are ordered a little more logically, in smaller chunks and there are more intermediate check-in points.

2. If feels like it ultimately burns a lot more credits/tokens using TM over CC's internal planning tool.

but...

My initial impressions are:
1. Building a features takes longer - there are way more steps involved and the back-and-forth between TM & CC seems to make the process a little slow.

Trialing TaskMaster AI alongside Claude Code. I'm not sure it offers a huge amount of value over Plan mode, but we'll find out soon enough...

Been looking into my deployment options for Ready Freddy: looks like Gigalixir & Fly have the best Elixir support, while Railway & Render offer some good options at a reasonable price-point.

What are y'all using to deploy your Elixir/Phoenix apps? I really don't want to deal with DevOps, just focus on building.

Yesterday's task was to polish Ready Freddy's UI to capture the brand and have a consistent look across the whole app - it's looking amazing and so happy with how it's coming together! I'll share some screenshots soon 👀 🔜

When did web apps stop using Gravatar for profile pictures? Seems like such a user-friendly way to handle it, and it means you don't need to handle file upload, storage, etc. Am I missing something?

I've named the new on-call tool that I've been building...

Meet: Ready Freddy! 👋

Because when alerts hit at 3am, you want something that's always ready to respond (and a bit of friendliness doesn't hurt either)

Right, you can now create basic schedules and associate them with services. The most basic version of the app is now ready and working! Time to deploy it!

Would you expect to have access to multiple organisations in your on-call scheduling & alerting tool? Are there cases where you'd be part of "on call" schedules for multiple orgs?

If I start working on embedded things I'll take a look. 🙏🏻

Billing is set up with LemonSqueezy! There's still a bit of work to do to polish it up a bit, but the basics are all in place and working, which is really exciting. Now time to move onto team management - letting users create organisations, and then invite people to them.

I've only heard good things about Rust

I'll take a look! 🙏🏻

That might be going in the opposite direction 😅 What language are you using for that?

Very cool!

OK, so now I'm not sure whether I should be using Stripe or LemonSqueezy - sounds like Merchant on Record could be really useful. Having a look into @peterullrich.com's lemon_ex library for this.

Very interesting!

Gotcha, that's a great point! I've never used distributed actors - they're only on the server, right?

Starting to integrate billing now - very exciting moment. First time that I've actually built billing into a web app. Now I get to learn about all the pain of Stripe that I've heard about.