CTRL ALTSCtrl Alt Solvereal-world developer knowledge
SearchJoin
Ctrl Alt Solve — Don't just ask what to do. Learn what developers experienced when they did it.
M

Mohit Agarwal

@mohitagarwal

Cloud Engineer

0 followers0 following0 expertise score6 posts

Writing postmortems so the next on-call sleeps better. (north)

C#.NETAzure

Experiences shared

Discussion3d ago·1 entry

we handled search ranking when the cache went cold

We ran into this around search ranking when the cache went cold. The error rate looked fine in the average and ugly in one slice. Two percent of requests reset upstream with no application exception. Idle timeouts between the proxy and the app had drifted apart. Aligning them stopped the intermittent failures within an hour. We added a panel for reset reasons so the next page is faster to find.

0 views0 likes0 comments0 bookmarks
#search ranking
MMohit Agarwal
Read →
Comparison26d ago·1 entry

vs Postgres for short-lived job locks

We needed locks so queue workers did not process the same job twice. Redis SET NX was faster under load and easy to expire automatically. Postgres advisory locks were simpler operationally for our small team. Failover behavior mattered more than raw latency in our case. We chose Postgres first, then moved hot paths to Redis later. Pick the lock store you can operate confidently at 3am.

73 views0 likes0 comments0 bookmarks
#queues#postgres#redis
Mohit Agarwal
Discussion27d ago·1 entry

typed API clients reduce bugs more than OpenAPI docs?

Curious how teams balance generated clients and hand-written SDKs. OpenAPI docs help humans, but drift still sneaks into multi-repo setups. Generated clients catch breaking changes in CI before they hit prod. They can also create noisy diffs when schemas change often. Plain fetch wrappers stay flexible but hide contract mismatches. What has actually reduced production bugs on your teams?

156 views0 likes0 comments0 bookmarks
#api#typescript#dx
Mohit Agarwal
Recommendation28d ago·1 entry

for a practical observability stack for a 6-person team

We need traces and logs without hiring a full-time SRE. Right now we stitch screenshots from three tools during incidents. OpenTelemetry looks right, but the vendor choice is unclear. We ship weekly and cannot afford a six-month platform project. What has worked for small teams that still sleep at night? Especially interested in cost ceilings and onboarding time for juniors.

235 views0 likes0 comments0 bookmarks
#sre#opentelemetry#observability
Mohit Agarwal
Showcase29d ago·1 entry

our internal changelog bot

We built a Slack bot that turns merged PRs into weekly release notes. It groups changes by label and pings owners when summaries are missing. The first version was a cron job; now it reacts to GitHub webhooks. Sharing the architecture and the parts that still need polish. Biggest win: PMs stopped chasing engineers for release copy. Feedback welcome if you have run changelog automation at scale.

145 views0 likes0 comments0 bookmarks
#opensource#devtools#slack
Mohit Agarwal
CareerSep 11, 2026·1 entry

from my first year as a staff engineer

Influence without owning every PR took longer than I expected. Saying no clearly protected the roadmap more than heroic overtime. Writing the docs nobody wants to write still changes team speed. I spent more time unblocking others than shipping my own features. Staff work is often invisible until the org feels the absence of it. Still learning how to measure impact without vanity metrics.

201 views0 likes0 comments0 bookmarks
#career#leadership
MMohit Agarwal
M
Read →
M
Read →
M
Read →
M
Read →
Read →