The other day a collegue of mine came to me, being pretty enthusiastic. He was amazed about his latest changes to the code. As I am the responsible architect, it is my turn to have a look onto the changes. So we sat together and did so. Usually we create our code via straight rules and best practices. As […]
Category: Don’t make me think
Coding principles: These assembly/ folder structures… suck.
We need to move people from time to time between products. It can be tough when you move from SSIS/ Sql/ SAP stuff to job-based Excel automation. How can we make a hard task easy? The very first things that developer see are the assemblies and the folder structures. Let me first put some bad examples for assembly […]
What’s wrong with that: Do not only code the happy case
Last pull request I’ve opened was some kind of disappointing. When going through the code files, I detected a lot of… questions marks above my head. We do use pull requests for two reasons actually: The need for doing review sessions goes down dramatically The team learns to improve each other while not being upset when anthing […]
What’s wrong with that: I am not that good in naming classes
Quite a while ago I was sitting together with another programmer to review the brand new sources. It was created as a prototype, a proof of concept. The original product has been rewritten for several reasons: The UI shall be completely redesigned The codebase had to be replaced due to bad maintainability and bad performance Yes, certainly if there would […]
What’s wrong with that – robust and unquestionable code
I recently had a session about proper exception handling and, more intensively, defensive programming. As exception handling is one of the most important as well as one of the most unattented tasks of a developer, the session was based on real code from the code base of the products. Don’t get me wrong here: It is not […]
Don’t make me think vs don’t think about it
I believe it was five years ago when I was sitting in a plane with a printed version of Don’t make me think. This book from Steve Krug from 2000 can be considered as kind of benchmark. When I read something about it I was impressed by two things: This guy does exactly what nobody […]