On.System Architecture
System Architecture (and it’s subfield Software Architecture) is a discipline which is surprisingly poorly covered. In a sense, it is still more an art than a science, and usually requires somebody intimately familiar with practical systems, to tell what’s to do and what’s to avoid when building a system.
IT Hares have lots of experience in both Software Architecture and more general System Architecture, and are trying to share their knowledge (and more importantly, their feelings) about them.
MOG GDD (a.k.a. Business Requirements)
October 26, 2015 by • “No Bugs” Bunny
Quote:
You don’t “make” a violin. It is barrels and benches which are “made”. And violins, just like bread, grapes, and children – are born and raised.
Another Quote:
The very first step should be to understand what exactly you're going to achieve.
Filed under: Book: D&D of MOGs1st beta of Vol. I-IIIOn.System ArchitectureRequirement analysis
Read moreMulti-threading at Business-logic Level is Considered Harmful
September 7, 2015 by • “No Bugs” Bunny
Quote:
However, the window for triviality is very narrow: for example, even going into two interrelated mutexes instead of one, can easily make multi-threading non-trivial
Another Quote:
Technically you are able to jump to any point of your program, but the variables you see may (and if you have a multi-threaded bug – will) differ every time you jump there.
Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingDebugging
Read more