I'm starting up a new CodeCook session on rethinking the traditional share dialog for sharing content. Follow along on this post thread as we explore how I can make sharing better on my publishing platform for live coding. #buildinpublic
Johnny Builds
@johnnybuilds.bsky.social
Dev sharing brass tacks & the nitty gritty #buildinpublic 💯 Only posting bangers! Currently building the publishing platform for live coding at https://codecook.live Also: 👋 https://publicbuilders.org 🏠 https://johnnybuilds.com
I’m starting to share this little project I’ve been working on and one thing that stands out to me is that the Profile and Project pages are a bit plain. I'm going to share my progress here in this thread. As a starting point, here is what the profile page looks like right now. #buildinpublic
Finished adding chat to CodeCook. Looking forward to my next live code session be a little more "live" #buildinpublic
In my last session on my publishing platform live coding, I started to add chat. Now I’m going to pick up from where I left off, starting with a UI refactor. Here’s a screenshot of where we’re at.
Renewing another live coding session on where I finish adding chat. Follow along at codecook.live/johnnybuilds... with any luck you’ll see a chat window show up there at some point during the session.
I'm going to work on adding chat to CodeCook so I'm starting up a live session (the first ever!) Unfortunately it won’t have chat because that’s what I'm building 😀 codecook.live/johnnybuilds...
CodeCook.live
The publishing platform for live coding that turns your commits into live code cooking sessions
codecook.live
I've been tracking follower growth of 100+ #buildinpublic accounts for a few months now. Originally, Bluesky was the clear leader for getting followers, especially for those that don’t already have a big audience. Unfortunately, 𝕏 has caught back up. I'm still hopeful for 🦋 but it is concerning
I’ve got live coding working on my publishing platforming for live coding. I’m thinking of calling live coding for introverts. I also have no idea what I’m doing 🙃 but its fun as hell #buildinpublic
The first live session of CodeCook is unfortunately just me on localhost listening for commits to CodeCook. #livecoding
Instead of writing tests when starting a project, go all in with strict typescript interfaces. No any! With Cursor, it is much easier to enforce. Once you've baked long enough and want to make sure you don't break stuff, add tests. Puppeteer can record clicks and Cursor can scaffold up your tests.
CodeCook Day 13 Update #buildinpublic 🦋 Added Bluesky sharing functionality #️⃣ Enhanced posts with hashtag support 🧵 Published first thread via Bluesky API 📂 23 ➕ 1201 ➖ 388
I came up with the idea for CodeCook.live when I was bsky.app/profile/johnnybuilds.bsky.social/post/3lct4orsaqc25 some code for a project. Sharing my coding process in real-time was a lot of fun. It got me thinking...
Working on adding a Post to Bluesky feature to my Next.js app. Got the connect account working. Next up, need to transform markdown into a post thread... #buildinpublic
Up next, setting up Bluesky as a first class integration for publishing from a coding session...
Published the first post ever from my new code publishing platform codecook.live/johnnybuilds...
CodeCook.live
The publishing platform for live coding that turns your commits into live code cooking sessions
codecook.live
Haven't been posting so much because I've been heads down working on CodeCook.live - the Publishing Platform for Live Coding. I've got a waiting list up now.
Its official. I’ve lost my mind. I’m working on CodeThreads. It is the most ambitious project I’ve ever tried. I’m building The Publishing Platform for Live Coding. #buildinpublic
I freaking love just giving Cursor the most pain in the ass but not actually that difficult code and it just absolutely one-shots it.
Importing CodeThreads into CodeThreads to build the prototype of CodeThreads so there can be a CodeThreads.
I know I’m supposed to be scared about AI replacing me but hot damn is Cursor fun to build stuff with.
For my Supabase projects, from the start I create all the tables via local scripts so that Cursor has the full context of the database. As I make changes, I use supabase cli to push migrations from more local scripts.
Messing around with my code threads idea today. Here's what I've managed to cook up so far (ui with mock data):
Just did the first commit for my new project. I'm calling it Code Threads. It is going to be the project-centered #buildinpublic platform that I wish existed where each commit becomes a post. Still in the early idea/tinkering phase but of course I've already got a landing page codethreads.vercel.app
Code Threads
Live coding in post thread format
codethreads.vercel.app
Having trouble finding a place where I can get realtime feedback on what I'm building. Are there any discord servers or other things I might join where I can share what I'm live coding, etc? #buildinpublic
Just submitted my project to Indie Hackers via this post www.indiehackers.com/post/directo... which I made via a node ATProto script to pull posts from my recent Bluesky mega threads on submitting instapoll.run to various SaaS directories, then used ChatGPT to write the article from those posts.
Directory Submissions: Lessons from Launching to 100+ SaaS Directories
Building isn’t the hard part of launching a SaaS —it’s getting people to notice. SaaS directories can help with SEO and initial traction, but it is a mi...
indiehackers.com
What should I #buildinpublic for my next project? a) AI Tarot Card Fortune Teller (w/custom card art per user) b) Daily Business Idea Generator (via users searching online) c) Global Multiplayer Elimination Game d) Code Threads (social live coding by post) Please vote by reply or ask questions
Follow along in this post thread as I live launch my #buildinpublic project (Instapoll) to top rated directories for SaaS products. We’ll find out together which ones work well and which ones not so much. I'll be doing the top 100 from the same list as before from @onlinedopamine.com Here we go...