Re:Ask HN: What would make your development 10 times or 100 ...
by jka on Wednesday June 24, 2020 @07:06AM
(#23626524)
As an additional thought: it would be useful if such a service could be applied retroactively to historical software concerns as well.
This would provide the community with more of an ability to maintain and improve the existing software that we all rely on to be robust, effective and secure.
For example, if a software project had decided to introduce component X at some point in the past, a platform like this could identify that (and the historical reasons for the selection) as a blocker for necessary changes to support a subset of the current user community.
That could lead to a task list for the changes required to rectify the architecture, and discussions about the subsequent tradeoffs involved in those changes - and so the process could continue, iteratively.
This would provide the community with more of an ability to maintain and improve the existing software that we all rely on to be robust, effective and secure.
For example, if a software project had decided to introduce component X at some point in the past, a platform like this could identify that (and the historical reasons for the selection) as a blocker for necessary changes to support a subset of the current user community.
That could lead to a task list for the changes required to rectify the architecture, and discussions about the subsequent tradeoffs involved in those changes - and so the process could continue, iteratively.