Farsight #01: Vertical Single Use Features

A horrifying idea, normally a classes inherit props/values for a feature, the process of a button or trigger some action.

For a quality of the product functioning, would making it more reliable to have AIs rebuild whole paths for new features to be completely stand alone and not dependent on code that's already in the repo?

Example, want new "find network hops" but we already have network tools, but the need is to make sure there's no regression and breaking of other tools, so the AI scopes and builds out down that vertical path, just that 1 tool button.

Like, it does hurts the brain, like "what about maintainability, entropy or readability?" cause say you need to update all tool buttons, well that might be in the past and may not really be standard practice, cause who was going to "maintain" that anyway, can spend the 30 seconds to even 30 mins for the feature to be re-build due to low execution of code cost.

Like sounds completely like madness, to bloat a code base like that, but that's off the premise of how it was previously done without that type of tools, like using wood carving tools when there's lave to build table posts. (we may be at the stage of drill vs impact drill)

Like, really unintuitive or corruptive, but i bet we'll start seeing stuff like that soon, if not already has happened.

This might not be the path of what will happen, but something is there in that area, and can be one path we may want to keep an eye out for.

Just a fun thought.