1. root
2. tools
3. software

§ What?

These are the tools I use and patterns I’ve observed or practiced.

§ Why?

Compound Interest is the champion of this narrative, as in any good story.

By investing in tools, we invest in the derivative of development velocity: we exchange learning hours for 2% greater efficiency, and benefit each remaining workday.

I like software, so I’ll probably do it forever, which makes this a good investment!

§ Tools

Eventually, each of them should have a page.

• the text manipulators:
  • the one and only vim
  • the GNU-coreutils gang (awk, sed, grep and friends)
• environment:
  • shell
  • chroot jails, systemd services; docker if needs be
• dev tooling:
  • build tools (make/pants/bazel/buck)
  • prometheus
  • vault, consul
  • nginx
  • gRPC/protobufs
• languages:
  • python
    • SQLAlchemy+flask, django, and friends
  • go
    • CLI tools with the regular spf13 goodies
  • javascript (aka react…)
• puffy things in the sky:
  • TerraForm
  • DigitalOcean, AWS, GCP
  • CloudFlare (CDN)
• databases, of one shape or another:
  • postgres
  • sqlite3
  • kafka
  • git

§ Ideas / Patterns

I have observed these concepts or meta-tools to be “portable” across tasks and tools.

You might find them useful as a foundation, to grow your own skills on, or perhaps as frameworks for reanalyzing or integrating the skills you already possess.

• bitemporal¹ data
• 12-factor apps
• using the right tool at the right time
• what they call UNIX-philosophy.
• domain-driven-design, bounded contexts, and Rob Pike’s 5th Rule
• service-oriented-architecture, deployed continuously from a monorepo
• ship of Theseus-style rewrites
• technical writing²
• Law of Demeter
• Principle of Least Astonishment