Just me keeping track of what I did to get my Erlang CLI dev env working OK
This is built using Windows 10
- Windows 10 Fall Creators Edition
- Linux Subsystem for Windows + Ubuntu Xenial
- Rebar3
// Place your key bindings in this file to overwrite the defaults | |
[ | |
{ | |
"key": "cmd+t cmd+t", | |
"command": "workbench.action.tasks.runTask", | |
"args": "Run All Tests" | |
}, | |
{ | |
"key": "f5", | |
"command": "workbench.action.tasks.runTask", |
This is a transformation of Adrian Colyer's Checklist to turn it into a working model for a cloud transformation. The assumption is that the original checklist can suffice for any services that are deployed on the build pipeline, but the question to answer here is about how the environment is provisioned, deployed, monitored and governed in such a way as to fit the architecture implicit in the service checklist.
kubectl run -i --tty busybox --image=busybox --restart=Never -- sh
A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."
// Use delegates to provide a nice clean name for complex func types | |
public delegate bool FileExists(string path); | |
public delegate byte[] ReadContent(string path); | |
public delegate void WriteContent(string path, byte[] content); | |
// this is the original function looked at, which contains two accesses of the filesystem, | |
// which had been intercepted through the use of System.IO.Abstractions | |
public byte[] GetContent(string path) | |
{ | |
if (path == null) { throw new ArgumentNullException(nameof(path)); } |
I hereby claim:
To claim this, I am signing this object: