Senior Software Engineer at Engineius
I still do plenty of DevOps alongside it, so I end up working on the application code as well as the infrastructure it runs on. This is where I keep my notes and write things down before I forget them.
Sections
- Projects What I’m building and what I’ve shipped.
- Blog Longer pieces on infrastructure and engineering, plus daily updates.
- TIL Short notes on things I had to look up.
- Notes Cheatsheets and quick references I keep coming back to.
- Reading Books and docs I’m working through, and what I made of them.
- AI Guides Guides I’ve had AI write to teach me a project rather than build it.
- Watching Films & TV Series I’m working through, and my thoughts.
- Now What I’m up to at the moment.
Learning with AI
The guides in AI Guides were written by AI, and that’s the point of them.
I didn’t ask for working code. I asked to be taught: what to learn, what to build next, and how I’d know it worked. What comes back reads like a tutorial written for exactly the project I’m doing, with the reasoning behind each decision left in, and I still have to build the thing myself.
It’s the part of this that I think gets overlooked. Most of the argument is about how much code gets written for you, and much less about how good it is at explaining something you’re halfway through learning.
First one up is building a Telegram reading bot in Go, which is the plan behind Reading Bot.