signal

- Based on a random survey of software engineers (who somehow had visibility to project inception & outcome)

- Doesn't define project

- Success was defined by not violating the iron triangle (so nobody knew what they were saying OR they're working on trivial "projects")

- If you read reviews for the book it's totally AI generated nonsense

- Based on a random survey of software engineers (who somehow had visibility to project inception & outcome)

- Doesn't define project

- Success was defined by not violating the iron triangle (so nobody knew what they were saying OR they're working on trivial "projects")

You don’t think DIY or ‘scrape by without a solution’ represents a significant dependency?

Sunk cost (amongst other factors) is a gravitational force on orgs that try to get things done without the right tool for the job.

What’s an example of a thriving tech company with home grown UX tooling?

How are you reconciling your take against the actual content of the article?

Hi folks! This is a writeup I published earlier in the year because I hear of a lot of people curious about the '4 Key Metrics of DevOps', what to measure, and how to get started making improvements to flow and performance.

TL;DR: Starting from a clear outcome is more important than chasing someone else's metrics, and mapping with your team can help you effectively translate your goals into action.

I'd love to hear thoughts, experience, and feedback!

Did I miss the target use case and user?

I'm a big fan of decision frameworks but without those two clarifications it's hard to give feedback. To make this practically valuable it would be great to have logging and an escape path for criteria that doesn't apply or when information isn't available. If I get to question 5/6 and I don't know the answer, can I get a valuable outcome? It would be ideal to capture those cases with logging so the tree can be improved.

This is a great idea and start though. I love how minimal it is. Once I use it, I immediately want it just built into Jira or wherever I'm making important/repeated decisions.

It would be interesting to see what you're saving on each tool and why they beat free alternatives. I think the only one that doesn't have a compelling free option is getresponse but there's sendfox for email that does the job well.

I'm in this camp - I want to share content with Pocket (and increasingly Notion for personal use, then outward to Twitter/LinkedIn/Automation and all of that is already in my browser.

Is that factoring in cost of living? There's an enormous difference between Toronto and SV there.

So, DevOps as you (mis)understood it is dead. Long live DevOps as it was meant to be understood.

This is super interesting! Are the product managers and designers a shared resource?

That's close, but still a problem. If you put change responsibility formally on the shoulders of a team or individual you're throwing them under the bus. It needs to be approached as a cross-functional team initiative (which is reproduced to scale out). A DevOps team might work if they're in a leadership position, but how does it work on the ground?

DevOps doesn't mean people doing multiple jobs. You can collaborate with separated roles and be productive. Furthermore you can build abstraction to simply remove manual, unrecorded interaction with systems to satisfy auditing and regulation.