I don't have any data on this, but I suspect the Windows community is more split between iOS, Android, and Windows Phone than the Apple community.
890 karma · joined March 14, 2012
I don't have any data on this, but I suspect the Windows community is more split between iOS, Android, and Windows Phone than the Apple community.
I just hope they release new MacBook Pros.
Not only is there little to no support for teachers, but it sometimes feels like because there are a few bad teachers floating around in the system, that everyone needs to be punished and inconvenienced. I like job security as much as the next person, but I was a huge advocate for getting rid of tenure as a result.
I'm still incredibly passionate about education, but suspect that being a teacher is the best way to create change. Even in my short tenure, the amount of bureaucracy had increased exponentially. When asked for advice on becoming a teacher by a college student recently, I recommended against it—which broke my own heart, because I believe that it's an incredibly important profession—just not one I would give my twenties to again knowing what I know now.
In fairness, the HN guidelines are pretty clear about this one:
Please don't submit comments complaining that a submission is inappropriate for the site. If you think something is spam or offtopic, flag it by going to its page and clicking on the "flag" link. (Not all users will see this; there is a karma threshold.) If you flag something, please don't also comment that you did.
That is, of course, if we're putting aside some of the basic UNIX tools that probably haven't changed since the 1970s—which I think is fair.
Hacker School doesn't take a segment of your earnings either. They try to get you a job at then end they take a recruiting commission from whoever hires you, but nothing from the student.
In fact, I don't know of a single school that does this. gSchool refunds your tuition if you don't find a job. Flatiron School refunds a portion if you take a job through one of their partners. No one, as far as I know, takes a portion of student's salary beyond the tuition.
Hacker School is free. Essentially, it's a 3-month, self-directed program but you're surrounded by dozens of like-minded individuals and some incredibly talented veterans from the industry.
As you probably already know—JavaScript is a language and the rest are all libraries and frameworks built in JavaScript (Node also has a C++ core too, but I digress). Just like Ruby is the language that Rails is built in.
The first distinction is between client-side and server-side technologies. Client-side code (e.g. Angular, Ember, Backbone, jQuery) run the in browser on the user's computer. Angular, Ember, and Backbone try—to an extent—to apply the MVC approach (like in Rails) to your JavaScript on the client in an effort to keep your code organized and DRY.
You only need one of the three. Backbone is probably the most popular. Angular, which is built by Google, also has a strong following. Ember is up and coming, but it's built by Yehuda Katz amongst others. Yehuda is a core contributor to Rails and Ember shares many of the same values (e.g. convention over configuration). In addition, it's built to play nicely with Rails. Backbone is the most minimal of the three and Angular takes an approach that expands HTML in interesting ways. It's worth dabbling in all three and seeing which one tickles your fancy. I should note that you can use any of the three with Rails. That might be a good jumping off point as you explore the world of JavaScript.
Okay, now on to the server. Node.js is a completely different beast than Rails. It's a platform, not a framework. This a bad example, but it's probably closer to Apache, Nginx, Webrick, or Mongrel than it is to Rails or Django. It basically creates a server-side JavaScript environment based on Google's V8 JavaScript engine along with some basic modules for networking and filesystem IO.
A big difference is the community. The Node community tends to favor small, modular code that can be pieced together to create bigger systems. As a result, large monolithic frameworks like Rails haven't really gain any kind of traction in the Node community. The frameworks exist, sure—Sails and Tower are two such examples, but they haven't really taken off.
The best place to start is probably Express.js, a popular but lightweight framework for Node inspired by Ruby's Sinatra. If you're not familiar with Sinatra in Ruby, play with that first (along with Ember, Backbone, or Angular) and then try Express. Express is actually a little more robust than Sinatra (for example, it includes a solution for logging—Sinatra does not).
It's also worth getting comfortable with NPM (the Node Package Manager). It's a lot like RubyGems, but with some interesting differences—for one, it keeps your modules (gems to the Rubyist) in a directory local to the project. I like to think that NPM is what RubyGems would be if RubyGems got to start over knowing it's own mistakes.
I hope this helps. Feel free to reach out to me on Twitter (same username) if you have any further questions.
When I saw this link, I expected that Apple was making their apps (e.g. Pages, Keynote, Numbers) free ahead of the anniversary of their App Store. Apparently, that's not the case.
A few months ago, I pinged Isaac on Twitter for advice on where to go next once you had a rudimentary understanding of how Node works. He encouraged me to dig into Node core and also to explore the source for NPM and libuv. I suggested that I was pretty sure that stuff was a bit over my head.
Isaac replied: "The best way to get strong is to lift heavy things."
I wrote some database software that took a lot of the hurt out of the process. Pop in the data in CSV format and it crunches all of the numbers and connects all the dots. That said, the whole workflow is still a bit of a pain. Most of the data is locked up in silos lacking any sort of API, but sporting a user interface that compels a little piece of my soul to shrivel up every time I have to log in and download the CSVs. Additionally, I have to bother the school support staff because I don't even have access to some of the data. Each different data source requires me to write a different parser. In the mean time, I still have to plan lessons and teach kids.
I've kicked the tires on the Clever API and it's fantastic for my purposes. They've done some incredibly cool stuff to make it easy to access data I've previously struggled to get my hands on. I'm really excited about the work they're doing and super-excited for more partners to come on board and use their API. It's going to change the way we deal with student data and ultimately get quicker information out to our teachers so that they can make better instructional decisions for our students.