Steve Coffman StevenACoffman

If you have several tools that are very closely related, you can make them easier to use, discover, and distribute by combining them into a single tool (and a single executable binary artifact).

If you’ve got a tool that’s sufficiently complex, you can reduce its complexity by making a set of subcommands. This is also useful for sharing stuff—global flags, help text, configuration, storage mechanisms.The above guidance doesn’t help you to decide when something is unrelated and should be separated, BTW.

It is worth comparing this advice to the Command Pattern from the “Gang of Four” “Design Patterns” book, where you encapsulate an an action or a request as an object that can be parameterized. Usually, in the Command Design Pattern the invoker doesn’t know anything about the implementation details of the command or it’s receiver, it just knows the command interface and its only responsibility is to invoke the command and optionally do some bookkeeping of what commands are possible and/or valid. There are

Random AST and SSA Helpers

	package main

	import (
	"fmt"
	"log"

	"context"

	"cloud.google.com/go/storage"

	package main

	import (
	"fmt"
	"io/ioutil"
	"log"

	"context"

	"cloud.google.com/go/storage"

	package main

	import (
	"fmt"
	)

	var (
	ones = []string{
	"zero", "one", "two", "three", "four",
	"five", "six", "seven", "eight", "nine",

	package main

	import (
	"fmt"
	"go/ast"
	"go/parser"
	"go/token"
	)

	func main() {

	// https://go.dev/play/p/CxJf4Jf9rDZ

	package main

	import (
	"fmt"
	"strings"
	)

	const ZZZZ = 18279 + 456975

Steve Coffman StevenACoffman

Notes:

Games:

	#Should be a job too :-D

	# With xargs (on all namespaces)
	kc get jobs -o=jsonpath='{range .items[?(@.status.conditions[0].type == "Failed")]}{.metadata.name}{"\t"}{.metadata.namespace}{"\n"}{end}' --all-namespaces \| \
	xargs -n2 sh -c 'kubectl delete jobs $0 --namespace=$1'

	# For loop (only in the current namespace)
	for i in $(kc get jobs -o=jsonpath='{range .items[?(@.status.conditions[0].type == "Failed")]}{.metadata.name}{"\n"}{end}');
	do kubectl delete jobs $i; done