Looking for best practices, opinionated talks and some fun. Making some new acquaintances, meeting old friends.
I'd rather reduce product presentations to a bare minimum.
This is not about dressing in camouflage and wearing a helmet when coding, but about applying martial arts concepts to software development.
Especially (but not only) when dealing with a mission critical environment, it is important to use a development strategy where failure is not an option. You can achieve this by employing concepts which have been around for ages to teach people how to survive a fight.
But remember: Even with great awareness for dangerous situations, it still takes training to either avoid them or to come up with a plan to succeed. When developing software, cultivate good habits by adhering to these concepts.
Let's walk through the different stages of a development cycle and reevalute our strategies, covering everything from team building, leadership, modeling & design, coding iterations, tests and deployment.
Naturally you could do Combat Ready Development while working with a couple of different programming languages. Ruby, however, is perfectly suited. During the course of this talk there will be real life code examples, as well as an introduction to a couple of abstract strategies.
So I just realized that I got another appointment scheduled for the Euruko weekend, which I can't move. Sadly, that means I have to withdraw my proposal. :-(
Sorry, guys. But thanks again for the feedback.
Thanks for your feedback, guys. It's nice to see that my proposal at least got your curiosity. Even though it's not quite easy to give a lot of detailed examples without spoiling too much of the talk's contents or giving away personal information (and thus killing the whole anonymity thing), I'm gonna try and shed some light on the matter.
First off, rest assured that this talk will contain some Ruby code. Of course there are some interdisciplinary topics in Combat Ready Development, but I'm also gonna talk about testing, design patterns and premature optimization.
Take optimization for an example: When training a martial art you'd never try to improve your performance before getting the movement right. First you refine your technique, then you try to do it with more power. The same should be true for your code. Once you're sure what data a view should display you start to tweak your queries using clever scoping, adding indices, counter caches, handwritten SQL, etc.
I could elaborate even more, but I hope I already got enough of your attention for you to vote for me. ;-)
I'm happy to answer more questions for you though. See you in Athens.
To be clear...I really like this proposal - I imagine talking about how real ninjas can help you be a better developer :P.
Ruby conferences have a tradition of including at least one non-Ruby or even non-programming talk in the program. And I'm behind Peter in that a breadth of subjects makes a conference like Euruko all the more interesting.
Outside views are all the more valuable if you can find the connecting thread that allows you to apply them in your field...in this case Ruby which is the connection I've been looking for to make it even more attractive ;).
I disagree that talks should be about Ruby only. Yeah, there are obviously some hard limits (like giving a pure Python talk would be ridiculous :-) but during the few EuRuKos I have attended, I personally enjoyed interdisciplinary talks the most (a bit of Ruby, a bit of comparison with X (be it a language, concept, philosophy etc), a bit of applying it in real life (and not only involving the dev layer, but up all the way to sales etc. etc). I have also heard about node.js for the first time from the original author, who was (or so we tought) a mostly Ruby hacker at that time, at an EuRuKo (well that was a lot of years ago).
Now I understand that some of use are pure hackers who'd love to know about Ruby 2.0's hidden features, or that chef has a setting which makes it easy to set up a DB sharding in the cloud in 5 min etc. and don't care about any non-dev aspect, and that's fine (and I have quite a bit of that in myself too) - but I personally think these conferences are better for their breadth/width (overview, broad picture, trends etc.) rather than depth (going into a specific framework like cucumber, puppet, rails, or whatever in great detail).
tl;dr: bring on the non-pure Ruby talks too! They will be sifted out anyway if the majority of the crowd doesn't like them. And don't be afraid, whatever you do, most of the talks will be pure Ruby anyways. Balance is good.
That said... I could also use some details :)
I would be totally interested though, in contrast to Vassillis. Still it would be very useful to give some examples of what you exactly mean.
The Ruby community is a great one for abstractions and best practices and it's members are always open minded. I personally love abstracting away the "implementation details" and find the subject fascinating...but Euruko is a Ruby conference and I don't get a Ruby connection from the abstract.
Can you elaborate without giving too many spoilers?