It’s Day 2 of my journey learning Rust as a longtime C# developer, and today I took the plunge: I installed Rust and created my first project. The whole thing felt a bit like unpacking a new toolbox—familiar enough to recognize the tools, but different enough that I had to check the manual.
Today marks Day 1 of my 42-day challenge to learn Rust—with a twist. I’m not approaching this as a blank-slate beginner. I’m bringing along years of C# experience, mental muscle memory from countless LINQ expressions, async/await workflows, and enough IEnumerable
But now? I’m learning a language that doesn’t have a garbage collector, doesn’t throw exceptions the same way, and thinks null is a bad idea.
I’ve spent over a decade writing C# and building solutions on .NET. But for six weeks, we will step outside the managed world of garbage collection and runtime JIT to dive headfirst into Rust—a systems programming language that promises performance, safety, and no nulls.
Over the course of 42 days, we will learn something new about Rust every single day. We will fight the borrow checker. We will make mistakes. And I will blog it all from the perspective of a C# developer trying to make sense of it.
What will happen when you take a C# developer, hand them a curly-brace language that loves safety and hates nulls, and give them six weeks to figure it out?
You will experience a journey filled with rewired brain circuits, redefined mental models, and a newfound respect for the compiler. This will mark the beginning of my 42-day dive into Rust, a daily learning challenge that will push me out of my .NET comfort zone and into a language that promises to be both frustratingly strict and beautifully empowering.
Welcome back, Razor Pages fan. Today, we’re looking ahead at where htmx and ASP.NET Core are heading in the grand scheme of web development. Spoiler alert: Server-driven apps are making a comeback, and htmx is leading the charge.
Alright, developer friends, it’s time to talk about something we all know is essential but often neglect until it’s too late: security. htmx makes building interactive apps with ASP.NET Razor Pages a breeze, but if you’re not careful, you could be opening your app to all sorts of nasty vulnerabilities. Let’s make sure that doesn’t happen.
Welcome back, fellow developer! So you’ve embraced htmx to make your ASP.NET Razor Pages more interactive and excellent. But just like anything in development, things can go wrong. And when they do, you need to know how to fix them. Today, we’re diving into debugging HTMX requests and responses like a pro.
Hey there, fellow .NET developer! Today, we’re talking about how you can take your ASP.NET Razor Pages apps from “meh” to “whoa!” with htmx. We’re diving into seamless navigation, enhancing user interactions, and even doing a little case study to show you how this all comes together. Ready? Let’s go.
Alright, web developers. Today, we’re stepping into the ring to watch htmx go toe-to-toe with the big players: React, Vue, and Angular. But this isn’t a deathmatch. It’s about finding the right tool for the right job. Let’s get into it.
Welcome back, fellow .NET enthusiast. Today, we’re talking about why htmx is a game-changer for ASP.NET Core developers. If you’re tired of drowning in client-side frameworks and you want something simpler without sacrificing performance, you’re in the right place.