Aniruddha

Last week I read this post by Mitchell Hashimoto arguing that everyone should know SIMD.

I've played ping pong for many years.

There is a lot written about how engineers use Claude Code.

Everyone is doing more with AI.

In Dragon Ball Z, the Saiyans wear a scouter, a little eyepiece that reads someone’s power level and puts a number on it.

When I was in undergrad, Google was the hottest company in tech, and I wanted in.

When I joined Pocus we ran a typical technical screen, two coding interviews back to back.

Tokenmaxxing is the belief that an engineer who spends more on AI is worth more, and in the past few months it has become how some companies tell themselves their AI investment is working.

Last week I read this post by Yao on being on-call and I couldn't agree more!

The first thing every software engineer learns about good code is don't repeat yourself.

When I joined Twitter, there were no public levels.

I spent most of college doing competitive programming.

I have a non-American accent.

The last time I thought seriously about engineering career ladders was at Mixpanel.

One of the things I found myself thinking about a lot when I was leading engineering at Pocus was when to create formal teams.

Engineering teams are drowning in PRs and nobody wants to say it out loud.

A little under three years ago, I joined a tiny startup called Pocus.

In any kind of stateful distributed system, the problem of mapping a key to a set of machines is pretty common.

Benjamin Franklin once said — “Those who give up essential accuracy for temporary speed deserve neither speed nor accuracy”.

While the Go programming language specification only states that the iteration order over maps is not guaranteed to be the same across invocations, Go maps in action goes a step further to say that the order is randomized.