Make Everything Multi-Threaded So It Runs Faster, and other myths, legends and anti-patterns


As developers and architects, we use patterns regularly to provide consistency to our applications. But as patterns become popular, so do anti-patterns – those practices and habits that may seem productive, sensible or efficient, but end up causing problems down the road. We’ll explore a number of these misconceptions and bad practices (such as “Make Everything Multi-Threaded”, “WET” and more) along with a touch of humor. The anti-patterns and misconceptions will each be presented as a separate module with separate code examples.

David Hoerster

David Hoerster, a 5-time C# MVP, is a recovering corporate financial analyst and has been working with the Microsoft.NET Framework since the early 1.0 betas. He is the Sr. Solutions Architect for Confluence, a managed investments software product company. David is the conference chair of Pittsburgh TechFest, the leader of the Pittsburgh Reactive Systems user group (http://meetup.com/reactive), the former president of the Pittsburgh .NET User’s Group (PGHDOTNET) and is also a regular speaker at Pittsburgh and regional user group and community conference events. David can be found rarely blogging at http://blog.agileways.com and tweets occasionally at @DavidHoerster.