Join me for some ranting about how best practices from open source development and project management school is making your sustaining team miserable
I dare say most projects start off with a goal of producing code that is easy to maintain for the sustaining crew. But as developers are too often split into either pure development teams or pure sustaining teams, not many in the development teams get to experience what sustaining is actually like. Many seemingly good ideas that are great in the developing phase, make life more difficult in sustaining. Many things that are essential for a good library or framework, are harmful when applied to application development. I want to share some concrete examples and hopefully inspire you all to write applications that is easier for others to work with.
I've been programming for money for 15 years now in all sorts of environments. Done both sustaining work and greenfield development. I like making things, and making things better. I also enjoy making people think, question their beliefs, not just follow authorities, but figure things out for themselves. Have 2 talks in the top 5 most viewed JavaZone talks of all time. vimeo.com/28885655 and vimeo.com/49484333