applied-learning

The process of real learning

Eli Kent

19 Jul 2025 — 1 min read

TL;DR: Last night I felt despondent. This morning I feel exhileration. Real learning - the overwhelm of the heap, the processing of the stack, the clarity of a returned value.

This isn’t about memorizing tools or copying workflows. It’s about going into the machine. That takes time. And pressure. And sitting in the dark for a while.

At first, learning feels like the heap. Just raw data.

But over time, a stack starts to form. I push frames onto it. I make connections with old frames. Return values come back. Meaning expands. Something new is made.

Git as railroad

I struggled a lot to understand Git. Once I started thinking of it in terms of a railroad — with stations, tracks, train cars, and a station master (Git) — it finally clicked. This post captures how I first made sense of Git. 1. git init builds a train station in the

How I turned my tag soup into a map

TL;DR: I had no clear tagging system for my blog posts — just scattered labels with no structure. By grouping tags into buckets like Domain, Focus Area, and Tool, I built a system that not only organizes my posts but also reflects my mental model of computer science. The Problem

Buffer v. disk - a visceral lesson.

TL;DR: Turns out, “unsaved” really means “nonexistent” — I chased a phantom file for 10 minutes. I created and opened in VS Code a .ps1 file from the terminal. PS C:\Users\EliKent\Documents\WindowsPowerShell> code sandbox.ps1 But I didn’t actually save it — I just started typing.

Heaps and stacks in Python

TL;DR: Heaps are where a Python program stores its data. Stacks are where the computations happen. This post breaks down what happens in RAM when Python runs a simple script. The Script: name = "Eli" x = 2 + 3 y = sorted([name, x]) Step 1: python script.py When

Read more

Git as railroad

How I turned my tag soup into a map

Buffer v. disk - a visceral lesson.

Heaps and stacks in Python