Quite a while ago I had a good talk with an colleague about “to log or not to log – that is the question”. 😉 That was a longer discussion, and a lot of questions had been raised: Shall we do logging? What shall be logged out? Should we create a log library by ourselves to […]
Tag: maintainability
How to do sensible logging in c#
In last post about Are Extensions the beauty or the beast? I added a screenshot that showed a class implementing the repository pattern. This actually also showed the implementation of our log strategy. I did get some questions why we do it like this and what are the benefits. Let’s have a look onto how we do it: […]
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 […]
MVC & Databinding: What’s the best approach?
We’ve got some serious movements in the product development. And it goes straight in the right direction. There are three product teams, all of them want to use at least a variant of MVC. What is right approach? MVC? MVP? Passive View? Supervising controller/ presenter? MVVM? There are a couple of questions to be answered before being […]
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 […]