For me it's not "overcomplication," it's strong interoperability with a workflow I like, specifically one that was kind of complicated to write once, but afterwards operates in a way such that I don't have to think at all.
I've been using this for years, so perhaps today there may be some voice or AI driven way to do this but -- first I add weekly events. And for one off events, I have a bash script that's like "whats the event?" then "what's the date/time" using standard linux date formatting, and returns an error and loops if wrong. (So e.g. "tomorrow" works, or "monday 4pm"
Then for retrieval, I can have it do notify prompts, and/or be a part of my bash prompt, and also throw up a nice HTML calendar.
Most of these tools are something you set once, write some scripts if it's a CLI, then forget about until someone tries to make a breaking change. Then you switch to the fork that maintains the old feature set.
I've been using this for years, so perhaps today there may be some voice or AI driven way to do this but -- first I add weekly events. And for one off events, I have a bash script that's like "whats the event?" then "what's the date/time" using standard linux date formatting, and returns an error and loops if wrong. (So e.g. "tomorrow" works, or "monday 4pm"
Then for retrieval, I can have it do notify prompts, and/or be a part of my bash prompt, and also throw up a nice HTML calendar.