Having experience with jQuery I thought this would be a good idea to see if George used the same practices as I do, which he did… which means either we’re both doing it wrong or we’re both doing things correctly… and I’m sticking to the latter
Not having heard of George I had no idea what to expect.
George is a defiantly a character, in fact on the DD9 speaker page they could have stopped after just three words
George is nuts
He has a great presentational style and is able to deliver comments about IE with impeccable timing
After satisfying people who need an agenda what has the content?
George
talked about closures and event delegation
showed demos of using the live method when creating new elements
demonstrated the modern way (at the time of writing) of creating Hijax links using the data-remote attribute
showed a workaround for cross domain AJAX calls using the callback? in the request and JSONP
The last thing I’ll say about this talk was how well George managed to still run demos even though the demo gods did their best to ruin his presentation and screw up his solution.
For me Ian Cooper is an exceptionally talented developer who has the the ability to give you so many good ideas and convey them in a simple way which is so easy to understand.
He began his talk about CQRS (Command and Query Responsibility Segregation) by discussing how CRUD operations were now a secondary task if a user wanted to change their address within a task based system.
In the new way of thinking companies should be capturing the intent of a change (e.g. moving house) and take advantage of any opportunities such as offering them a range of services e.g. phone, broadband, etc.
Ian also used the analogy of ordering a take away from a restaurant and how he would communicate using a numbers for a dish when placing an order.
This was a different shift in thinking when it comes to grid based editors where all the data was retrieved from the database and the sent back again when a change was made.
So in the case of a take away it would like them sending all the dishes to your house for you to make a selection.
Next Ian went on to talk about side effects in code e.g.
public int MyValue
{
return MyValue++;
}
and how you could reduce the amount of time it takes to think about code by using CQRS to separating reading and writing tasks.
He used a demo to show the benefits of not using your entities as data structures. In the next couple of weeks I’ll write a similar demo to show the benefits of developing your code to take advantage of this.
Before I came to this talk I was in two minds about whether I got CQRS or not. Turns out CQRS itself is a simple concept the problem is developers confuse it with event sourcing.
