Paul Shepheard @hamletarable

Husband, dad, technophile, guitarist - tries hard to keep them in that order, doesn’t always succeed. He / him. Views very much my own. hamletarable.com Joined October 2010

Tweets

446
Followers

171
Following

446
Likes

1K

Paul Shepheard @hamletarable

3 years ago

@LordBaldrick @VirginMoney Dev Tools -> View Source 🤷‍♂️

0 0 0 154 0

View Details

Paul Shepheard @hamletarable

5 years ago

@LordBaldrick Tools tend to be useful….just sayin’ 🙂

1 0 0 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

I mean, it's not wrong.....

0 0 1 0 0

View Details

@eikonne I think this is true of most things. Knowing how things should be is 5% of the effort…driving the change is where the value is…but no always the limelight. Was it Patty McCord who said “problem finders are cheap”? 🙂

0 0 0 0 0

View Details

Matt Wynne ✊🏿 cosocial.ca/@mattwynne @mattwynne

5 years ago

Are you working in Go and into BDD? We could use your help: github.com/cucumber/godog…

1 9 7 0 1

View Details

FindingAda @FindingAda

5 years ago

We want to provide our best-in-class mentoring program free to 50 working class or first gen women in science in the UK, but we need your help to do it. Our structured online program, with careers & skills advice, hands-on support, works. Donate: gofund.me/913dcfbb

0 4 1 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

@gojkoadzic But the beauty of my thingy abstraction framework is that you don’t need to know how many things are on top of things....

0 0 1 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

@tastapod @johncutlefish @marick @GabbyPatrick will see you and raise you Crazy 8’s 😁

0 0 0 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

@mattwynne Happy to chat any time, let me know if you want to go into more depth / detail. Hope you’re keeping well - looking forward to meeting up again when we’re out the other side of all this!

1 0 1 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

@mattwynne Specifically, it allowed us to remove the traditional UAT sign off late in the cycle, replaced with sign-off of the behaviours up front. When they are coded and go green, we can push. There are other considerations of course - e.g usability - but these were dealt with mid sprint

1 0 2 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

@khangharoth Strong agree! “But I just like designing and building cars, I don’t have much interest in how they perform over time once they roll off the conveyor belt..” - that kind of thinking isn’t much good to car buyers who need to get places!

0 0 1 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

@tottinge @bguthrie @tastapod @ckeithray @tastapod has been nudging me to write up something more comprehensive than a few tweets for a while! I've not prioritised this yet, but there's clearly some interest in the topic. I write roughly one blog post a year, maybe 2021 is when this one gets written up 😀

1 0 2 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

@bguthrie @tastapod @tottinge @ckeithray However, in that regulated environment, we were able to deploy multiple times a day with no user down time, and it was because we were provably compliant that we were able to do that. It took effort to get there for sure but in the end, a lot more was delivered as a result

1 2 3 0 0

View Details

Paul Shepheard @hamletarable

5 years ago

@bguthrie @tastapod @tottinge @ckeithray As ever, it's all about context. This was in a regulated environment. In others, going fast and only adding the controls you really need after a few crashes may be a better way. A/B testing and great o11y can help limit the blast radius of that approach