Daniel Raniz Raneland
raniz.se
Daniel Raniz Raneland
@raniz.se
23 followers 19 following 97 posts
Software engineer/architect, public speaker, dad, beer brewer, triathlete
Posts Media Videos Starter Packs
Time for another #tieday. Went a bit advanced with an Intrinity knot today. It's essentially a Penrose knot tied on top of a Trinity knot - long ties only 😅

Neon Oni's latest new album Nihilism is blasting out of the speakers today.

Bonus pics from TDC in Trondheim where I was on Monday.
Time for another#tieday again. The beard is getting a bit long so I'm off to trim it (and the hair) in an hour.

Tie is tied in a Rachel knot, named after the inventor's wife.

Have a nice day!
Friday is here, the sun is shining, the trees are getting colourful, Vintersorg is playing in the headphones and the necktie is tied in a Haddon knot..

I'm having a fantastic #tieday, hope yours is equally good!
Short tie for #tieday today so went with a Trinity knot because in doesn't use that much material.
Short tie for #tieday today so went with a Trinity knot because in doesn't use that much material.
Time for another #tieday. Sporting a Truelove knot today. As far as I know it has nothing to do with true love. It just happens to be the inventor's surname.
Does anyone know what this prompt actually does? It doesn't seem to be keeping me signed in since I last signed in a few hours ago...
#tieday in Borås today. Me and two of my colleagues are attending a conference about digital product passes in textile. Very exciting since I know practically nothing about this.

Oh and I'm sporting an Eldredge knot today. The tie is from Stenströms, but that's as much as I know about its origins.
Oh my, is it Friday again already? I guess that means time for another #tieday.

Found a new knot today: KES knot (courtesy of Mr. C's Another Knot). I rather like it.

Which one's your favourite?
Today's #tieday together with my colleagues in Karlshamn.
As a result of this, I spent most of my coding time yesterday refactoring and cleaning up code that I had previously created with the help of Claude Code. There were also a few bugs and design issues that needed to be fixed.
When coding with agentic AI I feel I'm missing out on the inherent design review that comes with writing APIs and structuring code. Just reviewing generated code doesn't trigger the same reflection on the design as writing it myself - and I don't just auto-accept changes without review
Absolutely, glad you liked it!

You can find the slides here
raniz85.github.io/talks_pipeli...

There's a PDF download button in the menu at the lower left of the window (only shows on hover).
raniz85.github.io
Vacation is over and I'm back at work. That means that I'm wearing a necktie for today's #tieday!

Eldredge knot.
I guess this is what the various instruction/guidelines files are for, but in my experience putting something in there is hit-or-miss since it seems to be ignored quite often.
They will remember this and not do the same mistake again (hopefully at least). A coding agent might find this instruction somewhere in the context for the rest of the session. But once I exit the session or it compacts the history it'll be gone and I'll have to provide the same instruction again.
If I'm teaching TDD to someone unfamiliar with it I can instruct them and give them reasons. If, for example, they throw an exception instead of returning a default response in a new method I can tell them that this doesn't make the assertion fail and as such doesn't count as a test failure.
One of the worst parts about working with coding agents is that they don't learn anything.
If you want to come but haven't booked a ticket yet, the organisers were kind enough to give you discounts for following a speaker!

ti.to/aafr/nc25/di...
NewCrafts 2025
Tickets available on Tito
ti.to
I'm giving my highly appreciated workshop on TDD at NewCrafts 2025 in Paris on November 3-7.

Will I see you there?
Last day before vacation and it's a #tieday. Got one day to calm down tomorrow and then we're taking the ID.4 on a road trip to Italy.

See you in 5 weeks 😁
This inconsistency means that I need to look up the documentation whenever I use them (unless I can copy an existing task somewhere), because I don't use them often enough to remember which task uses which names - and looking at different tasks is useless since there is no convention.
Note the difference in casing, the use of different names for the same thing (destination and target), as well as the inconsistent use of a suffix in the parameter to overwrite files.