danielbryantuk

11 ms·

61.
The Cloud Foundry Foundation Certification Program – Pivotal P.O.V(blog.pivotal.io)
2 points by danielbryantuk 11y ago|0 comments
62.
End-To-End Testing Considered Harmful: A Q&A with Steve Smith(infoq.com)
2 points by danielbryantuk 11y ago|0 comments
63.
Container Manifests, Docker Labels, and the Implications on Security(infoq.com)
3 points by danielbryantuk 11y ago|0 comments
64.
Docker Monitoring: Best Practices and a Comparison of CAdvisor and Prometheus(infoq.com)
1 points by danielbryantuk 11y ago|0 comments
65.
Implementing an Open Source Private Docker-Based PaaS: A Q&A with Rancher Labs(infoq.com)
3 points by danielbryantuk 11y ago|0 comments
66.
by danielbryantuk 11y ago
Thanks for the response. Yes, the article was primarily a summary, but it included content not available in the slides
67.
Beyond the Technology of Microservices: Organisational, Architectural and Ops(opencredo.com)
1 points by danielbryantuk 11y ago|0 comments
68.
by danielbryantuk 11y ago
Can I ask why you changed the link please? The original linked document provided commentary on the slideshare slides (and also linked to them)?
69.
Stop Being Lazy and Test Your Software(slideshare.net)
2 points by danielbryantuk 11y ago|4 comments
70.
by danielbryantuk 11y ago
In my experience working as a consultant across multiple organisations, not enough people have been doing this. As for a putting a name on it - a name can help spread the idea (ubiquitous language and all that), but it can lead to abuse a
71.
by danielbryantuk 11y ago
Great comments Daniel, and I think you've touched on one of the key points that we're seeing with the rise of mob programming and lean practices etc "it's really completely re-structuring what we think about when we thin
72.
by danielbryantuk 11y ago
Wow! I couldn't have said it better myself. Having worked across a variety of codebases and teams over the last 10+ years, it has become obvious to me that delivering software is an inherently social activity (at least the delivery of
73.
by danielbryantuk 11y ago
+1 to the comment here. I see lots of discussions after code has been cut ('why this design?', 'why this library?', 'did you consider this?'), which would have been much more valuable to have as the code is bei
74.
by danielbryantuk 11y ago
I think this reply thread is confusing the specific, i.e. the technique of 'mobbing', with the general, i.e. the (mis-management) approach to fixing issues with 'all hands to the pumps'. The only thing the Unruly team is
75.
The Benefits of 'Mob Programming'(infoq.com)
29 points by danielbryantuk 11y ago|43 comments
76.
JavaOne: Thinking Fast and Slow with Software Development(opencredo.com)
2 points by danielbryantuk 11y ago|0 comments
77.
Organisational, Architectural and Operational Challenges of Microservices(opencredo.com)
1 points by danielbryantuk 11y ago|0 comments
78.
Working Locally with Microservices (Patterns and Tooling)(opencredo.com)
3 points by danielbryantuk 11y ago|0 comments
79.
Thinking Fast and Slow with Software Development at the Software Circus(opencredo.com)
1 points by danielbryantuk 11y ago|0 comments
80.
Key Takeaways from the 'Agile on the Beach' Conference: Day One(infoq.com)
2 points by danielbryantuk 11y ago|0 comments
81.
Building Microservices with Go and ‘Go Kit’(infoq.com)
2 points by danielbryantuk 11y ago|0 comments
82.
Microservice Platforms: Some Assembly [Still] Required. Part One(opencredo.com)
1 points by danielbryantuk 11y ago|0 comments
83.
by danielbryantuk 11y ago
Looks awesome (and great graphics on the site)!
84.
Monitoring Microservices and Containers: A Challenge by Adrian Cockcroft(infoq.com)
2 points by danielbryantuk 11y ago|0 comments
85.
Scaling the Stack Overflow Monolithic App by Obsessing Over Performance(infoq.com)
2 points by danielbryantuk 11y ago|0 comments