Rishabh Jain (@rishabbbbbbh) header
Rishabh Jain (@rishabbbbbbh) profile picture

Software Engineer | Evolving from Bugs to Business Wins | Tech, Laughs, and Lifelong Learning.

Bengaluru, India
Joined August 2021
Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)Photo by Rishabh Jain (@rishabbbbbbh)
A piece written for future software developers.
7
17
1
98
22,665
people in blr get one viral tweet and start posting things like "distribution is the only moat"
12
6
1
141
4,119
I've been using OMP (Oh My Pi) by stencil.so for quite some time, and it's easily one of the best agentic coding harnesses I've worked with. Alongside it, I use OpenSpec for spec-driven development. It gives me more control over what my agents build, how they approach it, and the boundaries they should operate within. Recently, I switched my terminal to Tern, also by Stencil, and it feels like the terminal I've been looking for. Native OMP integration, file opening, notes, and a lot more—all in one place. What I like most about this setup is the separation of responsibilities: OpenSpec defines the boundaries, OMP does the engineering, and Tern brings the workflow together. Agentic development is becoming less about prompting an AI to write code and more about building a development environment where you can actually control and review what agents do.
4
172
I’m at a point in my software engineering career where I find it harder to decide how much engineering is actually enough. I don’t want to overengineer a feature, but I also don’t want to push back on so many design decisions that we end up underengineering it. Lately, I spend more time questioning what problem the customer is actually facing, whether we’re solving the right problem, and which engineering complexities are truly necessary. I’m still figuring out where to draw that line.
2
92
Read an interesting paper, “Who Will Become the Next Senior?” The path from junior to senior engineer has traditionally been slow, but relatively well understood. You learn by building, debugging, failing, and taking ownership. Now AI is changing that path. Some engineers might learn faster, while others might skip the experiences that build judgment. No, it makes me wonder that is AI changing how we become senior engineers, or will it eventually change what being a senior engineer even means? Paper: arxiv.org/abs/2607.17067
63
People started defensible about AI generated code and design docs. How can i tackle them in review?
1
43
So OS level AI is getting closer ?
MacBook Pro vs. Surface Laptop Ultra
1
82
Pair programming makes so much more sense now in AI-assisted coding. As writing code becomes cheaper, senior engineers and feature owners can collaborate on PRs in real time, review decisions, catch bugs, and fix issues together instead of going through multiple review cycles.
1
2
141
Had an interesting HR call today that changed how I think about resumes. The recruiter asked, “Do you have experience with AWS?” I said yes—I’ve worked with it quite a bit. Then they said, “I couldn’t find anything related to AWS on your resume.” And that made something click. A resume often has two very different readers. The first is HR/recruiting. They’re trying to quickly figure out whether your experience matches the JD. If the role asks for AWS and you’ve worked with AWS, it should be obvious. They shouldn’t have to infer it from the systems you’ve built. Then comes the hiring manager. That’s where technical depth, ownership, scale, architecture decisions, and measurable impact help validate that you actually have the experience you claim. So a good bullet needs to work at both levels: What you built + technologies you used + measurable impact. Keywords help your experience get discovered. Technical details and metrics help it get validated. My takeaway: a universal resume should be granular enough to make your real skills easy to find, while tailoring for a JD should mostly change what you prioritize. Having the right experience isn’t enough if the first reader can’t find it.
59
Rishabh Jain retweeted
ZENKAI is LIVE! 💙 We’ve put months of work into this, and we’re so excited for you guys to finally try it. Go explore, play around with the new features, and tell us what you think. Checkout: takeuforward.org
322
88
281
1,972
1,387,053
3 AM thought: Boring infrastructure makes money. Boring books make you sleep. Boring investments compound. Boring routines get things done. Maybe boring is underrated.
46
Rishabh Jain retweeted
I don't want to work somewhere that's like a family. I want to work somewhere that understands "We have families" ✅ Read this quote today and honestly couldn't agree more, now more than ever!
7
9
1
126
3,413
At this point, I finally understand why design patterns exist. Not using them has already given me enough bugs to learn the lesson hard way. 😭
2
70
Reviewed a AI-generated design doc and left some open questions. Author asked Claude, pasted the answers back, and didn’t even bother to understand the questions. At this point, he’s just an interface between me and Claude. 🙂
2
67
My teammates get overwhelmed when they need to work in different language codebase and most of the time that language was Javascript. 😮‍💨
1
124
I feel, There's no perfect balance between product managers and engineers, and it's better to accept this than keep searching for one. The core issue is straightforward: product managers need speed to capture market opportunities, while engineers need stability to maintain reliable systems. These goals naturally conflict. When you move fast, technical debt builds up and eventually slows down future work. When you focus on maintaining stability, you miss deadlines and market windows. Companies often look for people who can deliver great solutions quickly, hoping to solve this problem. But this misses the point. The best teams don't try to eliminate the tension—they make it visible and manage it deliberately. They track technical debt the same way they'd track financial debt: they decide consciously when to take it on, communicate those decisions clearly, and schedule specific time to address it later. The reality is that this friction can be reduced through good communication and planning, but it will never disappear completely. Teams will always swing between periods of fast delivery and periods of cleanup and stabilization. The difference between good and struggling teams isn't whether this happens—it's whether they manage it intentionally or just react to whatever problem becomes urgent. Accepting that the tradeoff exists, making it explicit in planning discussions, and being honest about the consequences of each choice leads to better outcomes than pretending perfect harmony is possible.
2
204
Back to track 🏃‍♂️
1
198
I have been promoted to SDE 2 😋
3
116
PMF in tech and beverages is different. here's what I have noticed; >In tech, PMF is when the engagement spikes, downloads increase, and no. of users increases >In beverages, it’s when your website cannot fulfill orders, and even your QCom can't In beverages, PMF doesn’t look like what you read in startup blogs. It is a reorder, and not just a metric. It comes from shelves being out of stock, not retention dashboards. For us at @DrinkQuenzy , PMF wasn’t a moment or something we were numerically able to track, but it definitely started looking like a pattern. When people started reordering before we restocked. That being said, I think we are a far way from hitting the PMF that we want to see, but consumer love is the biggest metric we tracked and still do.
2
2
16
4,120