It’s worked well for me on my #buildinpublic journey, but I have a suspicion that my path isn’t _the_ or maybe even _a_ right path. Have you switched to doing more programming than systems work? How did you do it?

Now that I've pivoted Kinetic twice in less than a week, I'm officially calling this phase of #buildinpublic the "Pivot in Public" phase...

I posted about Kinetic on the Indie Hackers #buildinpublic group if you're interested in the high-level vision:

indiehackers.com/post/building-…

Dub update #3 is here! I talk briefly about how I get data out of your Notion tables and into Dub's database. #buildinpublic

youtu.be/WVkzF3RA_mQ

This week was productive! Made major changes to the Dub uploader embed. #buildinpublic

loom.com/share/ba6c0cf8…

I’m finding it difficult to find a balance between being heads down programming and tweeting about progress. How do you handle this? How often and what do you share re: development? #buildinpublic

I may or may not have spent more time than I’m willing to admit using forEach() instead of map() when trying to render JSX earlier this week… #buildinpublic

I recorded a quick demo video showing the podcast webiste and audio upload functionality so far. Lots of work still to do, but making good progress! #buildinpublic

loom.com/share/ade86117…

I didn’t make too much progress today on Dub. Mostly some landing page tweaks and trying to figure out what the messaging should be. Writing copy is hard. #buildinpublic

Update on the podcast hosting project:
- Named the project Dub
- Bought dub.so (no landing page yet)
- Decided to go with nextjs, @supabase, and @tailwindcss

In addition, I'll be launching a podcast entirely with dub.so! #buildinpublic

@TimothyBramlett I've found that I get more reach by using hashtags, in particular #buildinpublic - shoutout to
@iamborisv for building the @_BuildInPublic_ bot!

I should also add that I am by no means a marketing person.

@TimothyBramlett I've found that I get more reach by using hashtags, in particular #buildinpublic - shoutout to @Brslv for building the @_BuildInPublic_ bot!

I should also add that I am by no means a marketing person.

Update on the podcast hosting project:
- Named the project Dub
- Bought dub.so (no landing page yet)
- Decided to go with nextjs and @supabase

In addition, I'll be launching a podcast entirely with dub.so! #buildinpublic

I'm building a podcast hosting service on top of @NotionHQ!

Lots of people manage their podcasts in Notion, so this seems like a natural evolution of that process.

We'll see where it goes! #buildinpublic

I've come to the realization that Ruminate's features are too easily replicable with tools that teams already use, so I've decided to stop building Ruminate and pivot to something else. I've got a few ideas around #notion's new API. Stay tuned! #buildinpublic

To those that have sold #notion templates on Gumroad, etc. - how do you push template updates to those that have already purchased it? #buildinpublic

Anyone creating online course material or running a blog with #notion? I’d love to hear your pros and cons list. #buildinpublic

No-code is not without its quirks, but so far I’m building Ruminate at least 10 times faster. As long as your app doesn’t have really unusual functionality, I see no reason not to go the #nocode route from the start. #buildinpublic

Back on the #buildinpublic horse after the move!

I've decided to make the jump into #NoCode for Ruminate with @bubble. My initial features list contains exactly zero items that can't be built with Bubble. I'm open to counterpoints or why you think this is a bad idea.

My #buildinpublic updates have been a bit sparse lately due to me getting ready to move into my new house this week. Looking forward to getting back on the horse next week!