Software Engineer (4+ yoe) | Web, Cloud, Gen Al

Nepal
Did sub 2h Half Marathon day before yesterday at Wipro Bengaluru marathon (1:56:40) strava.app.link/pOSVdBAQO6b
3
53
Pankaj Thapaliya retweeted
22
215
4,932
185,955
Pankaj Thapaliya retweeted
Google has an authorization system called Zanzibar that decides who can access what across products like Drive and YouTube. One of the most important services there... One of the key pieces of Zanzibar is an index called Leopard Index, and that is what makes access checks faster. The idea behind it is the core; let's dig deeper... In any Google product, authorization comes in two fragments. It has notions of users and groups. Users can be part of groups, and groups can even contain other groups. Say Alice is in payments-team, which is within backend, which is inside engg. To check whether Alice is in engg, you have to walk up that chain one hop at a time. With deep nesting, that means many lookups across many machines on every access check. Leopard's indexing system avoids the walk by doing the work in advance. It keeps two lookup tables. 1. member -> group - maps a user to the groups they belong to directly. Alice maps to payments-team. 2. group -> group - maps a group to every group nested under it, at any depth. engg maps to backend and payments-team, plus itself. To check whether Alice is in engg, look up both sets and see if they share anything. Here, they share payments-team, so the answer is yes. That is two lookups and one overlap check, no matter how deep the nesting goes. You would have guessed the trade-off that they are making here :) It is the classic. Now, to stay fresh, the index combines a periodic full rebuild with a stream of recent changes, so new memberships show up quickly. The cost is on the write side. Placing one group inside another means updating many precomputed entries. That is a good trade for authorization, since checks happen far more often than membership changes. If you have a slow graph walk on a hot read path, precomputing the answers may be worth considering. A mental model worth remembering. Hope this helps.
32
57
1,285
80,818
Okay finally 🥲
We're adding support for AGENTS.md to Claude Code. Starting today in version 2.1.277, if there is no CLAUDE.md in a folder, Claude will check for and use AGENTS.md. You can toggle this behavior in /config.
12
Pankaj Thapaliya retweeted
We're adding support for AGENTS.md to Claude Code. Starting today in version 2.1.277, if there is no CLAUDE.md in a folder, Claude will check for and use AGENTS.md. You can toggle this behavior in /config.
2,060
2,637
31,324
5,622,960
Pankaj Thapaliya retweeted
Me when that one guy still looking at the code asks why we have both a `createdAt` and `created_at` column in the `users_v2` table
93
287
8,797
549,838
Pankaj Thapaliya retweeted
We built our notification system on SQS instead of Kafka in 2023. Everyone said we would regret it. Kafka is the standard. SQS does not scale. Two years later: We process 4 million notifications per day on SQS. Our monthly bill is $180. Kafka would have cost us $2,400 per month plus 40 hours of maintenance. We have had zero outages. Zero rebalancing issues. Zero broker failures. Sometimes boring technology wins.
85
99
2,148
202,344
Can be easily done with your cards as well. It's official donation portal opened by gov of Nepal. pmdrf.nchl.com.np/
official disaster relief fund in case someone wants to help
130
Pankaj Thapaliya retweeted
In 2021, Nimsdai and Kili Pemba stood together with eight fellow Nepalis atop K2 singing the national anthem. Now Nimsdai and Kili Pemba are gone. This moment of unity and Nepali pride will live forever.
Nirmal Purja MBE
26
275
2,756
84,201
Pankaj Thapaliya retweeted
Docker is one of the best things that ever happened to software development. You can just literally spin up a PostgreSQL container, Redis, MongoDB or whatever you need for a project instead of going through the traditional route of installing everything directly on my machine and configuring it manually.
69
93
1,656
105,687
Pankaj Thapaliya retweeted
S3 transitioned from eventual consistency to strong consistency. No downtime required, across exabytes of data. "if something happens only once in a billion requests, that means it happens multiple times per day within S3" Werner has a great article on the process (link below)
Personally I’m more interested in how S3 transitioned from eventual consistency to strong consistency That’s a pretty significant upgrade aws.amazon.com/blogs/aws/ama…
5
42
922
122,728
Pankaj Thapaliya retweeted
There was a time when Google used to give links, Not Answeres. There was a time when figuring out things was a skill. There was a time where "What to search" was a skill. There was a time when we used to go throught 10s and 20s of chrome tabs just to figure out and make things work. That satisfaction was a feeling 🤌🏻
31
16
492
14,228
Pankaj Thapaliya retweeted
SECURITY ADVISORY — TanStack npm packages A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package. Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down. Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys. If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised: • Rotate cloud, GitHub, and SSH credentials immediately • Audit cloud audit logs for the last several hours • Pin to a prior known-good version and reinstall from a clean lockfile Detection — the malicious manifest contains: "optionalDependencies": { "@tanstack/setup": "github:tanstack/router#79ac49ee..." } Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root). Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level. Full technical breakdown, complete package and version list, and rolling status updates: github.com/TanStack/router/i… Credit to the security researcher for responsible disclosure.
135
965
3,804
3,922,959
Pankaj Thapaliya retweeted
We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity. This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.
4,599
11,612
128,338
24,133,771
Pankaj Thapaliya retweeted
Great news to start off the new financial year. @Razorpay is now embedded natively inside @OpenAI’s Codex, an industry-first for any Indian payments company. A developer prompts "build me a fitness app with a ₹499 one-time payment." Codex builds it. Razorpay handles the payments. No separate integration, no dashboard-hopping. If AI makes creation effortless, monetisation should be just as simple. India has 6 million developers & weekly Indian users of Codex 4x'd in two weeks this February. We’re building for this shift where more people can create, launch, and earn without friction. We have always enabled businesses so that their payments are smoother, easier, simpler & faster and Codex just got added to that already illustrious list.
65
65
1,302
209,797
Pankaj Thapaliya retweeted
Announcing JSON Alexander A really good JSON viewer browser extension. → Easily open/collapse objects → Copy property path → Access JSON in dev tools console → Funny hairy finger cursor github.com/wesbos/JSON-Alexa…
HEADS UP. Popular JSON formatter extension has started injecting geolocation tracking and donation UI into websites Reddit thread seems to think they are also swapping tracking IDs for affiliates (a-la honey) Uninstall and switch to another one
55
56
853
129,637
Saturday went well because I’m rebuilding my fundamentals from scratch @Hiteshdotcom’s backend structure explanation is far clearer and more systematic than how I’ve approached things over the past four years. Highlight of the day: DTO 🚀🙌 @ChaiCodeHQ @piyushgarg_dev @nirudhuuu
3
60
Pankaj Thapaliya retweeted
Petition to rename useEffect() to doNotUseEffect()
31
9
427
31,428