Design decisions
When architecting a system, it is inevitable to make certain high-level design decisions.
Some of these decisions, if they’re wrong, can lead to the re-architecturing and re-writing of the whole system some months later, so there is an incentive to keep things rather generic. On the other hand, trying to make system too generic is just another recipe to disaster (usually expressed in terms of missed deadlines and unmanageable code).
IT Hares try to describe certain not-so-obvious architectural decisions, and some considerations which should be kept in mind while making them.
Over-Generic Use of Abstractions as a Major Cause of Wasting Resources
September 1, 2011 by • “No Bugs” Bunny
Abstract:
Trying to be too generic can easily cause many-fold inefficiencies.
Quote:
It was a quiet night and I was downloading a 2G ZIP file with Internet Explorer...
Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingOptimizations
Read moreOverused Code Reuse
March 1, 2011 by • “No Bugs” Bunny
Abstract:
When done imporerply, code reuse can cause severe problems, including loss of life.
Quote:
Reusing code from other projects or (even worse) from 3rd-parties SHOULD NOT be taken lightly. Or else...
Filed under: On.System ArchitectureDesign decisionsOn.DevelopmentDevelopment Philosophy
Read moreFrom Occam's Razor to No Bugs' Axe
January 1, 2011 by • “No Bugs” Bunny
Quote:
Fight Features. …the only way to make software secure, reliable, and fast is to make it small" — Andrew S. Tanenbaum
Another Quote:
If you do not have a concrete case of how a feature will be used – do not provide it. Yet.
Filed under: On.System ArchitectureDesign decisionsOn.DevelopmentDevelopment PhilosophyDevelopment Processes
Read moreTo DLL or Not To DLL
November 1, 2010 by • “No Bugs” Bunny
Abstract:
Are DLLs a ‘holy grail’ or a ‘necessary evil’?
Quote:
It might not be your fault, but it is your problem.
Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingTips and Tricks




