* When a problem occurs varying data structures is easier than varying logic workflow structures. * Data Transfer Objects should be coarse grained and contain no logic. * Immutable data objects promote isolation, predictability, and readability. * Logic structures should avoid inheritance as much as possible and use a composition workflow logic structure.  The

# Place in /etc/systemd/system/ghost.service [Unit] Description=Ghost blog siliconheaven.info After=network.target [Service] Type=simple PIDFile=/run/ghost-siliconheaven.info.pid # This is the directory you installed Ghost to WorkingDirectory=/var/www/ghost/ User=ghost Group=ghost ExecStart=/usr/bin/npm start --production ExecStop=/usr/bin/npm

Guiding principle. The opposite approach started the XML wars from the turn of the century.

Column orient a database view because customers do not understand row data and their processes are brittle and change resistant Garbage specification that is allowed to continue because of inertia.  You must actively fight against technical debt and technical apathy or be confined to the limits of others abilities and

Attach raw HTTP handler at the AppHost level to serve static files from a folder or folders RawHttpHandlers.Add(req => { if (!allowedPaths.Any(z => req.PathInfo.ToLowerInvariant().StartsWith(z.ToLowerInvariant()))) { return null; } if (!req.HttpMethod.EqualsIgnoreCase("GET")) { return null; } // Send back static file handler return new

http://techfieldday.com/appearance/docker-presents-at-tech-field-day-extra-at-vmworld-us-2016/ Applications that exist in a Docker container are * Isolated * Scaleable * Complete in configuration and setup * Automated * Docker swarms are * Scaleable * Load balanced * Clustered * Fault tolerant All of the tasks, work, and architecture that previously was manually managed by disparate groups and individuals is automated in

Code is difficult to write, easy to break, and constantly changing.  To help developers concentrate on the code tasks at hand we should strive for the following goals * Code is readable and verifiable with an emphasis on maintenance and clarity for other developers. * Developers reduce technical debt whenever possible * Make