![User profile image.](/sites/default/files/pictures/picture-420-43d21d07879f65200ca9dbd2fcb04803.jpg)
I have always been interested in computers, and would find myself hanging out with the Computer Science students instead of the Aviation Management or Business Management students I was a part of. At home and at work I have been largely self-teaching myself using computers starting with Excel and Access with VBA through ASP and SQL at work. Thankfully my current employer values education, and so I have been taking classes and not only learning the technology, but un-learning what I have been doing wrong over the years. At home, though, I have been teaching myself Linux, system administration, networking and the overall method of migrating our system from Windows to Linux. I am involved in the Danbury Area Computer Society (DACS.org) I have the opportunity to take what I've learned the hard way and hopefully help others.. I have been enjoying Open Source for a while now, and I am hoping to get a better understanding of the entire model and application.
Authored Comments
We have gone from trying to run hours-long meetings to smaller, more focused meetings.
Twice a week (T,Th) we have a "standing" meeting where it is supposed to be so quick there's no time to sit down (or get comfortable). It's purpose is to go over what is being worked on now or the near future, and a chance to see if/how it impacts everybody else (e.g. how many projects does person xyz need to put into production this week?). We allocate 5 minutes per person.
Then we have our weekly status meeting one-on-one to go over what we are working on, prioritize our projects and allow discussion on our needs without boring everybody (or going into details). That can be 30 min or more as necessary.
Every week to 2 weeks we have a meeting that lasts the longer time period to discuss projects and look for more efficiency, talk more technically and collaborate on a deeper, detailed manner. That one we are working on outlining the purpose or subject of the meeting before hand.
These smaller meetings means we have access to each other more often, we can determine if something impacts any one of us that may not have thought about before, can discuss the technical issues in depth if necessary and otherwise be informative, done and back to work.
What is the performance like with using the Raspberry Pis? Compared to a traditional desktop or desktop computer cluster?
I'm sure you can tell I am not familiar with clusters, but wonder what the performance boost is like by clustering (and whether I could use something like this to replace my own home servers ;) )