3 ms·
Bullet points for requirements and one "box, swimlane, and cylinder" diagram (with no standard elements) for analysis and design if you're on a 'strict' project
by RandyRanderson 4y ago
Bullet points for requirements and one "box, swimlane, and cylinder" diagram (with no standard elements) for analysis and design if you're on a 'strict' project.
If we can't even decide on language A or B, CSV or JSON, ... (these are implementation artifacts that are essential to the solution), what hope do we have of even understanding- no even seeing that there is a problem in the other disciplines (requirements, analysis, etc) of technology delivery?
If we make it another 100 years, we'll look back at this time and view what we are coding now as wattle and daub huts whereas a century from now we'll be erecting the analogue of technological skyscrapers (but probably not good ones, if I'm being realistic).
- jnash 4y agoI predict that the future development landscape won't be much different from today. In the same way that the development landscape today isn't much different to how it was 60 years ago. The only difference will be faster hardware, allowing people to use even slower languages to do just enough to get typical web applications to work. Developers will still be 95% focused on their own convenience instead of focusing on the business/end user. Developers will still "solve" problems by adding another layer of complexity and copy/pasting code they don't understand from somebody else. Developers will still be coding in languages that are around today (because legacy).