Adrian Cockcroft
5 statements across 1 episodes · 1 bullish · 3 bearish · 1 people on the record · first statement Jan 2, 2019 by Adrian Cockcroft · said 2 times in 2 episodes since 2019 · across every show →
On the record as a speaker too: Adrian Cockcroft's record, appearances and statements → this page counts the times other people say the name.
Mentions by year
brought up most by Sonal Chokshi (2)
tap a year for its mentions
2019 2 mentions in 2 episodes 1 per episode
Everything said about Adrian Cockcroft, oldest first
Jan 2, 2019 negative
Cockcroft: Big banks maintain an illusion of cloud security compliance
“And a lot of what I'm seeing is a big banks and people like that. They have their existing policy frameworks and rules, and they're trying to apply it in the new world. And it looks the same. So they're happy because they're compliant, but they don't actually …”
Jan 2, 2019 positive
Cockcroft: Putting developers on call incentivizes reliable code and safer releases
“If you put a developer on call, they write really reliable code and they don't release code on Friday afternoons and because they want a quiet weekend and, you know, they learn a bunch of practices about having a, what it's like to be on call and how not to br…”
Jan 2, 2019
Cockcroft: Microservices require shifting enterprises from project-based to product-based teams
“What you see with traditional enterprise siloed organizations is they're actually having to do a reorgan set up teams that own, that are responsible for services, and that's, it's somewhat unnatural for the way they're currently set up, but I'm seeing an incre…”
Jan 2, 2019 negative
Cockcroft: Quarterly software releases pose an existential threat to legacy companies
“There's an existential threat here that if you're doing quarterly releases and your competitors doing daily releases and continuous delivery, You're going to fall so far behind in the user experience that you're just going to suffer, right?”
Jan 2, 2019 negative
Cockcroft: Microservices sharing a single database create fragile distributed monoliths
“And it turns out if you don't break apart your database backend, and you just create lots of services to talk to it, you've actually created what's called a distributed monolith, which has all the same fragility of the monolith, and you can't update things ind…”