Rationalizing the Presentation Tier
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
Tracking change and innovation in the enterprise software development community
Posted by Eric Evans on Nov 06, 2007 10:00 AM
Efffective Design, DSLs in Practice, DDD, Cloud Computing and more tracks @ QCon SF Nov 19-21
Introducing Project Zero: Building RESTful services for your Web application
Memory Analysis Best Practices Within Eclipse
Scale your applications without punishing your database
RESTful todo list sample tutorial with Groovy & Project Zero
I do not see any control for pause/forward/play recorded presentation. It completed Eric's first part, but it is not playing the 2nd part of the talk. Do i need to wait for 30 minutes for the break between 2st part and 2nd part?
well, i found the controls by mouse over the video,
so i found the end of the talk, i guess that the 2nd part of talk is not posted yet. am I right?
this is a great talk i recommend for everyone. Very well put and clearly explained concepts
Yes, it seems to be based on true experience. I once used other names in this domain, like Trip, TripEvent(Stops), TripSections(Legs) etc, a bit abstract perhaps, but generic. Downside with "generic names" is that it doesn't tend to sound very much like the "domain language", which is important for communicating core concepts with the domain experts, upside with generic names is (for the designer) that the emerging model "invites" to discovering generic patterns and "meta solutions" (a kind of a "the trees don't obscure the forest effect" if undressing the names of domain specific implementations). This in turn increases "insights" in the problem domain. And yes, try to get as deep into the problem domain as possible by discussing many and all aspects with domain experts. Don't stop at the first bright idea. I like that. But, OTOH, do NOT assume that the domain experts _fully_ understand the principles involved!, instead DO assume that they know (the best) how to do the job the way they currently do it (which is not exactly the same...). What I am saying is that a thorough analysis in the pre-design stage is an unique occasion also for the domain experts (usually the end customer) to learn to even better understand the problem domain(s) at hand, and from that follows a unique opportunity to potentially *improve* the business concept(s). Well, that's my experience anyway. It would be really interesting to hear also the other half of the lecture, hopefully the second part will also be uploaded?
Hi Yale Yes you're right. the second part of the talk will be published soon:)
Hi, Can the video also be downloaded somewhere? My connection fails sometimes and the player wants to restart and I am not able to seek to the point where the player stopped the last time.
Unfortunately not, however we are working on a fix but it may not be around for another couple of months.
Hi Ivo , you should try OrbitDownloader. Its free and can download any types of video :)
A very good talk. Despite Evans' moments of awkwardness he gave a coherent and well expressed presentation with a thought-out example. As a practitioner the new and exciting bit was at the end: many models can work to our advantage. Often I will consider 'the context' of a system first, define the basics of 'it' and move on. Maybe, next time I will spare some thought for the many contexts and workout a framework for each of them. I can't wait to see how to make it work, in part two... how/where will it be advertised? Will there be a link from this presentation?
>> Despite Evans' moments of awkwardness Wow this really was an idiotic claim! What if Mr. Evans was only thinking very deep inbetween, trying to increase value by trying to avoid confusing you by introducing too much complexity too early? He's actually doing very good. He's allowing things to sink in. Would you know exactly why his very humble and pleasant performance sometimes makes a short brake for a moment of deeper reflexion? This is what designer's do. They stop and think where other ruch ahead and causes,um... "all sorts". Disregard this stupid comment. // Rolf Lampa, Sweden.
Great how different the interpretation of "soon" can be.
Part two is now online on InfoQ: http://www.infoq.com/presentations/strategic-design-evans
where can i download the slides...? please... Thank you so much...
Hepl Blog >>> evden eve nakliyat
Nice site. Thank you ankara taşımacılık ankara evden eve
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.
In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.
In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.
It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.
In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.
In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.
Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.
Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.
You are viewing a mobilized version of this site...
View original page here
20 comments
Reply