Some Description Some text
Click Me To Expand
#!/bin/zsh| /* | |
| * Copyright (c) 1983, 1993 | |
| * The Regents of the University of California. All rights reserved. | |
| * | |
| * Redistribution and use in source and binary forms, with or without | |
| * modification, are permitted provided that the following conditions | |
| * are met: | |
| * 1. Redistributions of source code must retain the above copyright | |
| * notice, this list of conditions and the following disclaimer. | |
| * 2. Redistributions in binary form must reproduce the above copyright |
Download and install the following applications:
| /* | |
| ** in your header, define a reference | |
| */ | |
| - (void)switchViewController:(UIViewController*)view :(NSString*)segue; |
| IndianRed='[38;5;167m' | |
| LightCoral='[38;5;210m' | |
| Salmon='[38;5;209m' | |
| DarkSalmon='[38;5;174m' | |
| LightSalmon='[38;5;216m' | |
| Crimson='[38;5;160m' | |
| Red='[38;5;196m' | |
| FireBrick='[38;5;124m' | |
| DarkRed='[38;5;88m' | |
| Pink='[38;5;218m' |
| // This script takes an iTerm Color Profile as an argument and translates it for use with Visual Studio Code's built-in terminal. | |
| // | |
| // usage: `node iterm-colors-to-vscode.js [path-to-iterm-profile.json] | |
| // | |
| // To export an iTerm Color Profile: | |
| // 1) Open iTerm | |
| // 2) Go to Preferences -> Profiles -> Colors | |
| // 3) Other Actions -> Save Profile as JSON | |
| // | |
| // To generate the applicable color settings and use them in VS Code: |
Because... ...Why Not!
This document explores the strategic use of random chance in GitHub Actions workflows. By introducing probabilistic execution paths, teams can simulate real-world unpredictability, optimize resource usage, and experiment with delivery strategies. This approach supports goals such as chaos engineering, canary releases, CI load management, A/B testing, observability validation, and developer engagement.
Whenever we change our templates we still have to use our build script and this can get annoying. Thankfully with webpack-dev-server and BrowserSync we can fix this:
npm i -D browser-sync browser-sync-webpack-plugin webpack-dev-server
BrowserSync will act like a proxy, waiting for webpack to do its thing and then reloading the browser for us.
Picking the right architecture = Picking the right battles + Managing trade-offs