Testing in Rails usually forces a tradeoff. Factories are flexible but slow. Fixtures are fast but messy.
Kasper Timm Hansen built something that tries to fix both. Oaken is a different way of thinking about test data entirely.
What if your dependencies were so small… that you weren’t afraid of them?
Kasper Timm Hansen talks about why he aggressively limits lines of code and keeps gems tiny on purpose. Smaller code is easier to trust, understand, and even take over.
One of the biggest challenges in Rails apps: your models never stop growing. User. Account. Order. They just keep expanding.
Kasper Timm Hansen explains why the real job is breaking things apart before they get out of control.
What’s the difference between a concept and an abstraction?
One has direction. The other can feel like loose parts.
Kasper Timm Hansen uses a simple analogy to explain why most code feels harder than it should. Better modeling starts with clearer ideas.
After leaving Rails Core, Kasper Timm Hansen started building much smaller tools. Not bigger frameworks. Not complex systems.
Small gems with very specific ideas behind them. He explains why those tiny projects can actually have more impact.
What if the problem isn’t CSS… what if it’s how we think about CSS? Lyra talks about how treating it like a “not real language” limits what developers even try to build.
That mindset leaves a lot of capability on the table.
A lot of the web runs on layers of JavaScript that don’t need to exist.
Buttons. Hover states. Simple interactions.
Lyra Rebane breaks down why CSS can handle more than most developers think and why that matters for performance.
Most developers think they understand CSS.
But they’ve only seen a fraction of what it can do.
Lyra Rebane shares how pushing the limits of CSS completely changed how she approaches programming and security.
CSS isn’t just for styling anymore. People are building games, logic, and entire systems with it.
Lyra explains how a weird little corner of the internet turned CSS into something much bigger.