This is a tiny content strategy framework focused on goals, messages, and branding. This is not a checklist. Use what you need and scrap the rest. Rewrite it or add to it. These topics should help you get to the bottom of things with clients and other people you work with.
Give me feedback on Twitter (@nicoleslaw) or by email ([email protected]).
Adrian -
I appreciate that you spent time in writing this post. I know I've been up until 2am writing similarly long ones as well. I will take responsibility for having what is likely an irrational response (I blame Twitter for that) to the term "NoOps", but I invite you to investigate why that might be. I'm certainly not the only one who feels this way, apparently, and thus far have decided this issue is easily the largest distraction in my field I've encountered in recent years. I have had the option to simply ignore my opposition to the term, and just let the chips fall where they may with how popular the term "NoOps" may or may not get. I have obviously not taken that option in the past, but I plan to in the future.
You're not an analyst saying "NoOps". Analysts are easy (for me) to ignore, because they're not practitioners. We have expectations of engineering maturity from practitioners in this field of web engineering, especially those we consider leaders. I don't have any expectations from analysts,
| # This is example contains the bare mininum to get nginx going with | |
| # Unicorn or Rainbows! servers. Generally these configuration settings | |
| # are applicable to other HTTP application servers (and not just Ruby | |
| # ones), so if you have one working well for proxying another app | |
| # server, feel free to continue using it. | |
| # | |
| # The only setting we feel strongly about is the fail_timeout=0 | |
| # directive in the "upstream" block. max_fails=0 also has the same | |
| # effect as fail_timeout=0 for current versions of nginx and may be | |
| # used in its place. |
| ;; Copyright (c) Alan Dipert. All rights reserved. | |
| ;; The use and distribution terms for this software are covered by the | |
| ;; Eclipse Public License 1.0 (http://opensource.org/licenses/eclipse-1.0.php) | |
| ;; By using this software in any fashion, you are agreeing to be bound by | |
| ;; the terms of this license. | |
| ;; You must not remove this notice, or any other, from this software. | |
| (ns alandipert.kahn | |
| (:require [clojure.set :refer [difference union intersection]])) |
| class Proc | |
| def <<(other) | |
| case other | |
| when Proc | |
| Proc.new do |*args| | |
| call(other.call(*args)) | |
| end | |
| else | |
| call(other) | |
| end |
| #!/usr/bin/env ruby -w | |
| ## Using ruby's standard OptionParser to get subcommand's in command line arguments | |
| ## Note you cannot do: opt.rb help command | |
| ## other options are commander, main, GLI, trollop... | |
| # run it as | |
| # ruby opt.rb --help | |
| # ruby opt.rb foo --help | |
| # ruby opt.rb foo -q | |
| # etc |
| module ParameterizedConcern | |
| def extended(mod = nil, &block) | |
| unless mod | |
| @extended_block = block | |
| return | |
| end | |
| mod.module_eval(&@extended_block) if @extended_block | |
| end |
This is a contest, open to programming languages from all nations, to write modular and extensible code to solve the following problem: Implement a service that can run queries on a database.
Sounds simple right? Wrong! A programmer without control over the source-code of that service must be able to later add enhancements such as statistics collecting, timeouts, memoization, and so forth. There are a few more requirements: