Comment Green House effect (Score 1) 405
If I understand correctly, we'll then be able to determine the White House effect on the green house effect?
If I understand correctly, we'll then be able to determine the White House effect on the green house effect?
God forbid! The only thing putting my mind at ease here is that he'd probably never be able to achieve the code-quality standards that would allow him to contribute to PostgreSQL.
I can recommend the Alix boards. They are very well designed and draw 3 Watt on average, 5 Watt peak at 100% CPU. I've used them with Voyage, which works very well, and I'm in the process of releasing an alix-customised Debian distribution which will provide a richer environment than Voyage, yet still provides facilities as fall-back flash and network boot.
Have you tried the Samsung B2100? I just got one last week. It's waterproof up to one meter deep for 30 minutes, and you can drop it (a lot; tried that already). The casing looks sturdy enough.
Defining classes in Perl is not easy, and I always have to go back to the manpage to make sure I've got all the incantations. Many times, I simply use object oriented structures and forgo the object definitions.
Why o' why does Python use "pop" for arrays, but not "push"? What were the designers on when they decided "exists" is not a member function of hashes -- excuse me -- dictionaries and arrays? Why this syntactic distortion of over 50 years of computer programming overturned?
I never liked Perl or Python, but graduated from sh to awk to Pike. It's not for everyone, but for people used to C syntax, it's a script language from heaven.
There are several reasons why, even in smaller groups, using git is advantageous (even if you have only yourself, no other contributors). I'm not going to name them all, but in my experience (I've used RCS, CVS, SVN and now git), some of the more compelling advantages are that you can:
- Actually permanently erase/fix bad commits from the repository without a painful full dump/tricky edit/restore cycle on the repository. I suppose everyone has some of those occasional moments sometime: "Aaargh, I meant to commit only this one file, not this tar.gz file that happened to be in the wrong place at the right time." Git allows you to correct the mistake without bloat in the repository.
- Patch management (instead of keeping around a bunch of patch files, simply create branches for every patch file you'd normally keep) made easy and trackable.
- And related to patch management: commit early, commit often, then cleanup/merge commits before actually committing them "for real" to the bleeding edge version.
For small groups it means that you simply setup a central git repository everyone pushes to. You get all the benefits of DVCS and classic central management, i.e. it allows you to have your cake and eat it too.
Beware of Programmers who carry screwdrivers. -- Leonard Brandwein