My professional career covers 10 years of experience in infrastructure and IT operations, currently as Site Reliability Engineering team lead at Castor. I have managed various teams across multiple companies, with my sweet spot appearing to be the growing of small- to medium-sized teams responsible for managing software infrastructure, especially in regulated and safety-critical environments.
With today's release of obsidian-export I'm switching from Semantic Versioning (SemVer) to Calendar Versioning (CalVer). This post explains the reasons behind this decision.
Obsidian-export is a Rust libary and CLI program to export an Obsidian vault to regular Markdown.
Requires https://crates.io/crates/cargo-sweep Clean all build files older than 7 days: cargo sweep -r -t 7 ~/ Clean all build files not made by any of the currently installed (by Rustup) compilers: cargo sweep -r -i ~/
After working through “the book” on the Rust programming language and getting started with the first non-trivial, real-world application I found myself faced with a question I didn’t yet feel well-equipped to handle: “How should you structure error handling in a mature rust application?”