luckystarr
Joined 15 years ago
Joined 15 years ago
These sorts of refactorings take time, even more so if done by "committee". The good thing is that explicit interfaces have to be created thereby (hopefully) increasing adaptability and resilience over time.
Honest question, I don't really get how this would improve my work flow.
() Spec and (variably coarse) implementation plan are already grounded in code reality and are commited.
I wonder which trend will be winning though. I personally won't bet on quality.
I did subagent based removal tasks a few times. These were the ones that required the least amount of input or thinking from me, because the requirements are abundantly clear. "Remove this part of the code without breaking any other part or by porting the tests done with it onto another system."
In these situations the code acts as the bookkeeping ledger itself, and coordination complexity is almost a no-brainer.
Nothing else has value to them apart from capital and its "profitable" usage, so the fundamental reason why corporations even exist, to collectively bring about real world value takes a back seat.