Just start programming in anything really (except PHP, since you may learn some bad habits). Make something you want (i.e. it could be as simple as a greasemonkey script for FF/UserJS for Opera/GreaseMonkIE [or equivalent] for IE). Then try to see if you can program it in a better way and continue to refine it as much as you can.
Ultimately, you're going to learn that writing solid tests are equally, if not moreso, important as writing solid code. They help you determine the root problem, so I suggest just writing some code and learning how to properly test it. Also, test everything! I was coding a project and I think without a proper test suite (I made) and a debugger I would have never finished.
Professor Felleisen is an amazing professor, I had him for the fall semester for "Fundamentals of CS 1" and he really pushed you. Then his higher level course, "Software Development", I hear that he radically changes the requirements at the last minute. I guess that's to help you learn how to design a solid program in the beginning and then be able to easily change it down the road. It's supposed to be more like the "real world" (but I'm not quite sure when I'll get there).
I was wondering where people are coming from to go to the startup meeting, because I've been having trouble getting decent tickets so I wanted to know where are people looking for tickets/accommodations.
Ultimately, you're going to learn that writing solid tests are equally, if not moreso, important as writing solid code. They help you determine the root problem, so I suggest just writing some code and learning how to properly test it. Also, test everything! I was coding a project and I think without a proper test suite (I made) and a debugger I would have never finished.
Professor Felleisen taught us a design recipe: http://www.ccs.neu.edu/home/matthias/211-f06/Assignments/recipe.html and it works really well, it ensures a structured and organized code that is easy to maintain down the road.