http://railstutorial.org/, http://railstutorial.org/book
Based on Rails 4.0, missing:
- Turbolinks
- Russian doll caching
- New RSpec abilities such as feature specs
/****************************************************** | |
* @author Nootan Ghimire <nootan.ghimire@gmail.com> | |
* @file postfix-eval.cpp | |
* @desc Evaluation of Multi-Digit Postfix Expression | |
*****************************************************/ | |
// C++ Includes | |
#include <iostream> | |
#include <cctype> | |
#include <cstdlib> |
The range sliders at the top change the values for the force-directed algorithm and the buttons load new graphs and apply various techniques. This will hopefully serve as a tool for teaching network analysis and visualization principles during my Gephi courses and general Networks in the Humanities presentations.
Notice this includes a pretty straightforward way to load CSV node and edge lists as exported from Gephi.
It also includes a pathfinding algorithm built for the standard data structure of force-directed networks in D3. This requires the addition of .id attributes for the nodes, however.
Now with Clustering Coefficients!
Also, it loads images for nodes but the images are not in the gist. The code also refers to different network types but the data files on Gist only refer to the transportation network.
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
[assumes everything is installed] | |
cd ruby_rails [ie, wherever you want to keep all your rails projects] | |
rails new_project [create the project] | |
ruby new_project/script/server [wow - your new app is up!] | |
[ctrl-c to kill it] | |
[in new_project dir, do] | |
git init | |
git add . | |
git status |