3 ms·
Communicate ideas clearly, concentrate on the Nouns, not the Verbs, particular technologies, frameworks, languages are important, but not that important. Under
by rswail 6y ago
Communicate ideas clearly, concentrate on the Nouns, not the Verbs, particular technologies, frameworks, languages are important, but not that important.
Understand the domain(s), if you don't, find out who does, talk to them, write it down, read it back, until they say you've got it.
That way, you can take new ideas and new requirements and see how they fit into the domain, how it will need to stretch or flex to accommodate them. You will be able then to explain it to both the people wanting the new thing as well as the people that have to build and deploy it.
Making things flexible is the hardest thing, you don't want things to be too flexible, it makes it too hard to keep something running. But you also don't want it too rigid, it makes it too hard to adapt.
- twhitmore 6y agoI would strongly recommend the Strategy pattern, over modeling fixed concrete configuration structure. At least the first time or couple of times you encounter a complex configuration requirement, in a new domain. Spring XML or similar can offer pretty much a gold standard for being able to instantiate & parameterize strategies or simple executable ASTs.