The Static Spider Web Pattern

I would laugh if it wasn't so sad. I think this article shows a valid design pattern for a lot of programmers. Unfortunately.

Very smart article where everyone will find food for thought! Congrats.

If you're working in a container and this ones doesn't manage your instanciations, you end up working more or less like what's described above. Even if you're experienced.
The typical example was a Struts app using Hibernate a few years ago. No matter how hard you tried you were forced to "propagate static". 

Then DI arrived and solved a part of the problem. You still had some static "entry points" here and there.
With nowaday's SE/EE and a handful of thoughtful developers, you can avoid that issue :) Not always though.

I started banging my head on my desk when I read the author's comments on object allocation. Then, I saw his comments on static methods, then I nearly passed out. I blacked out when XML came into the mix. When I woke up, I realised the sarcasm. Hopefully, no one will take this article seriously.

Don't worry, this article is about C# (properties, small string, bool instead of boolean, funny IDE). Nobody programs java this way anymore ;)

Ship it!

That's a good one.

I would have laughed if I didn't have to deal with this approach on a daily basis...

It will take us years to refactor your code :P

This is so funny I would laugh if it wasn't for the almost heart attack I had when reading this. Good graphics. Then just when I had my injection directly to the heart and came back to life I realised that hey maybe this is a joke and a critisism to what happens in most (commercial)java projects. Sadly most of the comercial java projects I have seen have this pattern or even worse. Testability : How can you possible test a static method???????? If a static method calls another static method calls 20 more static methods that each needs some special services running to deliver x values, how in this world would you unit test that???? With a decent OO design you'll be able to mock this and mock out the methods that need the special services. How in this world would you do this with Java using static methods??? Byte code engineering??? In this world, if you just whant to write a test for a new algorithm for what every sos imple you've written you don't whant to launch special services like Web Service, JNDI service, Open EJB, Tomcat, Jetty, the lot and 2minutes later you'll be able to run your test, so that you can pass the string "222^200:200^122^2200:200" to it and get result 2. this is sad but most java projects are written this way :(, and then java gets the wrap for project failure. On more than one project I've seen its almost better the start from scratch than continue with statics all over the place. Please when we learn about Factory pattern and other static method prone patterns it doesn't mean use static when every you can!!!!....