@molly0xfff I'm sorry. I can't hear you over the sound of the (googles) Yamaha DTX 402 slamming away in the background of your blog post.
K
kianryan@oldbytes.space
@kianryan@oldbytes.space
Posts
-
damn, i just knew i was forgetting something! -
Graffiti conviction for Australian woman who stuck googly eyes on sculpture -
Shiver me timbers!!!After nearly six years at Tom's Hardware I am heading off for new horizons!@biglesp
Sweet. -
Just waiting for the DNS to finish flushing, but kianryan.co.uk is now hosted on @beasts.Just waiting for the DNS to finish flushing, but kianryan.co.uk is now hosted on @beasts.
Pushed from a GitHub Action, but that now gives me the flexibility to do things I couldn't do with Github Pages, such as:
Leigh Hackspace - Or How I Learned To Stop Worrying, and Embrace The Chaos
As alluded to on the Now page, after my RTA in 2022, the sporting side of my life slowed down. In the early part of my recovery, I walked in to Leigh Hackspace, which was in it’s early days of coming out of Covid lock down. A Hackspace is peculiar...
Kian Ryan (www.kianryan.co.uk)
https://www.kianryan.co.uk/2026-03-03-leigh-hackspace.txt
Plain text blog posts.
The height of 2026 technology.
-
I'm going to be offline for probably the next week.@biglesp Remember to take a Psion with you. Rest up.
-
the argument "but you're also no longer using a fountain pen to write" against hand-written code is silly to me.@mntmn It's the invasion in to my own space. I've played, and honestly, I'm in a similar space to yourself. I mostly code in C#, and have a NeoVim based workflow. I'll dip in to Visual Studio for legacy Framework projects. My workflow is /efficient/, and allows me to review my own work, and that of my co-workers. It lets me breathe and think. It uses LSP (primarily Roslyn) and a bunch of plugins to flow nicely.
Occassionaly I'm asked how my setup works, and I'll happily talk it through. It's not that complicated, and someone will play with it for a bit, and may find things they like, or not. Again, their choice. On a one on one basis, we can have reasonable discussions, usually with a coffee. There's been learnings on both sides.
For work, we run rules that you're responsible for your own commits, wherever that code comes from. That was true before, and it's true now. So far, it's held up. We had a couple of small incidents, and some re-education was applied.
But by Gods, the minute that I pop my head above the general internet parapet and say I'm /not/ using an AI driven workflow, as a personal preference, you realise how much you're against the grain.