Most of us think that applied knowledge consists of learning generalisable principles and THEN looking for places to apply them.
In this view, cases are simply examples of the principle in action.
But check this out:
Conversation
Replying to
Do you consider software development to be an ill-structured domain?
Based on this, I feel like it has a lot of the attributes being described for an ill-structured domain.
Tailoring concepts to context, poor top-down structures, high variability from case to case, etc.
1
3
Replying to
I think software engineering is ill-structured, yes. Computer programming maybe less so.
“Software is about developing knowledge more than writing code.” csc.gov.sg/articles/how-t
Replying to
Very interesting. I think this has been my approach so far as a dev. Look at and dissect many cases and try to extract knowledge from them.
It also reminds me of StarCraft 2. Many beginners would be extremely confused by advice because it's all highly situational and contextual.
1
3
SC2 ex: beginners would often blanket apply advice then come back and say, "I did the thing, why did I still lose?".
And more advanced players would chime in with something like, "you should have done this instead in this situation because of x, y, z", or point out other flaws.
1