I help coders, code
You are a C# programmer. You want to create quality code. You want to make sure it is maintainable in the long run. You are not happy with just delivering features. You want your code to be able to grow with the problems it solves. You want to become a true craftsman. I’m here to help
Learn with me, create better code, and grow your programming skills.
A good software craftsman is all about…
You are the expert
As a programmer, you have the responsibility to deliver value to the customer. You know how to build the software and deliver a good product.
We must take pride in the process. As programmers, we must make sure we don’t give the customer false assumptions.
It is easy to make a quick n’ dirty solution. But it will end up biting us sooner rather than later.
Bad code slows down the whole process and eventually stops it completely.
As a craftsman, you should be proud of the code you check-in. When others look at it, it is obvious that it is made by a programmer that is a master craftsman.
The customer knows about his problem domain. You know about programming. To get great results a collaboration is required.
A productive partnership is essential for good results. We must strive to not be on the receiving end of a pipeline of tasks.
Download one of my cheat sheets to grow your code
10 strategies to work with legacy code
The ultimate architecture starter kit
YEARS OF EXPERIENCE
You want to create quality code. You want to make sure it is maintainable in the long run. You are not happy with just delivering features. You want your code to be able to grow with the problems it solves. I’m here to help
Working with Frederik Banke has taught me that there is a significant advantage in writing code using good practices. He can explain very advanced techniques in software engineering in a way that is easy to understand.
MY BEST STUFF
Featured Blog Posts
Adding Unit-tests to a legacy codebase
Working in a legacy codebase can be a daunting task. But there are ways to make it less errorprone
Scaling .NET core with await/async
await/async is a great way to scale your .NET code. But you need to use it in the right way to get the benefits
Monolith or Microservice?
Is microservices always the right choice? It might not be, monoliths have benefits that should not be disregarded