Becoming a tech lead was the goal from pretty early in my career. I had a clear picture of what the role was. More responsibility, more influence over the work, more of the interesting problems landing on my desk because someone had to figure them out and that someone, finally, would be me. It read like the natural next step. The thing you graduate to once you're good enough. What that picture did
This section is the map for the rest of the book. The five stages introduced in the 1.1 chapter overview (parse, analyze/rewrite, plan, portal, execute) are traced here through the actual code: which functions implement each stage, and in what order they get called. The mechanics of each of the five stages are unpacked in later chapters. Here, only the skeleton matters: how a backend starts up, ho
PostgreSQL Internals · Chapter 1 Query Processing Suppose a client sends SELECT * FROM users WHERE id = 1. The path that single line travels before coming back as a result row is longer than you might expect. Inside the PostgreSQL backend, that SQL goes through a five-stage pipeline. Backend entry and dispatch. The backend receives the message from the client and decides which processing path it s
SQL is widely known for data querying and manipulation but systems do grow; data becomes larger; processes become repetitive and operations become sensitive. SQL has some features which enables it to be considered a fully fledged programming language. Some of the features which I discuss in this article are procedures, functions and transactions. Each of these concepts serve distinct purposes. Sto
Introduction Placing RDS in a private subnet protects it from unauthorized external access — but it also means you can no longer connect directly from your developer machine. This article walks you through a step-by-step guide to securely connect to a private-subnet RDS (PostgreSQL) instance using AWS Client VPN. Developer PC │ │ UDP 443 (TLS / Mutual Certificate Authentication) ▼ Client
_ Timeline - 2 Months _ PLAN DSA - C++ - Striver sheet , developer map for Leetcode. Development - Backend - JS ,MONGO - Developers roadmap for backend , Projects - Developers Roadmap. Low-Level - Rust - Developers Roadmap , Rust Book , Projects - CodeCrafter. Development - TS , SQL ,DOCKER , AWS, MY GITHUB MY LEETCODE
I have been meaning to upgrade my personal site to Astro 6 for a while. The release notes sat in my open tabs for weeks, and every time I sat down to do it, I found an excuse to work on something else. This week, I finally ran out of excuses. I carved out an afternoon, ran npx @astrojs/upgrade, crossed my fingers, and expected a smooth ride. The dev server crashed immediately with a cryptic error
For years, I called myself a web designer. Then a developer. Then a digital consultant. None of those titles ever felt quite right. Because clients weren't just asking me to build things. They were asking me to solve problems. Slow sites, broken checkouts, confusing navigation, teams that couldn't figure out how to update their own content. That's when I realized what a technology solutions profes