Making work visible
by Dominica DeGrandis · first published 2017
7mentions
4recommended by
6HN commenters
2018–2026first – last mentioned
67% recommend33% neutral
xxxi, 205 pages : 23 cm
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
…any language) - Enterprise Integration Patterns (I work on an enterprise APIs team) - Designing Data-Intensive Applications - Camel in Action Good for lending out: - The Phoenix Project - Making Work Visible - Effective DevOps - The Pragmatic Programmer - REST in Practice
on “Ask HN: What books do you keep on your desk?” ↗If you liked this post, the book Making Work Visible is a great expansion on these topics. Making Work Visible: Exposing Time Theft to Optimize Work & Flow https://www.amazon.com/dp/B09L3B9YK1/ref=cm_sw_r_apan_AX66TB...
on “Finishing what you start makes teams more productive and predictable” ↗Some of my favorite books around managing software projects and technical leadership: * The Manager's Path - read the chapter on being a Tech Lead * Making Work Visible * Accelerate My website has more book reviews on this topic: https://www.briansnotes.io/audience/tech-lead/
on “Any good resources for learning Software Project Management?” ↗…cultures are, and that has to be adopted and tried at an organizational level. Coming from the infrastructure world I find a lot of the DevOps and SRE resources were useful here; Accelerate, Team Toplogies, Making Work Visible, etc... The remote aspect of it has logistical issues, but ultimately it's about information flow and figuring out how to develop trust between team-members and teams.
on “Ask HN: Who is doing “remote” well?” ↗(also if you want a longer overview a bunch of related concepts are talked about in Dominica DeGrandis’s book Making Work Visible, and the advice on managing by the critical path method comes from a makes-my-eyes-roll-a-little-but-still-pretty-solid business novel by Eli Goldratt called Critical Chain, which applies the reasoning…
on “Productivity and the Workweek (2000)” ↗This is also where automated code quality checks can shine. You can say something like, if it's more than 5 or 10 lines we expect a ticket ID, otherwise we don't. See DeGrandis’s “Making Work Visible,” the hazard of “link to a ticket if it exists” is that sometimes this causes us to treat tickets as an external process, but we absolutely want to surface tickets that track our cleanup of tech debt…
on “The Continuous Delivery Test” ↗Making Work visible by Domenica Degrandis. I have switch more into it team management role (have been 17 years individual contributor) and Im trying to find good books, any advice welcome
on “Ask HN: What are you reading?” ↗