HackerTrans
TopNewTrendsCommentsPastAskShowJobs

signal

no profile record

Submissions

The 4x4 Method of DevOps Traction

vzbl.io
3 points·by signal·5 years ago·1 comments

comments

signal
·2 years ago·discuss
- 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
signal
·2 years ago·discuss
- 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")
signal
·4 years ago·discuss
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?
signal
·4 years ago·discuss
How are you reconciling your take against the actual content of the article?
signal
·5 years ago·discuss
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!