I've worked this way for a very long time, and it has worked out very well for me.

Key is just having the right intuition, for what is "special" and needs to be written and what isn't "special".  And it's even easier now with a common framework, in the past I remember finding what others had done, and having to port it, now usually it just works :).

I contend that one day (perhaps today) it'll be possible to write an averagely complex application by copy/pasting code found on the web and then renaming a few variables.

BTW What logging features does .NET have baked in? (that you were alluding to...)

What's better is when log4net is used.

And then an all new logging tool is built around it.

Sweet

Wow - that looks like a direct attack on this project: www.codeplex.com/ukadcdiagnostics

Which is both a logger (well, it extends what's built in to .NET already) and uses IL.Emit!

Josh

Yes, I am a contributor :)

Your post is timely.  I just wrote DuckCallLib (www.codeplex.com/DuckCallLib) before my colleague Jason Bock notified me that I basically just wrote a very poor man's Dyanmic Proxy, which is a problem both he and you have already solved.

My bad :)  Thankfully, I am only 12 personal hours into this, not work hours.

Or give search.msdn.microsoft.com a shot! We're working really hard on improving search for developers and I think you'll be plesently surprised with the improvements that we've made thus far. For more info check out blogs.msdn.com/msdnsearchblog.

Warning.... using google can be like looking through a garbage heap for something edible. There are a lot of experienced people out there share good things.

But there are lot more people who spend more time blogging than actually "eating their own dogfood".

Another warning... Don't be a CoPaster

www.obrienjd.com/.../The-copypaste-generation-(CoPasters).aspx

I think you're touching on a bigger problem: developers *want* to develop technical solutions, not business ones. They'll often jump at the half-chance to develop a new logging infrastructure or utility layer of some sort to the detriment of actually producing something with business value.

I'm not so sure it's entirely out of ignorance of what's out there, it's often more a case of 'I can do better' and 'working on X utility code is more interesting than working on Y business code'.

@Josh

I, too, have side projects that are aimed more at providing framework/utility code. I don't see a problem with this: it's a project dedicated to solve a particular problem, and that problem just happens to be technical rather than a business problem.

I think what Jeremy's getting at (and I apologize for putting words in your mouth, Jeremy) is that if there is a business problem to be solved, we should be *avoiding* solving technical problems, especially when they've already been solved well.

Heh. "co-irkers". A typo or...

And just ask Oren, he would have written the solution for you in 8 lines.

What bothers me is when someone writes an application and starts it off as godawful complex, without even trying to do something simpler.

An example would be a co-irker of mine wrote an application for which there are multiple different hardware types to be abstracted. He wrote a single base class, to which he adds all the functionality of a new piece of hardware to whenever that hardware is added. In most cases, 50-90% of the interface is dead code/degenerate functions. What I realized is that, the way it's set up, it's much simpler to use the command pattern and that's that. How is it that a relative nublet programmer (me - 1.5 years experience) came up with this significantly simplified version of the base class interface (no specific functions, just the one called Send(ICommand command)!), when a person with 15+ years of experience was completely blind to it? As a friend of mine said, "Welcome to the real world."

The fact is, the author of said class didn't look for anything simpler. He made it ridiculously complex from the start, and now when someone else has to add a new piece of hardware to the top, that person is left in a coma - because their brain shut down when they saw how it was "designed"!

@Kent and Jeremy

I sort of realised that you weren't attacking this type of activity but I wasn't going to pass up the chance to draw your attention to the project :)