By bloid
via rdn-consulting.com
Published: Jul 26 2007 / 04:34
This is a story that I’m sure is being written over and over again by software designers like myself that need to develop relatively complex applications in a short amount of time. The only realistic way to accomplish this is to bite off major chunks of functionality by leveraging the work of others. Reinventing the wheel, especially wheels you know hardly anything about, can’t be justified. Because of that many of the architectural decisions you have to make revolve around figuring out how to get all of those ‘frameworks’ and libraries and GUI components to work together. But I digress…
-
Use Capped collection on MongoAppender for Log4Net
-
How (not) to design a Metrics API – Part 1: “Millions of Metrics”
-
Leap 3D Sensor - Too Good To Be True?
-
Solving tabbed browsing for Vaadin applications
-
Attribute based routing in ASP.NET Web API
-
Multilingual and multinational site annotations in Sitemaps
Add your comment
