| # Thanks to this post: | |
| # http://blog.ikato.com/post/15675823000/how-to-install-consolas-font-on-mac-os-x | |
| $ brew install cabextract | |
| $ cd ~/Downloads | |
| $ mkdir consolas | |
| $ cd consolas | |
| $ curl -O http://download.microsoft.com/download/f/5/a/f5a3df76-d856-4a61-a6bd-722f52a5be26/PowerPointViewer.exe | |
| $ cabextract PowerPointViewer.exe | |
| $ cabextract ppviewer.cab |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| <!DOCTYPE html> | |
| <html lang="en" xmlns="http://www.w3.org/1999/xhtml"> | |
| <head> | |
| <meta charset="utf-8" /> | |
| <title></title> | |
| </head> | |
| <body> | |
| <script> | |
| "use strict"; |
| This regex parses attributes from their values such as those in HTML elements. It returns the attribute | |
| names and their values even when the quotes are escaped, nested, or omitted. | |
| The following are examples attribute/value pairs that are properly divided: | |
| a="a" b="b b" c='c' d=1 e="escaped \" quotes" f="'nested quotes'" g = 'gaps' h="multiple spaces" | |
| The attribute name will be in match position 0, while the value will be in either position 4 or 5 | |
| depending on whether or not the value is quoted. |
| jQuery Touch Gestures ported from QUOjs | |
| @see http://quojs.tapquo.com/ | |
| Version 1.1 | |
| -- @add singleTap event | |
| -- @fix doubleTap event | |
| -- @fix hold event |
| ffprobe -v quiet -print_format json -show_format -show_streams "lolwut.mp4" > "lolwut.mp4.json" |
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
