Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.
Your profile
Tag cloud
.net android asp.net asp.net mvc azure backup bigdata book c# community continuous delivery database denali functions gotcha how to howto indexing java linq mongodb nancy nhibernate nosql performance powershell ruby security silverlight sql sql advent 2012 sql friday sql server sql server 2000 sql server 2005 sql server 2008 sql server 2008 r2 sql server 2012 sql server denali ssis ssms ssrs structuremap t-sql tip training unit testing vb.net visual studio 2010 windows 7
Authors
- SQLDenis (577)

- Christiaan Baes (chrissie1) (527)

- Ted Krueger (onpnt) (332)

- Jes Schultz Borland (grrlgeek) (139)

- Eli Weinstock-Herman (tarwn) (116)

- Alex Ullrich (51)

- George Mastros (gmmastros) (46)

- Naomi Nosonovsky (27)

- Axel Achten (axel8s) (23)

- David Forck (thirster42) (22)

- Koen Verbeeck (20)

- Kevin Conan (18)

- chopstik (18)

- Rob Earl (14)

- thatrickguy (12)

- More...
Main Categories
Search
Google Ads
Tags: architecture
From Eli's Shelves: Books for IT Architecture
Most companies reach a point in their lives when they realize that they aren't entirely sure what IT resources they have, how they're deployed, what direction they're headed, or whether they're ready for the next big shift from the business. Some companies visit this point multiple times, either in response to shifts in the company or business landscape or as a result of letting the environment devolve back into it's primordial beginnings.
Model-View-Presenter: Looking at Passive View
Model-View-Presenter is an architecture pattern that defines a structure for behavior and logic at the UI level. M-V-P separates the logic of the presentation, such as interacting with back-end services and the business layer, from the mechanics of disp…
IT: Beyond the 'Right Now' Problem
In an IT department there is a tendency to classify operations as being reactive or proactive and, often, pressure to have more of the latter and less of the former. Pressure, that is, until a PC breaks down, a network connection drops, a data record goes missing, or any of a dozen other issues which will ultimately receive more attention than disaster recovery, employee development, business analysis, strategic planning and the rest of a long list of proactive tasks. Immediate, defined problems are far easier to focus on than tenuous concepts of proactive prevention.
Level of Pain...
Patterns And Practices Application Architecture Guide 2.0, Something Everyone Should Read
I was listening to show number 426 on dotnetrocks: Rob Boucher on Application Architecture Guidance! They mentioned the Patterns And Practices Application Architecture Guide 2.0, this guide is available for free on codeplex. Although it is a Microsof…
5 Books Every Developer Should Read
Which books should you read/buy when you are a programmer? I have listed 5 books that have helped me a lot. The books that I have chosen are not specific to any language although some of the books have examples in one language only. Design Patterns has examples in smalltalk and C++ but since the code is not very complicated you should have no problem converting it to your language of choice. I have included links to sample chapters for the books where I could find them. For some of the books I have also provided links to the author’s site; some of them have additional material so that...
Danger in Design: Why bother with Architecture ?
Creativity is a wonderful thing. It’s also something different for each of us, which is why sometimes our perspectives on the world can produce conflicting ideas on what is the right way and the wrong way to do things. This is a very common facet of the IT world, in particular making computer software, solutions and services.
We don’t need architects! …Do we ?
It’s important for us to remember that we develop software to “do something” that we want it to do. In which case we need to continually review the success of that software or...

LTD Social Sitings
Note: Watch for social icons on posts by your favorite authors to follow their postings on these and other social sites.