Posts
-

Reading Error Stack Traces Is a Skill
Reading a stack trace is a skill, not a reflex. How to read error traces step by step and find the bug faster than guessing.
-

Why Your Local Environment Does Not Match Production
“It works on my machine” wastes time and erodes trust. Why local and production environments differ, and how to close the gap without overengineering.
-

Code Reviews Without the Ego
Code reviews feel personal when they should not be. How to review code without attacking the author, and how to receive feedback without defensiveness.
-

The Case for Boring Technology in Small Projects
Boring technology — PostgreSQL, a single VPS, server-rendered HTML — helps small projects ship faster and cost less. Launch boring, migrate later.
-

Logging Is Not Debugging
Console.log everywhere is not debugging — it is guessing. Why structured logging and debuggers serve different purposes, and when to use each.
-

How to Estimate Programming Tasks When You Have No Idea
Estimating programming work is hard when you have never built it before. A practical approach: break it down, add buffer, track accuracy, give ranges.
-

Command Line Tools Every Programmer Should Know
Grep, sed, awk, jq, xargs, curl — six command line tools that save programmers hours every week, yet most courses never teach them.
-

The Hidden Cost of Copy-Pasting from Stack Overflow
Copy-pasting from Stack Overflow works until it breaks in production. Why understanding what you paste matters more than where you found it.
-

Why Junior Developers Should Learn to Read Bad Code
Reading bad code is not a punishment — it is a career skill. Why junior developers who learn to read messy codebases advance faster than those who only write clean code from scratch.