The Franconian
Coder Studio

Software development is all about solving problems, but not every tool or technology is a one-size-fits-all solution. From programming languages to frameworks and architectures, the choices are endless, and each comes with its own strengths and limitations. Writing an online shop in C or using Go for kernel development might sound absurd, but it highlights the importance of matching tools to tasks. The real challenge lies in understanding the problem, questioning outdated routines, and choosing the right tools for the job. In this article, I’ll discuss why a tailored approach is essential for creating effective solutions without unnecessary compromises.

In 2023, web standards are making a noticeable comeback, and tools like Lit are at the forefront of this shift. Unlike traditional frameworks that reinvent the web, Lit embraces existing standards, making web components more accessible and practical. With Lit, you can build web UIs without complex build steps—everything runs directly in the browser. This simplicity, combined with its lightweight design, makes Lit a compelling choice for developers. Material Web 1.0, built on Lit, further demonstrates its potential. While Lit may not replace major frameworks anytime soon, it’s a refreshing reminder of the power of web standards. In this article, I’ll explore why Lit is worth a closer look for anyone passionate about modern web development.

When it comes to side projects, the question of the ‘best’ tech stack is a common dilemma. But after years of experimenting, I’ve realized the answer is straightforward: choose whatever you enjoy! Side projects should be fun, productive, and a space for learning. Whether it’s Go, which I’ve used professionally for nearly a decade, or Zig, which I’m exploring for fun, the key is to embrace the diversity of technology. Don’t chase trends or the next big thing—focus on what excites you. In this article, I’ll share why enjoying the process and learning from different stacks will ultimately make you a better developer.

Kubernetes has become synonymous with modern infrastructure, but is it always the right tool for the job? While its scalability and automation are appealing, they can lead to a lack of critical thinking about core metrics like user behavior, response times, and redundancy. As a fan of straightforward solutions—like Go for programming—I believe infrastructure should be simple, predictable, and easy to understand. In this article, I’ll share why I’ve often opted for simpler setups using tools like Traefik, NATS, and Ansible, which have proven to be highly scalable and maintainable without the overhead of Kubernetes. Sometimes, boring infrastructure is a sign that everything has been done right.

Testing during development is essential, but real-world scenarios often defy expectations. To ensure my code performs reliably in production, I’ve adopted a strategy I first used almost a decade ago: writing the same logic twice. Ideally, two developers independently implement the logic, sometimes even in different programming languages. Only when both versions produce identical results in production is the code accepted. While this approach isn’t practical for every function, it’s invaluable for critical systems. Whether running both implementations continuously or temporarily after updates, this method complements traditional testing. In this article, I’ll discuss how double programming can enhance fault tolerance, error detection, and safety in production environments.