@iStarr@nicolefv Based on that. wouldn't it be more like "Continuous Accelerator in Chief" ?
Then again, we just haf StarWars day, and I've heard some like to use StarWars-based titles (at least according to Wookiepedia)!
@tottinge Part of 'master & minions' was also about optimizing 'utilization' of specialized "resources" to capture static system 'knowledge' in one form(at) & handoff to next-in-line to 'translate' to another format (adding SOME more detail, but LOTS more redundancy) -- soo wasteful!
@tottinge Too many folks then thought programming ("coding") was merely translating someone else's design into source-code (rather than a design activity).
๐ฅด
@tottinge I recall Martin Fowler speaking in XP's early days, responding to Qs about Pairing as inefficient (2 people doing the work of 1)!
He said "Programming is not a typing activity! It is a *thinking* activity -- and a *creative* one at that (unlike typing copy)!"
@davefarley77 Defining "steps to deliver a solution" is process (design), it is not solution requirements, nor solution design.
Best not to equate nor conflate ANY of those three things (solution reqts != solution design != process for reqts/design/delivery)
@patrickdebois@swyx Some hits:
Domain Modeling & Software Process Management
- https://t.co/njroYwTIW4
Laws of Software Process [in CACM 2000]
- https://t.co/uAaSl8hOdh
The Five Orders or Ignorance
- https://t.co/VpQyNcvEpV
Other articles by Phillip G.Armour
- https://t.co/9BMLUDyReM
@jennsemperamare โIf nothing changes, nothing changes. If you keep doing what you're doing, you're going to keep getting what you're getting. You want change, make some.โ
โ Courtney C. Stevens, The Lies about Truth
@jennsemperamare A.k.a:
* "By changing nothing, nothing changes!" --Tony Robbins
* โIf all you ever do is all youโve ever done, then all youโll ever get is all youโve ever got.โ --Margaret Spellings
also ...
@scottwambler@Disc_Agile Yes! And also it should be: living, literate (w/locality of reference), and as close to executable as possible (while still being readable)!
@matthewpskelton@TeamTopologies Yikes! So it is showing us:
- a 'Stream-Maligned' team
- a 'Disabling' ["Crutch"] team
- a 'Complexity Subsistence' [ "Concealed Carry"] team
- a 'Pratfall' team
Ya gotta "name it to claim it!"
@markburgess_osl Great stuff! Have yoy strong them altogether into a single article? (You should)
In HW & System CM, stds prominently mention "form, fit & function" -- what do you think 'form" & 'fit' are for Sw/digital?
(Interface? intregation?)
@tottinge@tom_a_r_johnson@quii I dont see "real change" vs "bookkeeping" change when I see merge-commits!
What I see is very simple (and meaningful): change, change, merge, merge, merge, change, merge, change, change, merge.
[Which is the point, since theyre separate events from different operations!]