Grid reports of the
Application Developer Days 2010 conference! There will still be some minor moves, there are still unoccupied slots - for them we still select the most interesting reports, but the common core has already been fixed:
There has not been such a busy
programmer two-day conference yet. You might think that the reports are chosen haphazardly, so different technologies they cover. Each of us can find there two or three familiar topics. But this is the main idea of the ADD 2010 conference - to get out of the routine and look around.
We are programmers, and our job is to solve assigned tasks using languages and technologies invented by someone and then chosen by someone to solve these very tasks. Are these the best languages and technologies? Is not a fact. But it’s hardly possible for anyone to search the Internet and arrange a good check.
')
“Back to work! This software won't code itself, you know! ”©In any case, this check takes almost infinite time.
At the conference, you will see and hear people (real experts!) Who solve other problems every day using other languages and other technologies. They will tell you in detail about their experience, after which you can catch them on the sidelines and talk for at least an hour. It is very possible that their stories will guide you to new thoughts, and you will figure out how to solve your problems faster and easier.
Separately, I would like to mention
Andrei Bibichev ’s
four-hour master class in designing application architecture using Domain-Driven Design methodology. Andrew brought together his long-term practice of developing complex systems and rich experience in design training. The result was an atomic thing, useful to any programmer developing application systems. At the same time, Andrei speaks perfectly, it is just pleasant to listen to him.
Friends, there are two weeks left before the conference. This is quite enough to win laziness and go, but especially there is no time to think. Register , we are waiting for you!PS We are often asked: "Why the woodpecker?". There are many interpretations, I am ready to personally reveal the history of the issue at the conference. :) But understanding came after talking with various masters of the “Indian style” (I program from here to dinner; the sooner we finish digging here, the faster we will go digging elsewhere). A bit angry, but true:
The programmer is not a woodpecker, knocking on the keyboard. Woodpeckers exist, and we can not change it. We can only not be woodpeckers. So we will not!
Update: Friends, this program is not the final one yet. You give feedback, and we move the reports in the network, so that everyone is comfortable. So the current program should always look at the site.