patterns & practices 2.0 – How would it look?
What would a patterns & practices 2.0 look like to you? There’s been a very lively discussion on just this topic on the ALT.NET list (For which I am the instigator). Below is the summary version. Go here if you dare to see the full thread and have hours and hours of free time.
- Guidance on core concepts and principles like OOP, separation of concerns, layering, etc
- Guidance on good software engineering and design practices, code quality, TDD, DDD, BDD, code smells, CI
- Patterns / Anti-patterns – GOF / Fowler, etc (Don’t make up new ones)
- Tutorials / examples
- Be Neutral / Pragmatic
- Trusted advisor on different tools, techniques and methods i.e. Stored Procs vs Dynamic SQL
- Existing OS solutions (NHibernate, Log4Net, etc)
- Be Critical including of community efforts
- Advocate community endeavors
- Engage with the OSS community
- Focus on toolkits and factories
- Become an evangelism org / marketing machine for the platform. (Though it’s okay to become an evangelism org for patterns and good engineering practices.)
- Be Dogmatic (our way is the only way, or even the best way)
- Dumb down developers
Now ALT.NET is only one small sampling of the customers who use our guidance. Do these views resonate with you?