Two years ago programmers were all like, “What I do is code.
the mental image i've had in my head that corresponds with your graph at the end is picturing the codebase as breathing
inhale, the system grows, the genie does its things and new features sprout
exhale, the system condenses, people go in, reassert understanding and control
and so the cycle goes
make sure not to inhale too deeply or it can be overwhelming
The visible vs invisible work analogy is very helpful. Thanks!
Hey Kent, great piece! Really helped me understand your Futures concept.
Wanted to ask you something: how are you so confident that feature development also slows down with genies if we don’t do the invisible work?
Is it your experience so far? Or have you seen it somewhere else?
I’ve seen it over and over. Until coding models are trained with “cost of future change” as part of their objective function this will continue.
the mental image i've had in my head that corresponds with your graph at the end is picturing the codebase as breathing
inhale, the system grows, the genie does its things and new features sprout
exhale, the system condenses, people go in, reassert understanding and control
and so the cycle goes
make sure not to inhale too deeply or it can be overwhelming
The visible vs invisible work analogy is very helpful. Thanks!
Hey Kent, great piece! Really helped me understand your Futures concept.
Wanted to ask you something: how are you so confident that feature development also slows down with genies if we don’t do the invisible work?
Is it your experience so far? Or have you seen it somewhere else?
I’ve seen it over and over. Until coding models are trained with “cost of future change” as part of their objective function this will continue.