Thats a very handy link, thanks.

The whole 'sociotechnical' part is gaping black hole for most new devs I meet, because it's not taught, and I don't know that schools know how to teach it.

Anyone have any internal processes (or resources) for helping newbs understand that side of the job?

check "recommended readings" on the right:

https://www.svilendobrev.com/rabota/

starting from Organisational patterns, down. Skip anything there about design/ architecture/ math.

But: have in mind Conway's law - software-produced <=> organisation's-culture. So you can't dismiss entirely either of the two extremes of the socio-techical (human-machine) systems.

IMO, Winnie the Pooh has much more sociotechnical hints than CS university course.

Thank you very much, I'll check that out

also check this about building/growing S3 at Amazon - quite some socio-technical points:

https://www.allthingsdistributed.com/2023/07/building-and-op...