In the world of cloud computing, usage-based billing is a pricing model where customers are charged based on their usage of a service. I quite like this model because it's fair. You pay for what you use, no more, no less. Let's explore this with a practical example.
Writing CLIs in Go is great, but there's one annoyance with the stdlib flag package:
flags must be defined before any positional arguments.
For example, if you have a --debug flag, you can't use it after a positional argument, it'll be
treated as a 2nd positional argument.
buf commandsThe buf CLI is a multipurpose tool for working with Protocol Buffers. The core
features include linting, formatting, breaking change detection, code generation, dependency
management, etc.
But the goal of this post is to highlight some of the lesser-known commands I've personally found
useful. Emphasis on personally. This is an evolving post of the lesser-known buf commands and
notes on how I use them.
Native blog support recently landed in Material for MkDocs
. This is huge, because technical documentation + blog can co-exist in the same place and
actually look nice!
Kudos to Martin (@squidfunk on ) for the hard work and dedication to the project. I've been following the project for a while and it's been a pleasure to watch it grow. I've used my fair share of documentation frameworks and tools, but I keep coming back to this one because...
Originally published on Medium. Cross posted here for posterity.
Nothing technical here, just an opinion on an alternative CLI (command line interface) framework for Go developers.
This will create the directory myproject and clone the repository into it.
Squash all the commits between your current HEAD and origin/main into a single new commit.
https://www.git-tower.com/learn/git/faq/git-rename-master-to-main
git branch -m master main
git push -u origin main
## May need to switch default branch in the UI, or use the gh CLI
gh repo edit owner/repo --default-branch main
git push origin --delete master
How to update a fork to have the same branches/tags as upstream repository?
# Set up the upstream remote for your forked repository:
git remote add upstream https://github.com/owner/repo
# Verify the remote with:
git remote -v
# Fetch latest tags from the upstream repository:
git fetch --tags upstream
# Push all tags from local repository to the forked repository:
Run git push --tags origin
Here's a simple script I use to upgrade Go on my macOS machine to the default location
/usr/local/go. It gets the job done.
Updates all direct dependencies of the current Go module to their latest versions.
This can be used instead of go get -u ./..., which updates all dependencies, including transitive
dependencies. The latter may not always be desirable.
Checks for and applies all available updates to module's dependencies.
The sort -V command is a version of the sort utility that performs version number sorting. It
understands the logical order of version numbers, which may not always correspond to alphabetical or
numerical order.
Example:
Regular sort:
But sort -V would correctly order them as:
This is because sort -V understands that in version numbers, 1.2 comes before 1.10.
# Lists all module dependencies (excluding the main module) by skipping the first line.
# For each dependency, explains why it's needed in the module.
go mod why -m $(go list -m all | tail -n +2)
This can be particularly useful when:
Identify which direct dependencies are pulling in various indirect dependencies.
Go's interfaces are brilliant. It's not immediately apparent and at first can be confusing, but after a while its brilliance shines through.
TL;DR - if a concrete type has the necessary behavior (methods) to satisfy an interface, it can implicitly implement that interface.