This script sends fresh LinkedIn job postings to Telegram 24/7 so you can apply quickly.
- Create a folder for this project. It should initially contain two files, and the script will generate two more:
linkedin-notifier.mjs(copy from this gist)
| Please see | |
| https://www.a-laughlin.com/how-quantify-engineering-efficiency-savings/ | |
| for the latest version. |
These guidelines are for an in-house infrastructure team that supports one or more product teams. They focus on UI component library design.
| node_modules | |
| package-lock.json |
| /** | |
| @name constructTree | |
| @description Creates vertex and in-edge hashmaps given a topology | |
| @example | |
| assert.deepStrictEqual( | |
| constructTree([ { breadth: 2 }, { breadth: 1 } ]), | |
| { | |
| vertices: { | |
| '0': { id: '0', depth: 1 }, |
| // purpose: tools to make replacements from deeply nested objects to imports for large codebase migrations | |
| // usage: | |
| // https://astexplorer.net/#/gist/b8ff1963328449b8063253147c04a462/111b0113648c8f800e8fac56d54e49006c3c2c2b | |
| const isObjectPath = p => | |
| p.type === 'MemberExpression' || | |
| p.parentPath.type === 'MemberExpression' || | |
| (p.parentPath.type === 'CallExpression' && p.parentPath.parentPath.type === 'MemberExpression'); | |
| // loops over a path, starting at base object, up to the first function call | |
| const eachPath = fn => p => { |
| Component Driven Design Notes | |
| Basic concepts? | |
| Bottom up from small components | |
| Benefits? | |
| Efficiency (Faster development) | |
| Testability (More) | |
| Enables component library/explorers | |
| One separation of concerns (Separation of concerns) | |
| Different Separations of Concerns? | |
| . Page-Based (Before MVC) |
| // Available variables: | |
| // - Machine | |
| // - interpret | |
| // - assign | |
| // - send | |
| // - sendParent | |
| // - spawn | |
| // - raise | |
| // - actions |
| Testing Notes | |
| Tradeoffs (high-level): | |
| ref? https://kentcdodds.com/blog/unit-vs-integration-vs-e2e-tests#cost-%EF%BF%A0-heap-- | |
| . Cost: Time to write/maintain/fix/run tests in Dev/Dev | |
| . Feedback Speed: Longer time to get feedback. | |
| . Confidence: How confident do we feel that passing tests mean users will actually experience the same behavior in production. | |
| . Confidence vs Cost/Feedback Speed | |
| Accessibility concerns to test? | |
| . Flows, like multiple keyboard navigation steps | |
| . Screen reader testing |