came back after a week offline and spent an hour just reading posts. people are shipping. full agent teams, named specialists, live clients. and i'm still on the foundation. but here's the honest version of what's actually happening. i build something. it works. then i look at it and realise it's not what i actually wanted. so i break it and start again. then halfway through the rebuild, a new idea comes in and now i don't know if i should finish what i started or pivot to the thing that's clearly better. i've rebuilt the same system three times in a month. and the worst part.. each version was better than the last. so was the rebuilding wrong? or is that just what building actually looks like before it locks in? genuinely asking because i can't tell if this is a me problem or if everyone here is quietly doing the same thing and just posting the final version.

someone in here rebuilt the same system three times in a month. felt stuck. but that's not stuck. *that's the recipe.* --- most people wont feel this. they copy a template, change the colors, call it shipped. they skipped the part where you hate your own work enough to destroy it. *that hate is the signal.* your taste is ahead of your ability. you're not a tourist. --- you're not stuck because you can't finish. you're stuck because you actually care what it looks like when it's done. that's the whole reason you're going to be good. --- i've rebuilt the same workspace a hundred times. don't mistake your reps for failures. each time i saw something i couldn't unsee. a cleaner way. something that made the last version feel like it lied to me. no one sees the versions that die. but those versions are the only reason the current one works. the rebuild loop is not a detour. it is the path. --- this is the very thing that gives you the eyes to see. and you'll need those here. cause when you're actually building, you can look at someone else's project and see where they've been. the constraints they accepted. the fights they won. *it's right there in the workflow*. that's how you know you're among good people. not because they post wins. because they have a folder full of versions that didn't make it. and you know exactly what that means. --- you're not stuck. you're exactly where you're supposed to be. keep breaking it.

I'm curious what everyone here likes to do for fun (of course building stuff with Claude is fun too lol), and if you've applied any AI to your hobby. For me it's been super useful for DND planning and I find I get to stay in creative flow more. Curious what other people are doing

I've been in this community for about a month now and wanted to share where things stand with one of my builds. This isn't polished by any stretch. I do have a few other workflows like content-creator, document-creator, but I needed something to help me navigate my day-to-day as I begin a couple side quests outside my normal 9-5. The goal was simple: I didn't want another chat window I have to remember to open. I wanted something that knows my priorities, reads my calendar, checks my email, and texts me when I need a nudge. Not a chatbot, more like a Chief of Staff. And the goal is to operate within the bounds of the subscription with no extra costs, while also maximizing token efficiency. The other thing I didn't want to do is implement an orchestrating harness yet (OpenClaw, Hermes, etc). The challenge for myself was to keep this as simple as possible without inflating scope. Someone in this community said once: 'constraints are just as, if not more, important than your requirements. What do you NOT want your build to do?' I've definitely taken this to heart in my workflows. ## Planning I've made a few posts about this in comments, but I cannot stress the importance of planning before you build. My method was simple: - First I brain dumped context via voice dictation and transcribed this. Simple tools: VoiceMemos, copy, paste. - Next, I worked through the planning phase with the chat function of Claude in Opus 4.6. I wanted pushback, challenge, and for the model to force me to think deeper and keep me honest. This produced the product requirement document, or PRD. This was a multi-day process (a week?) in my free-time. - For the architecture build, I used Cowork. Handed it the PRD, answered a few basic questions, and then it went on it's way. Got it uploaded to a private git repo. - Currently, I'm working thru further debugging and walking thru the checklist within the PRD in a phased approach. As you'll see below, I have setup a remote screenshare so I can also let Cowork see what I'm doing. This was the most essential because we work TOGETHER to make things happen. it's like working side-by-side with my developer and engineer.

Be honest, which one are you right now? A - I watch/learn/tweak but never start B - I start, fail fast, then go back to watching C - I just build and ignore mistakes I'm solidly in A. Your turn, pick and comment why.