>>>I agree completely with Rick in this regard. Those backdoor tricks only increase technical debt and will for sure bite you back at one time.
>>>
>>>Even better try to upgrade the affected data with non-ambigous values if possible.
>>>
>>>"Always code for the maintener:
>>>Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live."
>>
>>... and of course there is that possibility that YOU might be the poor soul that needs to maintain that bit of code.
>
>And then he has the benefit of knowing which moron wrote it, and where he lives...
In fact yes to the first, but no to the second, because this person has passed away a few years ago and and that had put the company he worked for in a very dire situation.
Now I have to assess the debt we are in. Based on past mistakes the company is loosing several hundreds of Euros, at times thousands, on a daily basis. A routine customization which should take maximum one day of work (average speed programmer) takes at least one full week, but mostly much longer.
The previous developers have constantly focused on doing something quickly. Now we are focusing on building good design. As the first strategy seems to give you quick results, it very soon becomes clear that you are loosing more and more time, the bigger the application gets. The more thought-through approach seems to be more time consuming in the beginning, but later rewards you with a complete system that will pay you off instead of increasing debt. Overtime has stopped and we are more productive then every before.
Also the previous code had to do many late hours and overtime constantly to
Christian Isberner
Software Consultant