royosherove

11 ms·

61.
The Pipeline Driven Organization – Enabling True Continuous Delivery(infoq.com)
2 points by royosherove 7y ago|0 comments
62.
I'll be driving you insane (2012)(youtube.com)
1 points by royosherove 7y ago|0 comments
63.
Red Pipelines and Build Whisperers(pipelinedriven.org)
1 points by royosherove 7y ago|0 comments
64.
by royosherove 7y ago
It's really about day to day decisions being "pipeline driven" - allowing automated pipelines to make continuous tactical decisions that humans usually make in "traditional" processes. When to merge, is it secure?
65.
by royosherove 7y ago
I maintain a blog about tech leadership at 5whys.com (turned it into a book later on called "notes to a software team leader")
66.
“Pipeline Driven” vs. “We Have Jenkins Jobs”(pipelinedriven.org)
3 points by royosherove 7y ago|0 comments
67.
About Being Lonely as a Consultant(osherove.com)
10 points by royosherove 8y ago|0 comments
68.
by royosherove 8y ago
I see a lot of similarities between writing code and making music. I wrote about it here: https://osherove.com/blog?tag=codemusic
69.
by royosherove 8y ago
I came up with my own set of questions that hopefully show how a person can deal with human complexity at work (the bulk of our issues), rather than memorizing algorithms. Some people don't like it - but it works for me: https:/
70.
by royosherove 8y ago
For a team that has low code quality - here's how I like to start my code review process. not everyone will like it, but I find it effective at growing people's skills: https://www.5whys.com/articles/step-4-s
71.
Ephemeral Environments for DevOps: Why, What and How? (2017)(enterprisedevops.org)
40 points by royosherove 8y ago|14 comments
72.
The Bus Factor – Why your ‘best’ developer is your biggest problem (2010)(5whys.com)
2 points by royosherove 8y ago|0 comments
73.
The Four Most Common Root Causes That Slow Down Enterprise Continuous Delivery(enterprisedevops.org)
1 points by royosherove 8y ago|0 comments
74.
Delivery Pipelines and Discovery Pipelines(enterprisedevops.org)
2 points by royosherove 8y ago|0 comments
75.
When I Want to Give Up(5whys.com)
1 points by royosherove 8y ago|0 comments
76.
TDD and Unit Testing- Why you should care and how to make it happen(youtube.com)
1 points by royosherove 8y ago|0 comments
77.
Red Pipelines and Build Whisperers(enterprisedevops.org)
3 points by royosherove 8y ago|0 comments
78.
by royosherove 8y ago
Yeah I can see that. Maybe the term "PR" can lead to misuse with things that would be better off integrated. I wonder, Perhaps a better name that does not imply that use case might make better sense.
79.
by royosherove 8y ago
I can see how that makes sense. Thanks for explaining!
80.
by royosherove 8y ago
I could be wrong, but I feel this actually enables the wrong kind of behavior we should expect from developers. We want fast, continuously integrated code that is merged early. Usually that means using feature toggles so that we can see com
81.
A Pipeline Friendly Layered Testing Strategy and Recipe for DEV and QA(enterprisedevops.org)
6 points by royosherove 8y ago|0 comments
82.
by royosherove 8y ago
Hold public audits by a trusted 3rd party to show you are not keeping any data - on a repeating basis (6 months?)
83.
TDD Kata 1 – String Calculator(docs.google.com)
1 points by royosherove 8y ago|0 comments
84.
Jerry Weinberg’s Last Worry(satisfice.com)
2 points by royosherove 8y ago|0 comments
85.
Vim Hates You(vimhatesyou.com)
36 points by royosherove 9y ago|2 comments
86.
Vim Hates You(vimhatesyou.com)
3 points by royosherove 9y ago|0 comments
87.
Ephemeral Environments for DevOps: Why, What and How?(enterprisedevops.org)
1 points by royosherove 10y ago|0 comments
88.
Continuous Delivery Values (2017)(enterprisedevops.org)
2 points by royosherove 10y ago|0 comments
89.
The first rule of continuous delivery toolchains(enterprisedevops.org)
1 points by royosherove 10y ago|0 comments
90.
Four root causes that slow down enterprise continuous delivery(enterprisedevops.org)
2 points by royosherove 10y ago|0 comments

More ›