Code Voyeur
RSS
Data Access Languages MVC ORM About Roadmap Contact Site Map RSS Sample Code Presentations Snippets dll Hell .net Rate My Snippet

About Code Voyeur

Who am I?

All content on CodeVoyeur.com is written and maintained by me, John Zablocki. I work as the Development Lead at MagazineRadar, Inc., an information services provider based in New York, NY. I also work as an Adjunct Professor at Fairfield University.

I became interested in open source while a student at Rensselaer at Hartford. I was hooked after using Ecplise, MySQL and Apache Tomcat in a course on J2EE and enterprise app developement. In that class, we learned about Hibernate and JUnit, which later led me to NHibernate and NUnit. I've been adding open source .NET projects to my development arsenal every since.

What's Code Voyeur all about?

The intent of the Code Voyeur site is to address what I consider to be one of the most significant obstacles to open source adoption in the .NET community - discoverability. There are several MVC frameworks available to a .NET developer. These frameworks live across a number of community sites (SourceForge, The Codehaus, CodePlex, etc.). I'll narrow down the field by writing about my favorites.

It's also hard to know where to find a good MVC web framework if you don't know why you might want one or what one is. To that end, I'll post articles about the various design concerns many of the projects are attempting to address.

What's Code Voyeur not all about?

Code Voyeur isn't trying to replace project documentation. Many projects have very complete API references and quick starts. However, changes to docs tend to lag behind changes to code. I often work with the nightly builds and use unit tests and project support forums to figure things out. I'll be posting articles about features that are not yet documented (and consequentially might never be released).

What about the articles?

Each article will be written with a very specific purpose in mind. That purpose is to meet the needs of today's Google power developer. In other words, I think developers use Google to look for very specific information - "Validation in Spring.NET" or "RollingFileAppender in log4net." I'll be writing recipes for common tasks.

Why open source in .NET?

The obvious answer is to save time and budget by not reinventing the wheel. A more subtle answer is that there is a great deal to learn from studying these projects. I had no idea what Aspect Oriented Programming was before I started off with Spring.NET. Castle's MonoRail convinced me that there's a faster (and better) way to build ASP.NET apps than out-of-the-box web forms. Open source projects expose you to some of the best developers in the world, solving problems you might not have known existed.

What Projects are used in this site?

My choice of projects was influenced primarily by a desire to learn Spring.NET's data project.