Five sample posts demonstrating the CMS. Click any post to read it.
There's a reflex that most developers have: encounter a problem, open a browser tab, type it into Google, click the Stack Overflow link, copy the answer, move on. I spent years doing this and called it productive.
The tutorials end at "it works on my machine." That's where the hard part begins.
I came to Go from Python. Not because Go was trendy, and not because my job required it — I picked it up because a side project of mine kept running out of memory on a $5 VPS, and I was tired of paying more for what felt like a tooling problem.
I spent four months building a content management system I never shipped.
The first project I ever put on the internet had a bug on the homepage. The navigation broke on mobile. The error messages were embarrassing — "something went wrong" for every possible failure, because I hadn't thought through the error paths. I knew about all of these problems before I launched.