FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
| from pprint import pformat | |
| from typing import Any | |
| from pygments import highlight | |
| from pygments.formatters import Terminal256Formatter | |
| from pygments.lexers import PythonLexer | |
| def pprint_color(obj: Any) -> None: | |
| """Pretty-print in color.""" |
I fell in love with CoffeeScript a couple of years ago. Javascript has always seemed something of an interesting curiosity to me and I was happy to see the meteoric rise of Node.js, but coming from a background of Python I really preferred a cleaner syntax.
In any fast moving community it is inevitable that things will change, and so today we see a big shift toward ES6, the new version of Javascript. It incorporates a handful of the nicer features from CoffeeScript and is usable today through tools like Babel. Here are some of my thoughts and issues on moving away from CoffeeScript in favor of ES6.
While reading I suggest keeping open a tab to Babel's learning ES6 page. The examples there are great.
Holy punctuation, Batman! Say goodbye to your whitespace and hello to parenthesis, curly braces, and semicolons again. Even with the advanced ES6 syntax you'll find yourself writing a lot more punctuatio
| #!/bin/env python2.7 | |
| import sys | |
| import loadimpact | |
| import json | |
| from loadimpact import LoadZone | |
| from loadimpact import UserScenarioValidation | |
| client = loadimpact.ApiTokenClient() | |
| def usage(): | |
| print "\nUSAGE: ", sys.argv[0], ' download SCENARIO_ID SCENARIO_FILE.lua' |
Dan DeLeo appeared on the FoodFightShow some time ago to walk through "what a Chef run really does". I expanded on these remarks in my personal investigation.
bin/chef-client creates a new Chef::Application::Client (subclass of Chef::Application which sets up common things like loggers across chef-client, chef-solo, knife, etc.) then jump to:
lib/chef/client.rb
application classes create a new Chef::Client object, which calls initialize().
| # the file doesn't exist | |
| TASK: [debug var=foo] ********************************************************* | |
| ok: [localhost] => { | |
| "foo": { | |
| "changed": false, | |
| "invocation": { | |
| "module_args": "path=/tmp/file", | |
| "module_name": "stat" | |
| }, |
| r53 = AWS::Route53.new( | |
| :access_key_id => 'aws-key-id', | |
| :secret_access_key => 'aws-secret-key') | |
| response = r53.client.list_resource_record_sets( | |
| :hosted_zone_id => "zone-id", | |
| :start_record_name => 'xxx.example.com', | |
| :start_record_type => 'CNAME' | |
| ) | |
| puts response[:resource_record_sets].map{|r| r[:name]} |
A lot of math grad school is reading books and papers and trying to understand what's going on. The difficulty is that reading math is not like reading a mystery thriller, and it's not even like reading a history book or a New York Times article.
The main issue is that, by the time you get to the frontiers of math, the words to describe the concepts don't really exist yet. Communicating these ideas is a bit like trying to explain a vacuum cleaner to someone who has never seen one, except you're only allowed to use words that are four letters long or shorter.
What can you say?
Just install this in your apps like so:
gem 'test-spec-mini', :git => 'git://gist.github.com/1806986.git', :require => 'mini'
