<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://radan.dev/</id><title>Radan Skorić's website</title><subtitle>A blog about software development and the Ruby programming language</subtitle> <updated>2026-07-15T11:56:11+02:00</updated> <author> <name>Radan Skorić</name> <uri>https://radan.dev/</uri> </author><link rel="self" type="application/atom+xml" href="https://radan.dev/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://radan.dev/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Radan Skorić </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>When broadcasting a Turbo refresh is not enough: faster UX with versioned immediate updates</title><link href="https://radan.dev/articles/turbo-versioned-updates" rel="alternate" type="text/html" title="When broadcasting a Turbo refresh is not enough: faster UX with versioned immediate updates" /><published>2026-07-15T00:00:00+02:00</published> <updated>2026-07-15T11:53:48+02:00</updated> <id>https://radan.dev/articles/turbo-versioned-updates</id> <content type="text/html" src="https://radan.dev/articles/turbo-versioned-updates" /> <author> <name>Radan Skorić</name> </author> <category term="articles" /> <summary>The simplest way to make a page collaborative with Hotwire and Rails is to subscribe to changes and broadcast a refresh when relevant models update. But that approach sometimes causes a problem. This post explains the refresh approach, the problem and the fix. The full monty. The problem Let’s assume we’re implementing a game because that is an example I have handy. My little MinesVsHumanit...</summary> </entry> <entry><title>RubyConf Austria and the future of Ruby conferences</title><link href="https://radan.dev/news/ruby-conf-at" rel="alternate" type="text/html" title="RubyConf Austria and the future of Ruby conferences" /><published>2026-06-11T00:00:00+02:00</published> <updated>2026-06-11T12:49:24+02:00</updated> <id>https://radan.dev/news/ruby-conf-at</id> <content type="text/html" src="https://radan.dev/news/ruby-conf-at" /> <author> <name>Radan Skorić</name> </author> <category term="news" /> <summary>To get from Zagreb, where I live, to Vienna, where RubyConf Austria was happening: drive 173km to Graz, take a right and go for another 198km. Sure, I’ve glossed over two country borders and some other details, but that’s mostly it. It’s pretty straightforward, unlike how the conference got me thinking about the future of Ruby conferences. But I’ll get to that. Day 1: The Vienna Ruby Meetup ...</summary> </entry> <entry><title>Practical CSS: simplifying UI code with pseudo-classes</title><link href="https://radan.dev/articles/css-pseudo-classes-practical-examples" rel="alternate" type="text/html" title="Practical CSS: simplifying UI code with pseudo-classes" /><published>2026-04-08T00:00:00+02:00</published> <updated>2026-04-08T16:05:43+02:00</updated> <id>https://radan.dev/articles/css-pseudo-classes-practical-examples</id> <content type="text/html" src="https://radan.dev/articles/css-pseudo-classes-practical-examples" /> <author> <name>Radan Skorić</name> </author> <category term="articles" /> <summary>pseudo, adjective: being apparently rather than actually as stated CSS pseudo-classes are like regular classes in that they can be used to select DOM elements. They’re unlike regular classes in that you can’t see them in the HTML. They select elements dynamically, based on their own rules. This is what makes them powerful. I really like them because they let me remove dynamic presentation lo...</summary> </entry> <entry><title>How well are the tests covering the code?</title><link href="https://radan.dev/articles/how-well-are-tests-covering-the-code" rel="alternate" type="text/html" title="How well are the tests covering the code?" /><published>2026-03-18T00:00:00+01:00</published> <updated>2026-04-18T14:57:25+02:00</updated> <id>https://radan.dev/articles/how-well-are-tests-covering-the-code</id> <content type="text/html" src="https://radan.dev/articles/how-well-are-tests-covering-the-code" /> <author> <name>Radan Skorić</name> </author> <category term="articles" /> <summary>The student asked: “Master, what should I pay more attention to, my tests or my code?”. The master said: “I cannot answer you when you ask the wrong question.” The student thought “oh fuck, here we go again”, but just said: “But master, is it not one or the other?” The master said, “If a bridge is suspended from the pillars. Which is more important the walkway or the pillars?” The student t...</summary> </entry> <entry><title>Why frozen test fixtures are a problem on large projects and how to avoid them</title><link href="https://radan.dev/articles/frozen-test-fixtures" rel="alternate" type="text/html" title="Why frozen test fixtures are a problem on large projects and how to avoid them" /><published>2025-12-09T00:00:00+01:00</published> <updated>2025-12-09T20:37:00+01:00</updated> <id>https://radan.dev/articles/frozen-test-fixtures</id> <content type="text/html" src="https://radan.dev/articles/frozen-test-fixtures" /> <author> <name>Radan Skorić</name> </author> <category term="articles" /> <summary>Tests grow to thousands All make their claim on fixtures Frozen by demands An ancient Japanese Haiku about a common problem with software test fixtures Act 1: The problem, frozen fixtures Fixtures have a lot going for them: super fast, clearly structured, reusable across tests … That last one is also the source of a common problem in large test suites. Every time you change fixtures you ...</summary> </entry> </feed>
