This really goes to show that everyone's 'flow state' is different.
My inner dialogue is always chatty; that doesn't stop when I enter a flow state. It just becomes far more laser focused and far less distracted. LLMs help to maintain the flow because I'm able to use it to automate anything I don't care about (e.g. config files) and troubleshoot with me quickly to keep the flow going.
I don't know if "more convenient" would be the words I would use. Setup on this project is very easy, it has very straightforward instructions. Meanwhile, I did a quick 5 minute pressure test of what you suggested and found myself with more questions than answers. I am not saying one way is better than the other, I am just thinking that for those that don't breathe SSH/VPN/Wireguard/Terminal Emulators/etc.. this project is actually far easier to understand.
Also, funny enough on compatibility, but "Termux" is not on iOS, so it fails that basic check. But there's alternatives, of course. Just an observation.
For someone like me that is less versed in these things, could you explain why bootstrapping a language is a required check for taking a language seriously? My criteria is far less stringent (is it stable? is it popular enough? is the toolchain mature? etc..), so I wonder what I am missing here.
I am not sure if this considered an anti-pattern, but in one of my teams, we wrote a lightweight generic Secrets library with configurable/pluggable backends (such as AWS Secrets Manager). It had a configurable local cache, with per-parameter overrides to bypass the cache. It meant vendor specific fetch logic was in the pluggable backends, while the app and the secrets lib remained vendor neutral.
When we moved it to Vault, it was seamless. Just meant adding our Vault backend wrapper as a dependency and updating the config to use the Vault backend.
There's a bug when the target article is titled the same as the disambiguation page. Search for "Earthbound", and try clicking on the article for the video game. It'll bring you right back to the disambiguation page.
My inner dialogue is always chatty; that doesn't stop when I enter a flow state. It just becomes far more laser focused and far less distracted. LLMs help to maintain the flow because I'm able to use it to automate anything I don't care about (e.g. config files) and troubleshoot with me quickly to keep the flow going.