unfair.so
Browse more creators
@nitinthisside_
Nitin.nn
Nitin.nn8.7K
Nitin.nn
This creator added themselves. Not verified by unfair.so.
@nitinthisside_B2B SaaSBackend DevelopmentAI Tools

21 | Software Developer | Interested in Backend + AI | Building SaaS & shipping ideas | Open to collabs 📥

8.7KFollowers
533Median impr. / post
2.5%Engagement
2
Paid partnerships
In their audience
4 affiliated with @amazon follow Nitin.nn
@HelloVyom@Hem_chandiran@Qayyum9505@dipan_c_barua2 affiliated with @avax2 affiliated with @x2 affiliated with @cisco2 affiliated with @getalchemyst2 affiliated with @thebuilder_base
1,115 verified followers analyzed
@HelloVyom@Hem_chandiran@Qayyum9505@dipan_c_barua+1111101 engineers98 AI engineers84 devtools engineers67 founders53 media creators53 AI founders
18–24 core age group
48.1%
70.8% of audience in India
🇮🇳
Last 7 days117 posts analyzed · replies not counted · updates weekly
ImpressionsEngagements
148K74K0
4.7K2.3K0
Aug 30Aug 31Sep 1Sep 2Sep 3Sep 4Sep 5
Past collabs
Nitin.nn@nitinthisside_ · May 19Go from zero system design knowledge to interview ready with one free resource @thita_ai just dropped a full system design module and here's what you're getting: - 20+ hours of structured content - Real case studies including AI system design - Cheatsheets for every major topic and case studies - Visual diagrams that actually make things click Everything is researched from system design interviews asked in 2024, 2025, and 2026 No outdated content from 2019 If your interview is soon, you can cover the entire thing in one weekend if you stretch it. Caching, sharding, load balancing, message queues, database design, consistency patterns, all of it This isn't a random youtube playlist stitched together This is one structured path from fundamentals to advanced link in repliesThitaPaid partnership5.1K views
Nitin.nn@nitinthisside_ · Apr 2This free open-source 𝗠𝗖𝗣 𝘀𝗲𝗿𝘃𝗲𝗿 cuts Claude Code's token usage by 60%. Instead of grepping 30 files to understand your codebase, it makes 5 calls. It knows who owns every file, what breaks if you touch it, which code is dead, and why anything was built that way. Real comparison on a 3,000-file codebase: "Add rate limiting to all API endpoints" Without repowise: > Claude Code greps 30 files. 8 minutes. Burns tokens reading code it doesn't understand. Misses that auth.ts has 47 dependents. Doesn't know payments/ is 71% owned by one engineer. Breaks hidden coupling. > Ships anyway. With repowise: > 5 MCP calls. 2 minutes. Found every dependency. Found prior retry logic to reuse. Flagged the right engineer for review. Knew there was no existing rate limiting decision. > Same task. Fraction of the tokens. Better result. It builds four intelligence layers on your codebase: 𝗚𝗿𝗮𝗽𝗵 : full dependency graph with PageRank for your most critical code 𝗚𝗶𝘁 : hotspots, ownership percentages, files that secretly change together 𝗗𝗼𝗰𝘀 : auto-generated wiki rebuilt on every commit with freshness scores 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻𝘀 : captures WHY code was built that way. The layer nobody else has. Also auto-generates your CLAUDE.md from real codebase data. Not a template. Real architecture, real hotspots, real ownership maps. Under 5 seconds. just 3 commands: pip install repowise repowise init repowise serve Self-hosted. Your code never leaves your machine. Works fully offline with Ollama. https://github.com/repowise-dev/repowiseRepovisePaid partnership7.4K views
Planning a launch?Nitin.nn is one of 200 curated B2B creators. Tell us what you are launching and we will put the shortlist together.
[email protected]·t.me/fdrtrm
Built with unfair.so
1 picked$50