"From the beginning I made some core decisions that the company has had to stick to, for better or worse, these past four years. This post will list some of the major decisions made and if I endorse them for your startup, or if I regret them and advise you to pick something else."
Mastodon Source 🐘
The author calls out a pain point I've encountered and also invested in addressing in multiple teams:
"With GitOps we’ve had to invest in tooling to help people answer questions like “I did a commit: why isn’t it deployed yet”."
- Product always wants to know when a feature will be available
- Dev always wants to know what's running when a test a test fails
- Ops always wants to know what version of code/artifact is running during an incident.
Mastodon Source 🐘
- Security always wants to know if there is CVE risk
There are many stakeholders who need to reverse lookup from an `instance-id`, not only a `class`, yet so much context is lost during CI/CD.
Visualizing the code lineage multiverse is a gnarly problem beyond just the number of transformations & packaging formats.
Mastodon Source 🐘
At a mundane level, we will only know when things are better when we are able to signify the things. Can you step in the same river twice and whatnot.