Jeremy Hutchings

I’m happy to see lots of people supporting and stating the obvious about this topic. Though I thought I’d add my 2c to the demise of this all to common evil of open offices. They are typically favoured by individuals who like to interrupt others, and also by those who look to short term visible costs. Open offices are likely the single biggest cause in companies of: The lost of human happiness The lost of team/individual effectiveness The lack of success of companies and projects I rank them in that order for importance as well, as that’s the order I’ve typically experienced them being absent in successful projects. I believe the mental state of the members of the team, and the collective teams health is a core (if not the primary) factor in successful outcomes. It’s good to see the academic community supporting (with research) what many have felt and known to be true for so long [1] , I’ve spent many years in different office environments, when I haven’t...

I noticed a post from an past college  Scott MacVicar  about getting involved with and helping out PHP.  Personally I've always thought about it and wanted to, though have always focused on hard core C, thinking : "Helping PHP, means writing hardcore C, and building libraries" The more I thought about that statement, and the way I typically think about software, Open Source and communities, I realized  what nonsense that is . There is so much more going on in a project and community, therefor there are many more ways to help. Developing a technology & community is a holistic activity . Some of us are writers, framework developers, application developers, business decision makers, power users, clients making requirements, community members, and so on. Though a lot of us, are more than one role, it takes us all and there is always room for more. Though you could use these points for any OSS project, I'm just ...