- Authoring Ebooks: http://www.authoringebooks.com/
- Create Your Own Programming Language: http://createyourproglang.com/
- Exceptional Ruby: http://exceptionalruby.com/
- JavaScript Performance Rocks: http://javascriptrocks.com/performance/
- Redmine Tips: http://www.redminetips.com/
- The SPDY Book: http://spdybook.com/
- Rails 3 Upgrade Handbook: http://www.railsupgradehandbook.com/
- Refactoring Redmine: http://www.refactoringredmine.com/book/
- Bootstrapping Design: http://bootstrappingdesign.com/
- Recipes With Backbone:
Original discussion began on Twitter and can be found by starting here and here. Discussion was continued on es-discuss mailing list in the thread Pure win: Array.from and Array.of
Update Nov. 3, 2011
Official strawman has been posted: http://wiki.ecmascript.org/doku.php?id=strawman:array_extras
A Lazy programming is the best hire you can make. Lazy programmers are ideal for a startup. They will be the reason a project will be successful.
-
Lazy programmers hate manual work. They will always automate anything that needs to be done manually. This creates a smarter solution which is less error-prone to the human action.
-
Lazy programmers hate talking to others. They will produce better code so that it works in all cases to avoid being questioned by others on their work.
##day one
- Influences of Node - Ryan Dahl
- Oh the Places You'll Node - Matthew Podwysocki
- Two Years of node in yammer : Matthew Eernisse
- State of the Node - Isaac Z. Schlueter
- Guillermo Rauch
- node knockout
print - lets you output numbers and characters to the console. | |
if - let's you choose which statements are executed if an expression is true | |
else - denotes the statements that execute if the expression isn't true | |
elif - let's you combine if statements | |
while - is a way of repeating statements in a loop until an expression is false. | |
break - is a way to jump out of the statement flow of a loop. | |
continue - let's you skip a cycle of the flow without ending it. | |
for - is used to iterate over items of a collection in the order they appear in a container |
var u = (function() { | |
var id = function(x) { return x; } | |
, single = function(x) { return [x]; } | |
, constant = function(x) { return function() { return x; }} | |
, $ = function(f, x) { return f(x); }; | |
var curried = function(f, n, args) { | |
return (args.length >= n) | |
? f.apply(null, args) | |
: function() { return curried(f, n, args.concat(slice(arguments))); }; }; |
- http://mirnazim.org/writings/python-ecosystem-introduction/
- http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html
- http://effbot.org/zone/python-with-statement.htm
- http://www.python.org/dev/peps/
- http://www.mindviewinc.com/Books/Python3Patterns/Index.php
- http://stackoverflow.com/questions/986006/python-how-do-i-pass-a-variable-by-reference
- http://agiliq.com/blog/2012/06/understanding-args-and-kwargs/
#!/usr/bin/env ruby | |
# checkout the readme from the master branch | |
`git checkout gh-pages; git checkout master README.md` | |
path = `pwd`.gsub(/\n/, "") | |
readme_path = File.join(path, "README.md") | |
index_path = File.join(path, "index.md") | |
# write the index readme file |
Update: The original post on Netmag has been updated since this was written.
I tweeted earlier that this should be retracted. Generally, these performance-related articles are essentially little more than linkbait -- there are perhaps an infinite number of things you should do to improve a page's performance before worrying about the purported perf hit of multiplication vs. division -- but this post went further than most in this genre: it offered patently inaccurate and misleading advice.
Here are a few examples, assembled by some people who actually know what they're talking about (largely Rick Waldron and Ben Alman, with some help from myself and several others from the place that shall be unnamed).