I was in a similar boat. I was already programming in qbasic when I was around 14-15, but went to a standard high school. Math had always been my strong point, but I lost interest and my grades suffered. It was then very difficult to catch up because I wasn't learning whatever I needed to learn throughout the year.
I did however excel at the programming course we had. I loved going to the computer lab and trying stuff out. This school would have been awesome if it was around when I was in school. It would have been a perfect fit.
Or the producers of television see this as a way to not deal with the networks and still get their show distributed to people, and the networks find themselves without good television to put on the air.
This article has tons of gold in it besides the "don't call yourself a programmer" part. I actually thought the paragraphs past that were better, especially for the younger crowd. I want to send this post to every kid that's about to graduate college.
This is the same problem I have with this approach. It seems like a cool idea, but I don't want to break accessibility. I think you can get around this using aria and having it skip over that element.
Authors MAY, with caution, use aria-hidden to hide visibly rendered content from assistive technologies only if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content. Authors using aria-hidden to hide visible content from screen readers MUST ensure that identical or equivalent meaning and functionality is exposed to assistive technologies.
I was thinking something similar to this last night. Google+ unifies the product set. Even the new Google mobile web is unified and easier to get around now. I can see it pulling me into products that I don't really use much just because it's more convenient.
This is pretty cool as there isn't much like this in the SFV. It would be nice if there were some photos so we could see what it looks like. I've been to co-loft in Santa Monica a couple times and am hoping this is similar. It would be nice if they hosted some meet-ups like co-loft does as it would be a much closer place to nerd out for people that live closer to SFV.
"Why would I use your product? What's the use case? What value does it provide that the other dozen or so top color pickers DON'T offer?"
Maybe it's just a cool hack. Not everything has to be a fancy boxed up product with the only hope of being sold to Google. Sometimes people just like to build cool things.
simonw hasn't worked on it in a while, but it's been forked a bit to keep up with the latest node. It doesn't give you an orm but does basic regex routing and django style templates.
Crockford's Javascript: The Good Parts, Stoyan Stefanov's books, and Zakas's High Performance Javascript. Also don't forget about http://developer.yahoo.com/yui/theater/. There are a ton of good video lectures to learn from.
I'm in the Los Angles area. There doesn't seem to be an event to actually go to right now, but even if there isn't one I was planning on making an irc channel or something.
I have around the same commute time. Lectures in the car don't work for me. Language audio lessons such as Pimsleur were a little better but still require a bit too much concentration. I can however listen to audio books and follow along.
I think this is an acceptable use of the word. This particular account may not have turned a profit, but it might over time. And even if it doesn't this is certainly more revenue than you would receive with iTunes.
Cheat sheets are great and all, but they don't teach you version control. I think that what we have here is a very difficult topic to grasp for most people, and countless cheat sheets don't make people understand them.
For example, look at how they are telling you to resolve conflicts.
5.) Resolve Conflicts (Merge Others’ Changes):
$svn update
$svn resolved
Resolving conflicts is almost never that easy, unless it's some white space. Even then you still want to peruse a diff to see what is going on. I know cheat sheets aren't meant as tutorials, but glossing over important stuff like resolving conflicts doesn't really help anybody.
Come join my team and help us build http://screen.yahoo.com
We use javascript all over the place.
If you are interested please send me an email with your github.