Eventually Consistent HTTP with Statebox and Riak
Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agile Maturity Model Applied to Building and Releasing Software
At 24:30 the presentation makes me remember a Guilherme Silveira's presentation, from Caelum, "Quando o scrum começcou a atrapalhar"
www.infoq.com/br/presentations/quando-scrum-pas...
[],
AC
Stop trying to educate your managers, just get rid of them.
+1 Sweet!
Wow. Many truths spoken here. This talk is pivotal and could well be the antidote to what many developers experience in toxic organizations: Agile-off-the-rails
Two nit-picky criticisms:
1. Don't use the word "lean" or "leaner". Lean is for machines, not people.
2. Never refer to people as "resources" (e.g., Resource Rumble).
Hmm... And after you got rid of all of the managers, will the developers draw up the contracts, get the customers, take care of payment and other administration stuff?
That's like the branches cutting off the trees.
No, there's a reason that managers are needed (as much as I hate to admit that), and they do need to learn how not to get in the way of progress...
Assaf,
Yes, many organizations need sales and administration. But unless managers are carrying water for the developers or clearing impediments, I haven't experienced demonstrable value w/ managers.
Assaf,
As pointed out in www.bcs.org/upload/pdf/complexity.pdf, p.14 (13th one), software is "invisible", at least for people that don't practice it, as are mathematical spaces for non-mathematicians.
The main reason I see for managers being possibly harmful, is that they often don't practice development enough, if at all, and have therefore decisional responsibilities in a very complex and subtle field of which they don't understand the constraints and the possibilities.
As for drawing up contracts, getting customers, etc., of course there is room for specialized people here, but they need to work in close relationship with software guys.
Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.
Erik Onnen attempts to demonstrate that Java is still the best programming language for the JVM if simplified idioms are used along with proper tooling.
Approaches to integrating data are changing with emergence of cloud computing.
Michele Ide-Smith presents the lessons learned in the process of introducing UX principles and techniques into a large organization through a series of small steps.
Dave Farley and Martin Thompson discuss solutions for doing low-latency high throughput transactions based on the Disruptor concurrency pattern.
Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project.
Dale Schumacher presents several patterns of actor interaction that can be used in collaborative programs written in any language.
Rúnar Bjarnason discusses Scalaz, a Scala library of pure data structures, type classes, highly generalized functions, and concurrency abstractions to perform functional programming in Scala.
8 comments
Watch Thread Reply