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?
Anatomy of a Deployment Pipeline – free chapter from the book "Continuous Delivery"
A Guide to Branching and Merging Patterns
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
and Mr. Lee has garnered wisdom that belies his youth.
I didn't know what to expect, but the talk was a load of fun to watch.
A statement like "a software engineer makes great applications not because he follows good rules but because he has a better way of looking at the world and he learns from experience" scares me.
To what criteria the application is great if there are no rules that set the objectives?
If someone starts with no experience, how many chances s/he has to get this experience if I would not buy produced application (because it was made w/o rules and experience)?
I don't think he was saying no rules, I think he was more saying that you can't just follow rules and get good software as a result. It's like art - "An artist makes great art not because he follows good rules, but because he has a better way of looking at the world and he learns from experience." I think it still holds up. Sort of like saying - knowing how to draw is not enough.
And I will say that it depends on what part of the spectrum you are working. User interface / user experience, are much more design problems than engineering problems. As such, they require more knowledge of people - soft skills, as opposed to hard. And its not just the visual design. There are plenty of rules for that too - color, whitespace, etc. Someone could easily do a presentation on that - there are plenty of books as well, but what Mike was getting at is more about the values that don't boil down to rules. Heck, each of the things that Mike pointed out COULD be made into rules, but that would be seeing the forest for the trees.
I love it. Very accessible and not necessarily specific to software.
I have always subscribed to the principle that by noticing what sucks about something you can learn how to improve it. Mike Lee really hits the nail on the head. He is a very entertaining and engaging speaker. Well done!
One of the most anti-lean comments I've seen. Which is kinda surprising to see on this week, where Eric Ries hosted Startups Lesson Learned Conference advocating MVPs for maximize learning, and overcoming the "My baby is ugly" syndrome.
Excellent presentation!
Great presentation. Very useful to all developers.
If only this site was not in Flash so I could watch it on my iPad!!!
If only this site was not in Flash so I could watch it on my iPad!!!
If only iPad supported Flash...
I was struck by how coincidental it is that the slides do not display properly while watching the presentation and how the frustration Mike Lee was describing matched my own experience of not being able to see the slides.
I don't know what changed with the presentation viewer but its broken now.
Saw 3/4 of video in full screen before realizing that slides were apearing below.
Now that sucks! :)
But a very entertaining and motivating message, nevertheless.
...but more importantly, am I the only person who wants a Harry Potter Sonic Obama backpack?
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.
13 comments
Watch Thread Reply