Programming

Not my site, just sharing a link I saw on HN.

They kind of glossed over the real value, which is using it as a template to automate a step at a time:

"Each step of the procedure is now encapsulated in a function, which makes it possible to replace the text in any given step with code that performs the action automatically."

It breaks the work down into more manageable tasks. I probably wouldn't give it to users until it was done, but putting placeholder functions is a common strategy.

Yeah, I'm really wondering why they thought this was a good idea. My best guess is that they want to keep everything within one file, since it makes the script easier to deal with. But when automation actually starts being implemented, they want the functions for each task to be grouped (and I believe, Python doesn't support inline modules), so they ~~ab~~use classes for that...?
Well, and I guess, it allows them to have pseudo-constants within each task, which don't need to be explicitly passed around between functions.

But yeah, really not a fan of needing this much boilerplate to start out with. In my opinion, the activation energy required to use this pattern instead of slapping down documentation needs to be as minimal as possible, otherwise folks will slap down documentation instead.

That is what makes it Enterprise-grade!

It's probably to allow for added complexity as they expand on each task. Makes it simpler to import elsewhere too.