I see that there have already been some posts about going into law. I'll try not to repeat what's already been said. Here's my own advice, based on good experience:
(1) Work for a few years doing something CS-related. Whether coding, sysadmin work, user interfaces, or software design, pick something and stick with it for at least a few years. The benefit of doing this is that you'll get invaluable real-world experience and you'll learn what you like and what you don't like. If you're lucky and good at what you do, you might also get some exposure to the business side of CS.
(2) If you're happy with what you're doing and you believe that there's a high potential for growth, stay in your field and look no further; you've found your dream, why break it?
(3) Keep yourself informed about legal issues related to CS. These may be intellectual property, privacy, computer security, computer crime, or even HIPAA/FTC/FCC/securities regulation. Think about how the knowledge you've gained from work has help you understand the issues better.
(4) Take the LSAT. Apply to law schools. As much as it pains me to say so, you MUST be aware of how a law school's ranking affects your ability to get a good job out of school. If you go to Yale, then a good job is virtually guaranteed. It's certainly possible to get a good job out of St. John's and Brooklyn, but the risk is also higher. For some schools, you must be at the top of your class. (FYI, the more technical your skillset, the more likely that a patent prosecution firm will overlook your grades in favor of your experience -- one of the few exceptions to the general rule that LSAT/undergraduate grades/law school grades define your future.)
(5) Again, think LONG and HARD about the financial risk you'll be taking by returning to school. You may not have an income for 3 years.
With all that said, I personally find computer law to be an incredibly fascinating field. A CS background allows me to talk with computer professionals and ask the right questions. It's my job to translate computer knowledge into plain English for a judge and jury. I love the logical puzzles -- both technical and non-technical -- that I need to solve every day. I have the ability to see much more of the "big picture" that CS programmers rarely see, and I hope to eventually apply that knowledge to important policy questions.