Alex Papadimoulis discusses avoiding over-engineering a program, presenting extensibility types used, extensibility design patterns, when to use them, and what happens when they are incorrectly used.
Alex Papadimoulis is the founder and editor of The Daily WTF, a leading how-not-to guide for developing software. Residing in Berea, Ohio, he is a software engineer at Inedo and uses his 10+ years of IT experience to help software development organizations utilize best practices in their products though BuildMaster, a next-generation ALM suite.
Code PaLOUsa is a conference designed to cover all aspects of software development regardless of technology stack. It has sessions revolving around Microsoft, Java, and other development platforms; along with session on higher levels that are platform agnostic. The conference schedule will feature presentations from well-known professionals in the software development community
Exactly these codes will end up at the Daily WTF
I've seen applications on a daily basis where they followed Alex' advice, like, they actually forked an application instead of providing clever extensibility, ending up with managing two full applications for more than 10 years, where one even had to stay in an unsupported platform. I see code without any design patterns or config files.
The only reason those codes didn't end up at Daily WTF is usually NDA. A full team of outsourcing company can laugh at you just before committing such errors themselves.
So, remember: that f.ing dumbass who did that crap and can't code, in the eyes of your project's next maintainer (or the first one who doesn't know you) is you!