Prince retweeted
4 weeks ago hatchzip had 4 stars
today it crossed 3,000 stars
im so happy
33,055 downloads. 43 pull requests merged from 8 contributors. started as a 2 hour build after a party
thank you all :)
Replying to @divyansh_1729
mai bolta hu i am generating sample for my project work to kar deta hai
1
134
Prince retweeted
Me and my Claude cooked something this week
gitpulse: a personal dashboard that scans all my GitHub repos and tells me what’s actually going on in them. Phase 1 is live, and it runs entirely on free tiers. $0/month.
What it does:
📊 Shows my language mix across all repos, and how it’s shifted over the years
📈 Tracks commit activity: most active days, hours, longest streak
🩺 Gives every repo a health score out of 100 (README, license, CI, tests, stale branches, old PRs, recent activity) and labels it active, slowing or dormant (Some of mine were humbling)
📬 Builds a digest: PRs waiting on me, new issues, failed builds, new stars
🧰 Detects my real tech stack from go.mod, package.json and Dockerfiles
The stack
- Go backend (chi + pgx, no ORM)
- React + TypeScript + Vite + Recharts
- Postgres on Neon
- Deployed on Render
- GitHub Actions for the daily scan
First full scan: 45 repos, 75 API calls, 81 seconds. Every scan is saved as a snapshot, so trends build over time. The backend Docker image is 23.9 MB.
3 fun problems along the way
1. Free Render services sleep after 15 min idle, so an in-app scheduler would never fire. The fix: a GitHub Actions cron calls a secret-protected /api/scan endpoint once a day, which wakes the server and runs the scan.
2. Frontend and backend were on different .onrender.com subdomains. The browser treats those as different sites, so the login cookie would have been third-party, and Safari blocks those. The fix: the static site forwards /api/ to the backend, so the browser sees one site.
3. Chrome flagged my brand-new site as “Dangerous” 💀 A new site on shared hosting, “git” in the name, a “Sign in with GitHub” button: to Google, that looks like phishing. The fix is a review request through Search Console. Lesson learned.
Phase 2: the AI layer
🔍 PR assistant: summarizes every new PR, flags risky changes, suggests labels
📝 Release notes generator: turns merged PRs into a changelog and drafts the release
🪪 Profile README that updates itself with my latest projects and articles
🔌 An MCP server, so I can ask an AI “which of my repos need attention?”
Code: github.com/harshit3011/gitpu…
Prince retweeted
Take 01: The First Steps
made with @Zopia_AI & @ViduAI_official
#Zopia #ZopiaViduChallenge #Zopia第二届创作大赛
Prince retweeted
A few months ago I was just posting articles on X and watching them disappear in the feed.
Now they live on a free site, organized, searchable by topic, with progress tracking: vidya-bodha.com
Still adding more every week. Still free. Still no signup.
If you’ve read even one article and found it useful, a repost is the best thing you can do for it. That’s how the next person finds it.
vidya-bodha.com is live.
My GitHub repo crossed 830+ stars, so I turned it into a proper learning website.
70+ in-depth engineering articles, all in one place, organized so you can actually learn instead of scrolling a timeline.
What you’ll find:
-30+ HLD breakdowns (YouTube, Netflix, Spotify, Instagram, Amazon, Discord, and more) -LLD classics like parking lots and vending machines -Backend fundamentals: APIs, databases, caching, concurrency -A complete Distributed Systems series, all 9 parts -A complete Microservices series -Search and filters by topic -Structured learning paths -Progress tracking, so you know what’s done and what’s next
“Vidya” means knowledge and “bodha” means understanding. That’s the goal here: not just reading about systems, but really understanding how they work.
AI, ML, and DevOps content is coming next, and every new article lands on the site first.
The GitHub repo stays open if you’d like to star it
github.com/harshit3011/Techn…
Prince retweeted
This is my first $1,000 from an application.
It took me 150-180 days to make my first $1,000 from Twitter payouts.
With my SaaS, it took just 39 days.























