- 1/4 cup pumpkin puree
- 1/4 cup almond milk
- 1/4 cup water
- 3 eggs
- 1 tbsp coconut oil (melted)
- 1 tsp vanilla
Year | YOE | Company | State | Title | Starting $ | Ending $ | Signing $ | Options | |
---|---|---|---|---|---|---|---|---|---|
2000 | 0 | Radnet, Inc. | MA | Webmaster | $48,000 | $55,000 | - | ? | |
2001 | 0 | Radnet, Inc. | MA | UI Developer | $62,500 | $62,500 | - | - | |
2001 | 0 | MatrixOne, Inc. | MA | UI Designer/Developer | $68,000? | ? | $2,000 | ? | |
2003 | 3 | MatrixOne, Inc. | MA | Senior Software Engineer | ? | $75,000? | - | - | |
2005 | 5 | Vistaprint, Inc. | MA | Lead Software Engineer | $82,000? | $98,000 | - | 3,000 | |
2006 | 6 | Yahoo, Inc. | CA | Senior Front-end Engineer | $115,000 | ? | $10,000 | 3,500 | |
2008 | 8 | Yahoo, Inc. | CA | Principal Front-end Engineer | ? | ? | - | - | |
2011 | 11 | Yahoo, Inc. | CA | Presentation Architect | ? | $165,000? | - | - | |
2013 | 13 | Box, Inc. | CA | Staff Software Engineer | $175,000 | ? | $25,000 | 50,000 |
### Keybase proof | |
I hereby claim: | |
* I am nzakas on github. | |
* I am nzakas (https://keybase.io/nzakas) on keybase. | |
* I have a public key ASDOjUn5w1cYZhamvMdllaGhLM-jbBo23c1TAW6oUYLslwo | |
To claim this, I am signing this object: |
Nicholas@Patriot MINGW64 ~ | |
$ node -v | |
v8.10.0 | |
Nicholas@Patriot MINGW64 ~ | |
$ npm -v | |
5.6.0 |
remote: error: GH006: Protected branch update failed for refs/heads/master. | |
remote: error: At least one approved review is required. | |
To [email protected]:eslint/typescript-eslint-parser.git | |
! [remote rejected] master -> master (protected branch hook declined) | |
error: failed to push some refs to '[email protected]:eslint/typescript-eslint-parser.git' |
This is my feedback on using GitHub to manage a popular project (ESLint). Topics are presented in no particular order. In general, everything I say about issues also refers to pull requests.
For each problem I've suggested a solution. I realize that actually building out a solution is a complex process and my suggestions do not reach the level of detail sufficient for implementation purposes. It's just to give you an idea of the direction I'm thinking.
Users are opening new issues every day, and these issues automatically bubble to the top of the issues list by default. We do label issues that we're committed to doing as "accepted", but if there are enough new issues, you don't even see those until the second page of issues. Why is this a problem? In a word: distraction.
0 info it worked if it ends with ok | |
1 verbose cli [ 'C:\\Program Files (x86)\\nodejs\\node.exe', | |
1 verbose cli 'C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', | |
1 verbose cli 'publish' ] | |
2 info using [email protected] | |
3 info using [email protected] | |
4 verbose publish [ '.' ] | |
5 silly cache add args [ '.', null ] | |
6 verbose cache add spec . | |
7 silly cache add parsed spec { raw: '.', |
// target is the backing object | |
let target = { length: 0 }, | |
proxy = new Proxy(target, { | |
set(trapTarget, key, value) { | |
let numericKey = Number(key), | |
keyIsInteger = Number.isInteger(numericKey); | |
// special case for length property - only need to worry if length is | |
// shorter than number of array items |
8721 passing (45s) | |
81 failing | |
1) CLIEngine executeOnFiles() should report zero messages when given a directory with a .js2 file: | |
AssertionError: expected 0 to equal 1 | |
at Context.<anonymous> (C:\Users\Nicholas\projects\personal\eslint\tests\lib\cli-engine.js:309:20) | |
at callFn (C:\Users\Nicholas\projects\personal\eslint\node_modules\mocha\lib\runnable.js:286:21) | |
at Test.Runnable.run (C:\Users\Nicholas\projects\personal\eslint\node_modules\mocha\lib\runnable.js:279:7) | |
at Runner.runTest (C:\Users\Nicholas\projects\personal\eslint\node_modules\mocha\lib\runner.js:421:10) | |
at C:\Users\Nicholas\projects\personal\eslint\node_modules\mocha\lib\runner.js:528:12 |