Abhirama’s Blog

Below tweet appeared on my timeline. https://twitter.com/therealfitz/status/1301278933497909248 The tweet brought back a quote(paraphrased from memory; I do not know the author).

In life, we have to do many pointless things; at least pointless for us.

Good Will Hunting is the story of Will(Matt Damon), a janitor at MIT, who is an undiscovered maths savant.

In this post, I will walk you through the principles to keep in mind while designing processes.

No one has an incentive to tell you hard-hitting uncomfortable truths about yourself that you are blind to.

What role does code quality play in the outcome of a business?

Organizations do not give attention to their internal communication architecture.

Software developers love abstractions.

FUD stands for fear, uncertainty, and doubt.

The three pillars of scalability are statelessness, idempotency, and coding to interfaces.

TLDR; there is no way.

This post walks you through a framework for adopting new technologies.

The key to building a great team lies in ejecting the stereotypical portrayal of the role from your mind, objectively figuring out the qualities needed for success in the role, and ruthlessly going after that.

Today, while developing software, external calls are a given—your code talks to external HTTP services, databases, and caches.

Top management loves centralization.

The programming world heralds laziness as one of the virtues of a programmer.

What is the point of life?

All software abstractions, sooner or later, leak.

Charlatan - a person, falsely claiming to have special knowledge or skill.

Two members of a criminal gang are arrested and imprisoned.

Are you in awe of the Jedi programmers who seem to produce bugless code?

How do you run effective Platform Engineering teams?

Whether one is an optimist or pessimist is dictated by genetics.

How do you create a quality assurance strategy?

AWS re:Invent is an annual event hosted by Amazon in Las Vegas.

I was reading this Twitter thread on Ben Horowitz’s new book on culture.

In HackerNews, I read yet another write-up on daily standups and how they suck.

I believe keeping an eye on the competition is a good idea.

All of us wish to be in a state of zen.

The post is going to be an intuitive introduction to Big O notation.

The post is a listicle on product and feature development in no particular order.

I have been pondering for a long time - Why is startup experience invaluable?

Security by obscurity is one of the most common ills that plague the software industry.

Distributed tracing means different things to different people - depends on whom you ask.

This post is a thought experiment in designing a great meeting room experience.

How many times have you been part of a conversation where someone goes - “Let us use a queue like Kafka.”

Creating software is easy; creating quality software is hard.

The CAP theorem says that in the event of a network partition, a distributed system can be either consistent or available, not both.

kettle-2178442_640.jpg There have been tomes written on team management, but, if you whittle it to the core, it boils down to the following.

Moving from your own data center to a public cloud can be a daunting task.

Confused how to choose an open source library?

Before you ask, I do not have any.

Software abstractions that developers create should leak enough to let non-developers design the right product experience.

Amara’s law says - “We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.”

Are you focussing on developer productivity?

Are you confused as to whether to do a daily standup or not for your team?

As a young fledgling startup, you should not be building layers of abstraction over the technology that you are using; on the contrary, you should be going all in.

“Make it large” is the mantra these days, but when it comes to releasing software, think the opposite, make it small.

Over-engineering is ripe in the software industry; this mainly manifests in three ways: 1.

This is the second part in a series on open source software.