4 ms·
Re: systems are almost never explicitly designed with an exit plan in place. How do you plan for the future when nobody can accurately predict the future? I re
by tabtab 6y ago
Re: systems are almost never explicitly designed with an exit plan in place.
How do you plan for the future when nobody can accurately predict the future? I remember where it was claimed that OOP UI api's could "last forever" because they were an abstract interface rather than implementation. However, they couldn't handle the stateless-ness of the web because OOP is inherently stateful. It's almost like having a printer API that assumes a color printer, and suddenly it's being asked to translate into black and white. You'll lose output meaning without reworking everything. Abstraction usually has to make assumptions, and these assumptions may turn out wrong down the road.
Re: no one wants to budget for those activities
True. That's one thing an org can and should plan for: money to pay for upgrading. In other words, you cannot predict future technology, but you can safely predict that adjusting to the future requires resources the vast majority of the time.
- spdionis 6y agoNext question: how many resources?
- cced 6y agoRe: How do you plan for the future when nobody can accurately predict the future? It isn't so much 'planning for the future' as it is documenting the present. What are the things that you are doing _today_ which haven't been documented. Processes and procedures are often left undocumented because, well, ask Bob he knows how to do it. ... when Bob goes to retire it becomes a whole different discussion.
- rightbyte 6y agoYe I have noticed this bullshit antidocumentation attitude everywhere. It is like something people make up as comfort since secretaries and technical writers were sacked in the distant past and people are not even trying to keep things in order anymore. It has got way worse becouse of Scrum and constant churn living in the now and not planning two sprints ahead.