Why you should check a domain's history before buying it
7 min readHow the Web Works
Domains are secondhand goods. Search engines, browsers and mail servers all keep long memories about names, and you inherit them at checkout.
Getting started as a developer is well documented, with tutorials, bootcamps and a thousand courses covering every first step. The top of the ladder is well documented too, in architecture books and conference talks by staff engineers. The stretch in between is not. You can ship features all day and still feel like seniors know something nobody ever wrote down.
They do. It isn't another framework and it isn't algorithm puzzles. It's understanding what your tools are doing underneath: what actually happens when you press Enter, how a website remembers you're logged in, why your deploy doesn't show up until someone hits refresh. That's the missing level, and this blog covers it one plain-English deep dive at a time, no CS degree required.
7 min readHow the Web Works
Domains are secondhand goods. Search engines, browsers and mail servers all keep long memories about names, and you inherit them at checkout.
5 min readSecurity
A properly designed website doesn't know your password — and it can still check that you typed it right. The elegant idea behind hashing, explained without a CS degree.
6 min readHow the Web Works
DNS, TCP, TLS, HTML parsing, rendering: the journey from typing a URL to seeing the first pixel on screen.