cmdln,
@cmdln@thecommandline.social avatar

I am reading "Shape Up" in the sunshine out on our deck.

One editorial choice I noticed and like, preferring simple words and clear explanation over jargon. The author could have used the term, opportunity cost, but didn't. They pithily described it instead, in about six words.

I think that choice for plain language is making the book faster to read and easier to internalize.

cmdln,
@cmdln@thecommandline.social avatar

"Try to keep the clay wet." This book is literally speaking my language. I regularly use the metaphor of the nonsnse of trying to change a clay pot after it has been fired. That and leaving dross on the die, from lean manufacturing/TQM, that is only fix as much of the design as needed at each step so each following step still has some freedom to adjust and adapt.

cmdln,
@cmdln@thecommandline.social avatar

I like that the first step in shaping described in "Shape Up" is setting boundaries. I think it helps reinforce that the process is always trying to navigate many, many constraints.

So many projects I've been on start with the software version of assuming a perfectly spherical cow of uniform density on a featureless, frictionless plain. Then struggle to squeeze that into any practical way of working after.

No wonder why most software projects eventually fail.

cmdln,
@cmdln@thecommandline.social avatar

I may get a small "fixed time, variable scope" tattoo. I've felt this idea as a guiding principle more and more strongly over the years. I am glad to finally see a tech book explain it so clearly and even better reveal why it can be a better way to approach scoping effort of pieces of a project.

The inversion "appetite" represents is novel to me but tracks. As opposed to starting with a usually unconstrained design and struggling to produce a useful estimate for it.

cmdln,
@cmdln@thecommandline.social avatar

Another stellar thought from "Shape Up": 'Beware the simple question: "Is this possible?" In software, everything is possible but nothing is free.'

The stakeholders I've worked with who don't get this are the most dangerous. They are the ones least likely to actually heed or even trust developers.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • DreamBathrooms
  • ngwrru68w68
  • modclub
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • InstantRegret
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • mdbf
  • GTA5RPClips
  • megavids
  • tacticalgear
  • normalnudes
  • tester
  • osvaldo12
  • everett
  • cubers
  • ethstaker
  • anitta
  • Leos
  • cisconetworking
  • provamag3
  • JUstTest
  • lostlight
  • All magazines