@david_kubgak · X

Generate a professional README from any GitHub repository in seconds.

@theakbarjuraev · X

connect to your github repo and it debugs to the core and deploys the changes. Mainly for people who build stuff

@shawkalent · X

我开发了两个平台，一个是开源平台：

@Tweet2Tusharr · X

hey everyone 👋 we've been working on something over the last few weeks around customer research. we'd genuinely love if you could spend 5 minutes trying it and tell us what we're getting wrong.

@Dil_Lynn · X

u/ramu9703 · Reddit

I built a public ledger that tracks a software idea from "shower thought" to shipped code hey everyone, I spent my weekend building a public backlog called vibehub (thanks 5.6 sol :) ) the main problem i wanted to solve is that too many good micro-ideas die in notes apps, and too many open-source projects launch without anyone knowing why they were built, who had the original spark, or how they evolved vibehub tracks the entire lineage of a project: - public feed of software briefs

@Vaggarwal2107 · X

Just launched the MVP for DevDossier 🚀 A sleek, minimal showcase for developers to manage their projects and dev timeline in one place. Check it out and drop your feedback! 🔗 #buildinpublic #webdev #indiehackers #reactjs #developer #portfolio #AItool

@ReleasePilotHQ · X

Just shipped ReleasePilot. Connect GitHub → push code → release notes write themselves. No Actions. No config. Just push. Free for 1 repo & free trial → #buildinpublic #indiehacker #saas #github

u/freestyle_gonzo · Reddit

Vibe coding made building fast. It didn't make understanding easy. Something changed in the last year. Vibe coding (or agentic engineering if you ask some) made writing an app fast. Week-to-weekend fast. More people are building software than ever before, and I think that's a genuinely good thing. But fast building creates a new bottleneck. Writing code is no longer the hard part. Understanding what you built and its nuances is. A huge share of people shipping right now have never analyzed

u/SnooStrawberries827 · Reddit

my team had 47 open PRs and nobody was reviewing them, so I gamified it our team hit 47 open PRs at one point last month and nobody was reviewing them. tried slack reminders, deadlines, rotating reviewers, none of it really stuck. might be related to the fact that everyone's hyped about how fast AI can write code now, copilot cranking out entire features in hours, but none of that matters if the PR just sits there for a week. feels like writing code stopped being the bottleneck a while back

u/Comprehensive-Bad-43 · Reddit

I got tired of documentation that lies, so I made docs that have to prove every sentence Founder here! Every codebase I have ever joined had the same problem: the docs describe the code as it was six months ago. Nobody updates them, because updating docs is the least rewarding job in software. So I built RepoFold . You connect a GitHub repo and it generates a full wiki, but with one hard rule: every technical claim has to cite the exact file and line numbers it came from. If the AI can'

u/Thick-Rip-1187 · Reddit

i started realizing something weird about github profiles you can look at someone's github and see commits, stars, repos, languages, all that stuff. but you still don't really know what that person is actually good at. like... someone could have 500 commits because they're building AI infra. someone else could have 500 commits because they're building dev tools. on the surface, their profiles can look pretty similar. and i kept thinking... why is it so hard to understand what s