This blog is about collecting, persisting and showcasing my thoughts and potential solutions to software development topics for my own reference as well as a means for recruiters and potential employers to get to know more about me as a developer.
I expect it to be mostly about how to increase code quality and reduce room for error. It could go a little like this:
While actually proving the correctness of software would be the gold standard, that is still impractical in day-to-day enterprise software development. However, there are many ways to tie down the correct business logic statically at compile time through the type system and other compiler features, make human (developer) error more obvious by programming declaratively rather than imperatively and checking data and behavior dynamically during runtime (automated tests, validation), just to name a few.
Apart from this general theme there may be reviews of meetups and possibly some longer trains of thought pertaining to my github toy code snippets.
Well then, let’s see how this goes…
