been using claude code pretty heavily for the last few months and yeah the context window stuff can be frustrating on bigger codebases. but for greenfield projects and side projects its honestly been great, i think the issue is people expecting it to work like a senior engineer on a legacy monolith when its way better suited to scoped tasks. the trick is breaking things down before you start
the middle ground nobody talks about is using AI for the boring infrastructure stuff (stripe integration, auth boilerplate, static site scaffolding) and writing the actual business logic yourself. i've shipped like 3 side projects this year using that approach and the code quality is fine because im not vibe coding the parts that actually matter
Yeah, people do forget how much of our codebases is already slop. Like, anything that's in a "boilerplate" or "scaffold" is probably code that a human shouldn't be spending time writing in the first place.
love seeing more local-first tools like this. feels like theres been a real shift since the codebeautify breach last year, people are actually thinking about where there data goes now. nice work on keeping it all on device
honestly the thing that worked best for me was just writing about the problem i was solving, not the product. like a dev.to post about why server side processing is unnecessary for most dev utility tools got way more traction than any "hey check out my thing" post ever did. people engage with the take, then they find the tool naturally. also reddit > twitter for early stage imo, the subreddits are way more targeted
