Opens profile photo
Follow
Click to Follow jiten
jiten
@jiten
Engineering
@Viacom18
Startups, Learning, Coding, Product
jeet.worldJoined November 2007
731 Following
6,799 Followers

jiten’s Tweets

Pinned Tweet
jiten
@jiten
I recommend an on-call roster for any team with more than five engineers. It all boils down to work-life balance & context-switching! This is a thread about why I recommend an on-call roster. #jeetkagyan
6
171
Show this thread
jiten
@jiten
Another week, another release! My team is back with a new beta version of our website - beta.jiocinema.com Take a look and give me feedback (DMs open).
Quote Tweet
jiten
@jiten
My team has been working on a new version of JioCinema app for a couple of months. Our Android and iOS public beta apps are out. Get a sneak peak for these apps. DM me for beta access.
Show this thread
6
97
jiten Retweeted
Rohit Tikmany
@some_rohit
Who's world class at #pushnotifications? I have a few technical questions that will intrigue & pique a master. Help me connect with an expert / consultant / agency who are renowned specialists in PNs & I promise to buy you (and them) beers (or more). And don't forget to RT!
6
10
jiten
@jiten
My team has been working on a new version of JioCinema app for a couple of months. Our Android and iOS public beta apps are out. Get a sneak peak for these apps. DM me for beta access.
37
735
Show this thread
jiten Retweeted
Arnav Gupta
@championswimmer
Senior Frontend Engineers, looking to work at hundreds of millions users of scale, challenging things like building platform level author, analytics libs, video streaming, DRM infra. If this is you, hit me up. (Needless to say, RT for karma).
8
293
jiten Retweeted
Sunny Gupta
@sunnykgupta
A lot of people approach asking for advice on how to switch. Remember, once you are in the industry, you're not only being judged for your DSA skills. Companies would like to know if you were invested in the projects you did. If you've been on the bench, build something in OSS.
8
400
Show this thread
jiten
@jiten
If you are a founder/engineering lead and have a product that customers are using, your team is spending time tackling live/production issues- talk to your team and see if the on-call roster makes sense for you.
2
3
Show this thread
jiten
@jiten
7. A well-implemented on-call roster is a multi-level roster. Figuring out level 1 and level 2 is often tricky. I usually keep senior engineers on L1 and engineer managers on L2, but I have seen implementations where L1 and L2 schedules are just staggered by a week or two.
1
2
Show this thread
jiten
@jiten
4. Sometimes, bug triaging and resolution will be slower than in your current ad-hoc system. Overall, I still feel that detection and resolution issues would decrease (which is a good thing) with a dedicated engineer.
1
1
Show this thread
jiten
@jiten
3. You are sacrificing a good percentage of velocity by dedicating on-call bandwidth. I think about this bandwidth because the team was probably already spending all this time across multiple engineers; you are only consolidating the effort to one engineer.
1
1
Show this thread
jiten
@jiten
2. Onboarding new team members in on-call takes time because they need to be effective. Shadowing current on-call followed by a reverse shadow week often helps.
1
1
Show this thread
jiten
@jiten
Pitfalls I plan to write another post about how to run an on-call system effectively soon. I do want to inform you about some pitfalls here: 1. Everyone on the team is not ready to be on-call. The system works when on-call can handle most of the production issues themselves.
1
3
Show this thread
jiten
@jiten
6. When the on-call system works well, the team pays attention to other teams' services, helping break information silos. The system also reduces individual dependency on projects and improves overall teamwork.
1
2
Show this thread
jiten
@jiten
5. We often use the on-call engineer's time to fix technical or operational debt in our product. We often ask on-call engineers to create documentation, increase automation coverage, and write playbooks to make the next on-call job easier.
1
4
Show this thread
jiten
@jiten
3. Lots of learnings for the engineering going on-call - business context, debugging tools, analytics, etc. 4. Our whole stack becomes debuggable and better documented
1
2
Show this thread
jiten
@jiten
2. Reliable and fast responses and resolutions because one person is responsible at any point. Fast resolutions for issues benefit customers and build trust with them. In an ops-focused business, all engineers shouldn't be getting support calls, and we shouldn’t block the ops.
1
1
Show this thread
jiten
@jiten
On the call, the roster gives comprehensive benefits. I have continued using an on-call roster with weekly rotation (or multiple rosters in larger teams). Here is how I feel this adds value: 1. Removes context switch and increases productivity for engineers
1
5
Show this thread
jiten
@jiten
They didn't stay up all night and monitor things but didn't put their phone on silent mode at night. We traded uncertainty for our customers and everyone on the team with a system that allowed everyone to execute without context switches.
1
5
Show this thread
jiten
@jiten
Someone had to know who is the best person to fix the issue if they were going to start waking people at night. I made my first proper on-call roster with this team. One developer from our group was available on call in case of any issues.
1
4
Show this thread