Methodology

There are lots of articles and even books about the art of writing clean code. But when exactly is code actually to be considered clean? Today I’d like to give you a brief overview of how you can assess and improve your code quality. I should perhaps note that writing good code, and therefore this article, is independent of the programming language used and is rather methodical in nature. However, for more detailed information, I recommend that you really get a book on the subject. The standard advice on this is certainly “Clean Code” by Robert C. Martin. ...

When you’re at the beginning of your career as a software developer, like me, you probably know the feeling that you’re being overwhelmed by everything you want to learn. Especially at the beginning it is often not easy to work productively and to learn why I want to show you which methodologies I have developed for myself. Even though I use my own experience, my approach is of course not limited to the industry. ...

Todays focus is on how you can test your applications automatically to detect bugs early and improve your code quality. I want to introduce you to the concept of automated testing. In order to make the content accessible to as many users as possible, I will not use code examples and concentrate purely on the underlying idea instead. Once you understand them, you will have no problems implementing the concept in the programming language of your choice. ...

As a software developer, you are probably well aware of the feeling: You are overwhelmed by the amount of interesting stuff you want to test and learn. But I’m sure that this problem is also very common in other fields. If you feel like me, you may read and watch various books, blog articles or online courses, but you won’t really keep much of their contents. In today’s article, I’d like to help you to learn more effectively about the topics that really interest you, wasting less time. ...

After I introduced Scrum in my last article, today will be about Kanban. Like Scrum, Kanban is an agile software development methodology and I have to say that I apply the principles I present today to most of my personal side projects. Kanban is Japanese and can be translated as “billboard”. Kanban was first introduced by Toyota in the automotive industry and is now mostly associated with just-in-time concepts. But I don’t want to bore you with historical details, I want to show you the usage in software development. ...