A list of select principles that have been particularly useful in helping design, refine, and debug complex systems (both computer & human)
Any organization that designs a system (defined broadly) will produce a design hose structure is a copy of the organization's communication structure.
| @exemplar/native-storybook: 7 | |
| @exemplar/storybook: 9 | |
| @exemplar/storybook-react: 35 | |
| @exemplar/storybook-react-native: 6 | |
| @gasket/assets: 310 | |
| @gasket/cli: 641 | |
| @gasket/data: 225 | |
| @gasket/engine: 505 | |
| @gasket/fetch: 212 | |
| @gasket/helper-intl: 230 |
| # Ignore things not in the gist | |
| * | |
| !facade.js | |
| !hebcal.js | |
| !README.md | |
| !temporal.js | |
| !why.png |
| const puppeteer = require('puppeteer'); | |
| const util = require('util'); | |
| const fs = require("fs"); | |
| const path = require('path'); | |
| (async (url) => { | |
| const browser = await puppeteer.launch(); | |
| const page = await browser.newPage(); | |
| await page.coverage.startCSSCoverage(); | |
| await page.goto(url); |
| executeMultiple | start | |
| executeMultiple | end | |
| executeMultipleAsync | start | |
| executeMultipleAsync | end | |
| executeMultiple | execute1 | |
| executeMultipleAsync | execute1 | |
| executeMultiple | execute2 | |
| executeMultipleAsync | execute2 | |
| executeMultipleAsync | callback |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"/> | |
| <title>es6 proxy #jsbench #jsperf</title> | |
| <script src="https://cdnjs.cloudflare.com/ajax/libs/benchmark/1.0.0/benchmark.min.js"></script> | |
| <script src="./suite.js"></script> | |
| </head> | |
| <body> | |
| <h1>Open the console to view the results</h1> |
| Start | 1 | foo | |
| Start | 2 | bar | |
| Start | 3 | bazz | |
| End | 2 | bar | |
| End | 3 | bazz | |
| End | 1 | foo | |
| [ 'foo', 'bar', 'bazz' ] |
@salakar, @ashoat, @indexzero, @swaagie, @3rdeden, and @msluther met today to discuss this. This is the draft proposal written up during that meeting. We plan to iterate on this over the next week and then post it into a new proposal in
react-native-community.A recording of that meeting can be found below in MP4 format.
| #!/usr/bin/env bash | |
| for FILE in ./*/**/config.json; do | |
| PNAME=`dirname "$FILE"`; | |
| PJSON=`cat "$FILE" | json notes`; | |
| if [ ! -z "$PJSON" ]; then | |
| echo "$PNAME $PJSON"; | |
| fi | |
| done |
| question: | |
| - https://github.com/winstonjs/winston/issues/1107 | |
| - https://github.com/winstonjs/winston/issues/1119 | |
| - https://github.com/winstonjs/winston/issues/1088 | |
| - https://github.com/winstonjs/winston/issues/1148 | |
| - https://github.com/winstonjs/winston/issues/1167 | |
| - https://github.com/winstonjs/winston/issues/1192 | |
| - https://github.com/winstonjs/winston/issues/1201 | |
| - https://github.com/winstonjs/winston/issues/1275 | |
| - https://github.com/winstonjs/winston/issues/1226 |
