
Who’s writing this
About
Why write when you can show? Then agentic dev came along, and the excuses stopped working.
Listen to this page · 6 minutes, read by Brian, an AI voice
I started with science experiments in the backyard, which morphed into pulling apart computers, then writing software for them. I eventually settled on making computers move and understand their environment through my Mechatronics1 and Robotics studies - including sending a wheeled robot full speed into walls or copying human movements on industrial robot arms. Eventually computers became smart enough that I could actually work with them in natural language and images, thus the MSc in AI. I’ve spent decades discovering why and how things work.
After years of “too much work”, “who’s going to maintain it” and “social media posts are boring”, along came agentic dev2 and I ran out of targets to blame.
What I work on
Reasonably complex applications, mostly, in whatever language the job needs. I collect software languages (like I do human ones - more on that shortly). Though my favourite is C# (and the .NET platform3 since 2005), maybe because it was my first? Let’s not get started on C and C++ - always fun when the application crashes and the motor decides to get stuck on maximum throttle. My day job’s focus is .NET Blazor4 and distributed applications.
What I keep coming back to is the seam between engineering practice, ISO standards (27001, looking at you)5, and tooling - the parts of delivery that quietly decide whether a team ships monthly or quarterly or not at all because a change breaks all access controls!
Using AI to engineer (fun) stuff
Most of what I write about here. Not “AI will replace your job and everyone you love”, but the more interesting and less glamorous question: where do agents actually fit into an existing SDLC?
That includes all the boring stuff like: reviewing reams and reams of code, triaging vague customer reproduction steps (none whatsoever), migrating to the latest tech, writing more reams of boring test code, keeping up all that documentation everyone says they’ll do tomorrow but tomorrow never comes, and exploring what updates will break the code next.
But it also includes the fun stuff: my personal anecdotes, hints at what I do in my spare time, and all the things that didn’t end up fun because something broke or wasn’t possible yet.
This site is a fusion of the two, built with Anthropic’s Claude Opus6, read aloud by an AI called Brian, and supervised by Ms Claudie Mittens who is a purely hypothetical kitten (maybe one day I’ll have a real Ms Claudie Mittens).
When I’m not engineering
I love collecting languages both human and computer ones. I’m a Greek speaker (spoke it exclusively till 5 years of age), English speaker (boring), fluent Japanese speaker (I’ve spent a lot of time living in Japan - 日本語が大好きです~!), and absolute beginner in German and Irish - maybe one day I’ll translate my posts.
While not using my brain, I love to hike up a random mountain or soak up some O2 on forest trails. Somehow I also have time to explore the world: I’ve visited nearly every continent and spent more time on planes than most people spend in cars. But the truth is I usually tell people to ask me where I’ve not been.
Shoved between all that brain work and travel, I would be happily exploring RPGs on Xbox, PC, or even Switch 2 🎮
What you won’t find here
Have to say this part: “there won’t be any employer code and related bits on here”. I focus on my personal hobby projects while sticking to concepts, patterns and write-ups - generalised deliberately, and written from my own projects where there’s code to show.
Also:
- 🔍 No analytics - not like I’m selling ye something.
- 🍪 No cookie banner - there aren’t any to eat, I’ve given them all to Ms Claudie Mittens.
- 📰 No newsletters, no emails, no Discords, no group chats, this is exclusively a one-way parasocial7 relationship!
Keeping our parasocial relationship alive
You can keep pace with me at:
Hope that gave you enough to make fan art of me now 😉. Send them on, I’ll have Opus screen them for me (sorry Opus)!
Footnotes
-
“1960~”, Yaskawa Global Site, accessed 11 October 2026 - “Legendary engineer Tetsuro Mori applied in 1969 to register as a trademark ‘Mechatronics,’ a phrase coined by the combination of mechanism and electronics.” It is the engineering of machines whose mechanics, electronics and software are designed as one thing. Robots, mostly. ↩
-
“Overview”, Claude Code Docs, accessed 11 October 2026 - “Claude Code is an agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools.” Agentic means the AI does the work itself, a step at a time, where a chatbot would only tell you how. ↩
-
“Introduction to .NET”, Microsoft Learn, 10 March 2026 - “.NET is a free, cross-platform, open-source developer platform for building many kinds of applications.” In 2005 it was neither cross-platform nor open source: that was .NET Framework, which ran on Windows alone. ↩
-
“ASP.NET Core Blazor”, Microsoft Learn, 11 November 2025 - “Blazor is a .NET frontend web framework that supports both server-side rendering and client interactivity in a single programming model”. The part of a web page that would usually be JavaScript is written in C#. ↩
-
“ISO/IEC 27001:2013 Information Security Management Standards”, Microsoft Learn, 7 December 2023 - “ISO/IEC 27001 is a security standard that formally specifies an Information Security Management System (ISMS) that brings information security under explicit management control.” The page describes the 2013 edition; the current one is from 2022. ↩
-
“Claude Opus”, Anthropic, accessed 11 October 2026 - Anthropic’s Opus model, at version 5.5 when this was written. ↩