IanTwenty

Wow that’s bad. The original idea of standing up, I understand, was to keep the meeting short through physical discomfort and only speak of blockers to progress or ask for help. It is not meant to report status, which can make people feel like they have to continually justify themselves and their work.

Errors in command substitution e.g. $(cat file) are ignored by ‘set -e’, one example of its confusing nature. It does not force you to all handle errors, just some errors and which ones depends on the code you write.

https://mywiki.wooledge.org/BashPitfalls#set_-euo_pipefail

Hoping this tool lives up to its own hype:

PyInfra—where your infrastructure is actually code. Real Python. With loops that don’t require learning a DSL. With functions that are… wait for it… actual functions. With error handling that doesn’t involve praying to the YAML gods

https://fosdem.org/2026/schedule/event/VEQTLH-infrastructure-as-python/

Performance:

https://docs.pyinfra.com/en/3.x/performance.html

This is overkill but reminds me of

https://en.wikipedia.org/wiki/Homomorphic_encryption

…where operations (including search) can be carried out on data that remains encrypted throughout.

Sounds like you only need encryption at rest however. So can you keep tickets in memory for searching perhaps?