70537401
submission
DoofusOfDeath writes:
I work on a fully distributed software development team with 5-10 people. Normally it's great, but when we're doing heavy design work, we really need to all be standing in front of a whiteboard together. This is expensive and time consuming, because it involves airplanes and hotels. Conference calls, editing shared Google docs, etc. just don't seem to be the same. Have people found any good tools or practices to replace standing in front of a real whiteboard?
40471253
submission
DoofusOfDeath writes:
I've done a good bit of SQL development / tuning in the past. After being away from the database world for a while to finish grad school, I'm about ready to get back in the game. I want to start contributing to some OSS database project, both for fun and perhaps to help my employment prospects in western Europe.
My problem is choosing which OSS DB to help with. MySQL is the most popular, so getting involved with it would be most helpful to my employment prospects. But its list of fundamental design flaws seems so severe that I can't respect it as a database.
I'm attracted to the robust correctness requirements of PostgreSQL, but there don't seem to be many prospective employers using is. So while I'd enjoy working on it, I don't think it would be very helpful to my employment prospects.
Any suggestions?
