rhythmAddict

Definitely. That is a grad school worthy slide-deck without a doubt.

I do indeed, sorry - my fingers have a mind of their own.

The font on that blog makes me want to gauge my eyes out.

Take long walks around Manhattan by myself with music blasting. (It's amazing how much faster you walk with some good music on, btw)

This guy better get a job offer from Chad Hurley. Seriously though...genius idea.

See if you can go back to your job, hopefully earlier than later (as in, e-mail your boss if you have not already and tell him you have an important matter to discuss). It's probably best of the HR side of the house does not get too far along. That, or, you can respond to one of the many individuals that said they were hiring (I'm not sure how much time you have/how much time you can be without a job, in general).

Good luck and keep us posted.

I'd agree with this general sentiment. If I need to finish something quickly, provided it's not ridiculous, I will. Also, keep in mind that when you've been writing code professionally, you have access to either code others have written at your organization, code you've written, or both. At times, this can help dramatically. There are countless times when I think "I know I've done this before" and I rip out 10-15 lines of something I worked on 5 months ago and go ahead and adapt it. There really isn't any reason not to do this, IMO...

Also, in general, I don't get a requirement/feature/enhancement/etc and start slamming away in my editor. My personal preference is to think about it, scratch some ideas down on paper/white board and just stare at my monitor while I run everything through my head. It's always my first reaction to think I need to start typing out some code - and [for me] that's usually not the most efficient approach. Once I have a concept/logical-flow in my head that I have run through several times, I'll write that in my editor as comments. After that, it's really just me writing code that adheres to my comments rather than trying to design the program while coding it.

I'm not at all saying this is the right approach for all, but that's certainly the case for me.

cheers

Actually, you guys are right. I realized the flaw in my thought process right after I read seasoup's post.

I do, however, have intellisense in my eyes.

I agree that it makes it "more readable", but that only would matter if intellisense wasn't working. I see the parameters, and they are strongly typed. In JS, this isn't the case, so it is much more helpful (e.g, I can completley screw up types/params and they will probably materialize as some strange behavior. As far as bools, I generally try to avoid having more one or two bools as an argument, unless it's required, and it rarely is.

Obviously, all IMO.

Totally agree. I used spotify for 2-3 months, but after a bit it got annoying when my tor proxy would suddenly stop working, and I'd have to find a new one that had enough bandwidth and was actually reliable enough. It is totally doable, it's just annoying. That said, I would be more than happy to pay their fee.

(If anyone has a solution to this...either a good proxy, or something else. I am all ears. Also, when the eff are they coming to the US? I know they had some plans...)

I now use Grooveshark, it's good, don't get me wrong, but spotify is much better in terms of interface, but mainly they have a better catalog for the music I listen to (mostly ambient/downtempo/trip hop). If I search for a group Grooveshark will likely have 70% of the songs from each album...maybe. Whereas in Spotify, I can just view 100% of all the albums. Also, while I have not used the Spotify mobile app, I can tell you the Grooveshark mobile app kind of sucks.

Cheers

Code Complete 2nd edition

I know I'm being a stickler here, but setTimeout() is conventional JS...