For those of you who happen to write software for a living, and even for those of you who aspire to one day sit in your mom's garage all night typing assembly and BASIC into your Altair computer because it makes you hardcore, you should check out stackoverflow.com. 
So what is this stacky overflow thing again? Well a stack overflow is a computing problem when one runs out of memory on the call stack. As PCMag.com defines it ,a stack overflow is:
An error condition that occurs when there is no room in the stack for a new item.
But that still doesn't explain what the site stackoverflow.com is about now does it. Maybe we should look at the explanation from their site:
So we have another question and answer site....oh great. We all remember Yahoo! answers and how that worked out, heck, even the Google had a Q&A site and they took it down because it was becoming too much "how do you milk a goat," type of stuff. Either way, stackoverflow has a vast community of programmers that will offer you answers to your questions in an extremely fast manner (it is language agnostic, whether you program in Ruby on Rails or Java, it is all the same). How fast you might ask? Let me demonstrate, I will ask a rather narrow question at this time, it is now 7:58 AM:
(have a SQL Server 2005 database and I have 4 GB of text files that I need to import into it. The question is, if these 4 GB of text files are 1.2 GB when they are zipped, how big would the database be if they are imported? Does SQL Server shrink data by default, or how would I set this (think create a database as a detached item, to be attached to another DB later).)
It is now 8:02 AM, and lets see if I received an answer to my question:
(SQL Server will not shrink data by default. In fact, there will be a small overhead per column and row, so it would require more space.
If you really must store those files in the DB (it is recommended that you don't), take a look at this article I blogged a while back. In SQL Server 2008, they have introduced the FILESTREAM type.)
Sure enough, I actually got an answer to my question, a link to an article that helps more with this question, and I learned something along the way, all in three minutes or so.
So the next time that you are stuck, when you need some help to get over a problem and you are really thrashing, get out there, ask a question, and get some answers that will allow you a peaceful and wine filled (this happens, right?) programming experience.