Daniel Raniz Raneland
@raniz.se
Software engineer/architect, public speaker, dad, beer brewer, triathlete
I have restructured my online presence a bit. I wrote a new site in Astro and put it up at raniz.se, then migrated my blog there as well so everything is now in the same place. You can read a bit about it on the first blog post on the new site. buff.ly/uAPF2Bo
I have a new blog!
New design, new framework and new URL. With intact history
raniz.se
#Code has always been a liability, so with it apparently being a commodity now means that we're commoditising liability!
Non-Americans: Do you use #BritishEnglish or #AmericanEnglish #spelling for APIs and #documentation? I am gearing up to publish the Rust assertion library I've been slowly working on for the past two years or so, and I am currently working mostly on documentation and some polishing.
Day three of DevSum, just for the speakers today. Haddon knot.
Day two of DevSum, which means it's a #tieday. Sporting a Trinity knot today because I was in a hurry after breakfast and didn't have time to do something more intricate.
Conference (DevSum) in Stockholm this week, which means #tieday for the rest of the week. Starting out with a Thinking knot for today. Presenting about how to modernise legacy software systems with the Strangler Fig pattern tomorrow at 15:30.
That's a wrap of Devoxx Greece for me. Gave my presentation this morning and now I'm on my way back home. Haddon knot for #tieday.
#tieday in a rainy Athens today. I'm here to present about pipeline patterns and anti-patterng tomorrow. Sporting an Eldredge knot with a tie from Japan
I've started toying with local models ever since I got my nvidia graphics card working in the Incus containers I use for development last week. #agenticcoding #claudecode #llms #agents #development #softwaredevelopment -- Photo by Vicky Sim via Unsplash
Are there any good ways of securely transferring files between two parties that don't necessarily trust each other fully? #datatransfer #security #opsec #zerotrust #infosec #cybersecurity
Adding manpower to a late software project, makes it later. We've known this since Fred Brooks wrote it in 1975—the opening sentence is a direct quote. Yet many projects still try to add people to meet deadlines, and it fails. #Development #SoftwareDevelopment #Productivity #TeamTopologies #DevOps
Spring is in the air (I can tell because of my pollen allergies...). Trying out a Carnation knot today for some flowery goodness. #tieday
So, the source code for Claude Code was leaked. Here are my takeaways:
credentials-collector.evil-hacker.com
Celebrating your milestones is almost as important as reaching them. --- Image by Harrison Chang via Unsplash
All developers are familiar with (and mostly loathe) "boilerplate", but have you ever thought about where the word comes from and what code and boilers have in common? -- Image: Sky via Unsplash
When embarking on a modernisation journey with your legacy system, it is important to have a plan for (roughly) what you want the system to look like when you're finished.
Without significant change of process and/or methodology, your new system will become your next legacy mess. (Photo: Stacy via Unsplash)
The system you're replacing your ageing legacy with will be worse than what you have today. This is because you are very likely to overcompensate for what you dislike in your current system. (Image: "The magic roundabout" in Swindon, by Alby via Wikimedia Commons, CC BY-SA 2.0)
A lot of rewrites fail because they are cancelled before completion—and a half-finished rewrite is, in most cases, not usable. (Photo by Sébastien Lavalaye via Unsplash )
