Also, Kanban was invented in the 40s as a process for automotive production lines. That’s why it aligns so well with maintenance and operations projects in IT. It’s ridiculous how more and more people claim it comes from software development and would not fit hardware projects, when that’s the core use case of the methodology.
1Password can’t fail that hard easily. They’ve done great write-ups to compare their architecture to that of LastPass. Long story short: it’s the secret key that protects you: https://blog.1password.com/what-the-secret-key-does/
Trouble with those tests is, that they become unreliable or even meaningless, when you have done then once before, let alone daily.
The original author of git flow begs to differ. But hindsight is always 20/20 https://nvie.com/posts/a-successful-git-branching-model/
If you use feature flags, don’t forget to remove them after some grace period. Almost everything bad about feature flags that you can read online is related to long-lived feature flags and all the dead code and complexity involved. Adding a feature flags without a commitment and plan to remove them (the flag, not the feature), is asking for trouble down the line.
You can implement public or semi public ledgers without Blockchain. That’s what banks are doing already by sending huge CSV files internally and externally. Blockchain is not a technology of zero trust. It’s close to the opposite. You trust a few peers and blindly trust everyone they trust. That way you trust a network that you know nothing about and if the network decides on a common truth that you are convinced is incorrect, there is nothing you can do about it. The consensus always wins and there is no single entity to complain to and get it fixed. This is great for making sure that many actors need to be bad actors in order to have the whole system fail. It’s bad if you don’t trust anyone and want to make sure that your standards are always observed. From a technology standpoint I love the concept of Blockchain. But use cases that are not forced are few and far apart. Too few for the amount of hype it receives.
Coffee seems to be a self enforcing meme at this point. It’s not unhealthy enough to have suffered the same fate as cigarettes. Which had pretty much the same jokes not too long ago.
Paperless -> Paperless-ng -> Paperless-ngx
Postgres handles NoSQL better than many dedicated NoSQL database management systems. I kept telling another team to at least evaluate it for that purpose - but they knew better and now they are stuck with managing the MongoDB stack because they are the only ones that use it. Postgres is able to do everything they use out of the box. It just doesn’t sound as fancy and hip.