I'm in a spot now where we are engineering on the fly practically to catch emerging gotchas that were missed during requirements gathering. I'm digging through legacy data to import from backups of a broken process, GIGO but this kinda thing fits to your point. Systems evolve s the domain and business processes get thoroughly examined. Classes, methods, interfaces all define constraints of the system but being able to iterate over the detail, find out what's really needed, what's available and how it fits together in a business system that's where iterative architecture comes into play - just my 2 cents. Thought provoking article for me tho.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm in a spot now where we are engineering on the fly practically to catch emerging gotchas that were missed during requirements gathering. I'm digging through legacy data to import from backups of a broken process, GIGO but this kinda thing fits to your point. Systems evolve s the domain and business processes get thoroughly examined. Classes, methods, interfaces all define constraints of the system but being able to iterate over the detail, find out what's really needed, what's available and how it fits together in a business system that's where iterative architecture comes into play - just my 2 cents. Thought provoking article for me tho.