Skip to content

Instantly share code, notes, and snippets.

Avatar
💭
I may be slow to respond.

Nicholas C. Zakas nzakas

💭
I may be slow to respond.
View GitHub Profile
@nzakas
nzakas / pancakes.md
Created Apr 10, 2020
Pumpkin pancakes
View pancakes.md

Pumpkin Pancakes Recipe

Ingredients

  • 1/4 cup pumpkin puree
  • 1/4 cup almond milk
  • 1/4 cup water
  • 3 eggs
  • 1 tbsp coconut oil (melted)
  • 1 tsp vanilla
@nzakas
nzakas / salary.csv
Last active Feb 20, 2020
Salary History Table
View salary.csv
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
View gist:0480cc46409ac8f2eab81125c4a5a077
### 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:
@nzakas
nzakas / environment.log
Created Apr 1, 2018
Netlify Function error log
View environment.log
Nicholas@Patriot MINGW64 ~
$ node -v
v8.10.0
Nicholas@Patriot MINGW64 ~
$ npm -v
5.6.0
View techleadbook.md

Tech Lead Book

  1. Introduction
  2. What is a Tech Lead?
  3. The Tech Lead Mindset
  4. Becoming a Tech Lead
  5. Working Cross-Functionally
  6. The Art of Delegation
  7. Technical Best Practices
  8. Effective Decision Making
@nzakas
nzakas / gist:edbb30b7f3a15ace61e3eb68013603ee
Created Sep 20, 2016
GitHub blocking push to master branch
View gist:edbb30b7f3a15ace61e3eb68013603ee
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: At least one approved review is required.
To git@github.com:eslint/typescript-eslint-parser.git
! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to 'git@github.com:eslint/typescript-eslint-parser.git'
@nzakas
nzakas / githubpainpoints.md
Created Jun 30, 2016
An overview of my pain points with GitHub
View githubpainpoints.md

GitHub Pain Points

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.

Problem: No good way to distinguish new issues from "accepted" issues

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.

View npm-debug.log
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 npm@2.14.9
3 info using node@v0.12.9
4 verbose publish [ '.' ]
5 silly cache add args [ '.', null ]
6 verbose cache add spec .
7 silly cache add parsed spec { raw: '.',
@nzakas
nzakas / arrayproxy.js
Created Feb 16, 2016
A proxy that acts like an array
View arrayproxy.js
// 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
@nzakas
nzakas / output.log
Last active Jan 8, 2016
Test failures
View output.log
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