The Codebase Is just the Receipt for Every Bad Business Decision. Let’s say you join a company as the new CTO. On day one, you open the codebase. And it is bad. 😐 Not “we should improve this slowly” bad. Proper bad. There are no useful tests . Deployments are scary . One service has not been touched in years because everyone is afraid of it. The database has columns that look like someone named th

Let me give you a situation. You have 7 engineers and around 11 months of runway . You have a few paying customers, but you are still not sure whether you have product-market fit. Your biggest customer wants an important feature in the next 8 weeks . Now your engineering team proposes this architecture: Microservices Kubernetes Event-driven communication Separate databases Independent deployments

If you're using JSON for your LLMs, you are likely overpaying for your API usage. I’ve always treated JSON as the default for data transfer. But while working on optimizing LLM workflows recently, I learned that it can be incredibly expensive. ou are paying for every curly brace { } , quote " , comma , and repeated key. Recently, I came across TOON (Token-Oriented Object Notation). The difference

Understanding open source licenses is crucial as it determines how software can be used, modified, and distributed. This guide explores the various types of open source licenses, their legal implications, and how to choose the right one based on your project’s goals. Software licenses dictate the terms under which software can be used, modified, and distributed. Choosing the right license is a cri

Ever tried editing a Google Doc simultaneously with ten colleagues? If so, congratulations—you're already acquainted with this technology! Before you lose faith in collaborative tech, let's introduce your soon-to-be favorite acronym: CRDTs—Conflict-Free Replicated Data Types. The Problem: Everybody Wants Control Imagine you and your coding team simultaneously editing the same GitHub README. You up

A Survival Guide to Blame Your Team and the Universe "Congratulations! You’ve discovered a new dimension where physics doesn’t apply." Let’s be real: your local environment isn’t a development setup—it’s a magical realm where dependencies resolve themselves, environment variables grow on trees, and all edge cases politely disappear. But the moment your code touches production? It’s like sending a

A friend invited me to join his startup, having issues like no funding and leadership conflicts. I offered help with funding and management for a pay cut, but some things made the deal impossible. I walked away, understanding that if a company won’t invest in talent, they can’t expect top results. A few days ago, an old friend reached out to me about a project he was working on. At first glance, i

I was going through my old bookmarks and saw some blogs about promising Node.js technologies. Some of those turned out to be industry leaders, while I barely remember others. Let's see which projects thrived, and which didn't, and, most importantly, why they became popular or lost their momentum. It’s been 10 years since I first set off on my software engineering journey back in 2014. Just the oth

Versioning isn’t just a random string of numbers tacked onto each software release. It’s a powerful tool that shapes how users experience updates, how developers handle dependencies, and how a project grows over time. Introduction to Versioning If you're a software veteran, you already know what versioning is and why it is important. You probably know the different types of versioning (or maybe no

People might argue that JSON Schema is overkill or outdated. But in this article, we'll explore that it is not the case and understand how it is often overlooked. First, hear me out — You are already using a schema Think about it: if your end users are API consumers, whether they’re external (think Rapid API) or internal teammates using your (micro?)service’s APIs, they’re counting on responses to

Table of content Introduction Understanding the CAP Attributes a. Consistency b. Availability c. Partition Tolerance The CAP Trade-offs a. Consistency and Availability (CA) b. Consistency and Partition Tolerance (CP) c. Availability and Partition Tolerance (AP) Real-World Examples of CAP Trade-offs a. CA Systems: Relational Databases i. MySQL ii. PostgreSQL b. CP Systems: Distributed Databases i.

Unleashing the Power of Collaboration and Growth in the Tech World Introduction: The tech world is an ever-evolving landscape, with countless opportunities for growth and learning. One of the most valuable resources for developers is the community that surrounds them. Developer communities are forums where individuals can connect, collaborate, and innovate together. In this article, we will explor

Let's begin with a quick overview of HTTP/3. HTTP/3: HTTP/3 was introduced in 2020 and is the latest version of HTTP. It is based on the QUIC protocol, which was developed by Google. Like HTTP/2, HTTP/3 uses a binary format and supports multiplexing and server push. However, it also includes several other features that aim to improve performance and security, such as improved congestion control an

There are a lot of blogs and video tutorials on how to set up Filebeat and Logstash with self-hosted Elasticsearch. But when I tried to connect the same thing with Elastic Cloud, I faced too many problems. Because there was very little discussion about that in the community forums like StackOverflow or their own forums. First, we'll be discussing why and where do we need Filebeat and Logstash. The

This article covers: Why to move to Amplify? How to deploy an app and all its features. Before moving to the how part, let me tell you why I moved my frontend applications (React, Vue etc.) to AWS Amplify. Why Amplify? For deploying my frontend applications, I've been using various things like EC2 , CloudFront , etc. But there are problems with managing everything on our own in an organization: Th