It site is an amazing and hilarious encapsulation of pretty much every conclusion I've come to after programming professionally for 20+ years (except maybe generics)
I remember, early in my career, being excitedly shown the "Agile Manifesto" by a bearded older dev.
I recently caught myself excitedly showing grugbrain to a younger dev, quoting the microservices section - and realized that I've come full circle, and now I'm the old bearded dev passing on some piece of thing that I found inspirational / exciting.
when mysterious packages (new sandals, new animal skins, etc.) keep arriving at cave door for mrs. grug, grug not save very many shiny rock.
also, wolves and sabretooth tigers get hungry, need grooming, need vet, etc. picky about food too, want expensive organic stuff. sometimes mrs. grug buy animal skins for wolves even though they have perfectly fine pelts of their own. and don't get grug started on lil' gruglets (which this grug not have).
then no pile of shiny rock for rainy day, when shiny rock stop coming and cave mortgage is due.
shiny rock very important. get as much shiny rock as can without compromising values. happy mrs. grug = happy grug.
Many people misunderstand this. Just saying 'no' and being firm won't make you successful, it's not a very useful. Saying 'no' while convincing others that 'no' is actually the best strategy is a great skill.
I have a feeling that the ability to say “no” may be one of the key abilities that good human developers have over coding AIs. Knowing how to figure out the actual business need and realistic technical solutions, as opposed to just saying “yes” to the initial request, without really understanding feasibility or the real requirements.
