Explaining to your boss (or your wife:)) why tier based architecture doesn't scale. Two weeks ago I had the pleasure of presenting at the NY JavaSIG. The event was hosted by an old friend, Frank Greco, who has been doing a really great work keeping the NY Java community up to date with the latest and greatest for quite some time (Great work Frank !). Even though it was one of those freezing NY evenings, the room was packed with around 300 people. In this presentation, I used an analogy that I refer to in many of my recent talks to explain the fundamental limitations of the tier-based approach.
I thought it is worth documenting this analogy, for those of you who are looking for a simple argument to convince their managers to open their mind to alternative approaches. One of the things I experienced with this analogy is that everyone gets it (my wife included J) It goes like this: Imagine a Coca-Cola production line that consist of three factory lines: one producing the bottles, one filling them and the third shipping them. Coca-Cola Factory - "Tier Based" Final words: Web Designers vs. Web Developers (Infographic) By Wix Let’s be honest. Being a web developer or a web designer doesn’t exactly give you an edge with the pretty girls (or guys) at your local pickup bar.
If you were a part-time firefighter or investment banker, maybe. Nevertheless, the feud continues between web designers and web developers over which profession is the true calling. Like the yin and yang, these two are in constant battle to prove their dominance over the other, even when they work closely together. Here is an infographic of the differences between web designers and web developers. Click to enlarge. MVVM Light Toolkit. Developer Review - Four ASP.NET MVC View Engines - Coding4Fun - Site Home - MSDN Blogs. In this Developer Review, we evaluate four view engines available for use with ASP.NET MVC. First, we discuss the role a view engine plays in a website built with ASP.NET MVC, then we provide details about the four view engines in order to help you decide which one suits your needs.
When we refer to a view engine in ASP.NET MVC, we are talking about three pieces of functionality: · A template locator/provider (implementation of IViewEngine) · A template that can render itself (implementation of IView) · A template engine that can parse and compile the view file syntax into executable code Combining these three pieces, a view engine provides your controllers with the ability to translate views into Html. Though the view engine that ships with ASP.NET MVC has all the functionality you need to create views for just about any website project, it is also easily replaced. As with choosing a programming language in .Net, there are many reasons why you may choose one view engine over another: Loops 1. Tomas Petricek - F# blog : ASP.NET and F# - Creating MVC web applications in F# FusionForge: ACUBE: Information sur un projet.
Free Rational Downloads, Tutorials and Articles.