Empty Space

Trust and independence are undermined by requests to how things are instead of what do you want. Analogous to giving set of operations to versus get this.  Telling someone how to do something is micromanaging instead of asking them for what you want. What instead of How, look to open

Stored procedures are made to destroy boundaries, but at least we have table functions now which at least give some modicum to respecting the data i.e. there are inputs and there are outputs instead of ref or out parameters. Use a table function with a cross apply instead of

Code rots as soon as you write it.  Code rots faster than wood and doesn't preserve its shape like a rusting metal like iron. People think that it is static and preserved because the text the wrote isn't changing, but that is wrong and misleading because

This is the list of things I would like to address and implement that there never seems to be time for because our agile process has no slack times defined. Why planned slack times are good http://www.solutionsiq.com/the-importance-of-slack-in-achieving-speed-and-quality/ * Typescript * .NET Core * .NET Core ServiceStack * .NET Core NancyFX

Anonymized Mapping Project X/Y -------------------------------------------------------------------------------- Thinking about this Project X/Project Y revision with respect to options and constraints over the past couple of hours and came up with this. First an alternate option not discussed for Project X/Project Y - Create a Universal Windows Application with Xamarin

Committing to Agile is a continuous process that spans every aspect of an organization.  If you do it piecemeal and inconsistently you will build up barriers and set yourself up for expectations failure. Agile and Executives [https://theitriskmanager.wordpress.com/2017/03/12/where-executives-and-agile-beliefs-diverge/]

Not possible.  Words mean things and actions have effects.  Stop forcing processes that are detrimental on people. Myth of scaling [https://michaelfeathers.silvrback.com/the-myth-of-scaling]

Creates a trigger that tracks all successful changes on a table and writes the time of last change while dynamically determining the calling table name. DROP TRIGGER [dbo].[Tracker] GO SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TRIGGER [dbo].[Tracker] ON [dbo].[TableToTrack] AFTER INSERT, UPDATE,

Extracted this from screenshot from another software developers at another companies thoughts. * Reliability investments create leverage over time, where-as firefighting is actually an act of regression. * A reliability investment means that some future problem class is eliminated, creating space to focus on creating value. * Every time energy is diverted towards

Directly from the Agile Manifesto [http://agilemanifesto.org/] * Individuals and interactions over processes - and tools * Working software over comprehensive documentation * Customer collaboration over contract negotiation * Responding to change over following a plan That is, while there is value in the items on the right, we value the items on

Company culture is the by-product of consistent behavior.  What you do always wins against what you intend to do. - Jason Fried -------------------------------------------------------------------------------- * Poor management practices * Lack of autonomy * Too much process, too many meetings -------------------------------------------------------------------------------- * People don’t leave companies, they leave managers * Skip level 1:1s * Multiple sign

Testable components of ReactJS and Redux Simple components should pass the props directly rather than compute from a global Redux state and that is what Redux is a global consolidated state.  Apportion the state you need as a large data structure at the root element and then send it to

* 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