3 ms·
I remember early uml courses (based on pre Java / OO languages). They were all about modules and coupling dependencies. Trying to keep them low, and the modules
by agumonkey 4y ago
I remember early uml courses (based on pre Java / OO languages). They were all about modules and coupling dependencies. Trying to keep them low, and the modules not too defined. It seems that the spirit behind this (at least the only one that make sense to me) is you don't know, so you just want to avoid coupling hard early, leave the room for low cost adaptation while you discover how things will be.
- ThalesX 4y agoWhenever I start a greenfield frontend for someone they think I’m horrible in the first iteration. I tend to use style attributes and just shove CSS in there, and once I have enough things of a certain type I extract a class. They all love the result but distrust the first step.