| # Adapted from https://github.com/bennofs/nix-index/blob/master/command-not-found.sh | |
| command_not_found_handle () { | |
| if [ -n "${MC_SID-}" ] || ! [ -t 1 ]; then | |
| >&2 echo "$1: command not found" | |
| return 127 | |
| fi | |
| echo -n "searching nix-index..." | |
| ATTRS=$(@nix-locate@ --minimal --no-group --type x --type s --top-level --whole-name --at-root "/bin/$1") |
| import pandas as pd | |
| import plotly.graph_objects as go | |
| from scipy.signal import savgol_filter | |
| data = pd.read_csv('DOGE-USD.csv', index_col=0, parse_dates=True) | |
| data.head() | |
| # Savitzky-Golay filter | |
| y_filtered = savgol_filter(data.High, 11, 2) |
| ### | |
| ### [2023-06-19] UPDATE: Just tried to use my instructions again on a fresh install and it failed in a number of places. | |
| ###. Not sure if I'll update this gist (though I realise it seems to still have some traffic), but here's a list of | |
| ###. things to watch out for: | |
| ### - Check out the `nix-darwin` instructions, as they have changed. | |
| ### - There's a home manager gotcha https://github.com/nix-community/home-manager/issues/4026 | |
| ### | |
| # I found some good resources but they seem to do a bit too much (maybe from a time when there were more bugs). | |
| # So here's a minimal Gist which worked for me as an install on a new M1 Pro. |
(full article by Andrew Welch here: https://nystudio107.com/blog/dock-life-using-docker-for-all-the-things)
alias composer='docker run --rm -it -v `pwd`:/app -v ${COMPOSER_HOME:-$HOME/.composer}:/tmp composer '
alias composer1='docker run --rm -it -v `pwd`:/app -v ${COMPOSER_HOME:-$HOME/.composer}:/tmp composer:1 '
alias node='docker run --rm -it -v `pwd`:/app -w /app node:16-alpine '
| tags |
|---|
coaching, scrum |
(notes taken from the article https://medium.com/the-liberators/how-to-use-powerful-questions-virtually-46a76096630a)
The best way to unleash teams is to ask questions instead of giving (your) solutions.
| javascript: Promise.all([import('https://unpkg.com/[email protected]?module'), import('https://unpkg.com/@tehshrike/[email protected]'), ]).then(async ([{ | |
| default: Turndown | |
| }, { | |
| default: Readability | |
| }]) => { | |
| /* Optional vault name */ | |
| const vault = ""; | |
| /* Optional folder name such as "Clippings/" */ |
| // in a new folder be sure to run "npm init -y" and "npm install puppeteer" | |
| const puppeteer = require("puppeteer") | |
| const fs = require("fs/promises") | |
| async function start() { | |
| const browser = await puppeteer.launch() | |
| const page = await browser.newPage() | |
| await page.goto("https://learnwebcode.github.io/practice-requests/") | |
| const names = await page.evaluate(() => { |
| Software documentation types: | |
| https://ibb.co/0s7W7TD | |
| Key topics to document | |
| - Architecture of how microservices or system components interact with each others | |
| - Decision documents | |
| - architecture of each component or microservice on its own | |
| - When/How to run Migrations and how to generate | |
| - Design System documentation / storybook if applicable | |
| - GUI for the database? |