Re: another hint of quantum consciousness

On 9/15/2024 12:00 PM, Edward Rawde wrote:

Maybe, but you're likely to find that they attract users who think it will make their lives easier.
Maybe it will at some future time.

Few "sizeable" projects are handled by single developers.
VCSs impose order on projects where multiple entities are
examining, correcting and modifying a single document store.
This includes provisions to notify folks who happen to be
working with a particular "module" so they are alerted that
someone else has made a change to it; presumably this means
the "new" version now works better (more correctly) than the
version you might be using so its in your best interest to
see what's happened to the module before moving too far
down range.
Of course, this only works when there is a discipline imposed on
the development team.  Many people don't like having to play by
"rules" so disdain anything that imposes same.
I am tickled when a colleague discovers a problem or an improvement
to a piece of code or a bit of hardware as that saves *me* from
having to make the same discovery (or, worse, risk NOT making it!).
It's also an excellent mechanism for rewinding the development
clock to determine where a particular problem crept into the
design.  (We had a problem some years ago when someone made
a presumably simple change to a FET used on one of the boards
that, later, presented problems.  "Why was this change made?
Is the problem because of the change or just brought to light
by it??")
It's also a requirement for many structured design policies
(ISO9000, et al.)