Many times before, I have tried to take up a lot of challenges to build stuff in public and learn in public.
I did end up finishing the projects and learning the things I planned to.
But I am never able to keep people updated. Which means I learn and build, but never in public.
So after a lot of mental preparedness, I am planning to do this.
Contents
I’ll start a system design learn in public series. I am reading an amazing book(not sponsored or affiliated) to learn this, along with reading various amazing articles for the same.
And the only reason I’m doing this? To become a better software developer by making my projects actually scalable
So, I am planning not to keep any deadlines as such for this one. I’ll just work one hour daily for this.
Every day, I’ll update what I learnt briefly on my X handle, and a little in detail, for people to follow along on my blog.
Every time I fail, is because of the random targets I throw at myself. Not this time, though.
Let’s keep it simple, real, and imperfect.
Goal: Build an AI job search agent that evolves from a broken MVP to a scalable system while learning system design concepts publicly.
The name of this project would be: HuntKit.
HuntKit is an AI agent that analyzes your dev profiles, scrapes company job postings, finds recruiters, and drafts personalized outreach emails—built specifically for developers.
20-Day Sprint Cycle For HuntKit
- Days 1-3: Read chapter, share key learnings
- Days 4-7: Plan features for this sprint
- Days 8-15: Build the feature (expect it to break)
- Days 16-20: Deploy iteration, write comprehensive blog post
Repeat 5 times = 100 days = 5 improved versions of the project
Right now it is only a thought, but 20-50 days later, hopefully it finds me some perfect fit jobs/internships.
And 100 days later, 1000s(or even more) of others like me.
100 hours = 1 problem solved.
