Schema-less is a bit wrong term, since you always end up with one but, indeed, schema-on-read vs schema-on-write discussion for individual use cases is far from a settled thing, even though the zeitgeist is that schema-on-write won sometime in the 70s.
You say "prototyping", but I would generalize that to "faster evolving" in the long term. Of course, not without tradeoffs.
I personally have zero issues writing a custom marshaller when needed for any the schema-less document collections I have. Constraints your application has on the data are a superset of db schema anyways.
Just to add to sibling comments, one killer feature for me is ChangeStreams[1]. It's miles ahead of what Postgres[2] offers, and it enables really interesting use cases. Some of my services built around ChangeStreams end up not doing a single query to the DB. Data is right there in the program memory, indexed how I need it to be, and program is immediately reactive to any changes in the DB.
OpenResty with Redis on the same system - both Lua-powered - is a god-like power.
Ability to do basically control and rewrite all your ingress AND egress and have some state via Redis over UNIX sockets.
What's not to love? After all, it's what powers the bulk of internet.
Granted, it sounds dreamier than it is, since a lot of the contraptions you could come up with might be better placed at application layer. But having operational ability to do these things ad-hoc, security advantages of manipulating at your own infra edge or performance boosts, sure does come in handy!
Safari for general browsing (and default) because it's the most energy efficient one.
Firefox for work. The best implementation of pinned tabs. Shame it's a resource hog.
Chrome for reference and research type stuff. No reason why Chrome, I just want that separate from other contexts.
Chrome Canary for development. Still a Chrome, the best browser for development, but I get to separate all the reference stuff nicely from actual Chrome
Brave for streaming, because it's still a Chrome (so supports all the things) and blocks video ads really well.
Tor for... nice try, FBI. :)
I set up iTerm to open up reference type links I care about in Chrome, and all the other ones in Safari.
Boolean capabilities of meter per every entry? Shouldn't impact size that much, easy to index. As a bonus, you can track failure of a sensor per each meter, and know when it first failed.
> What do you mean by using the key cluster module? I don't have it, but how does that help you when you need to use a laptop?
Well, I put a lot of mappings in the cluster module (tmux prefix, tmux macros, another alt, still playing with what's optimal there), but idea is to focus onto the cluster module what'll not be available on common/laptop keyboard so when you do have to use it, your muscle memory won't press the wrong buttons, since they aren't there. I don't think it completely removes the issue of muscle memory and changing keyboard, but for me it certainly goes a long way.
Similar thing with trackpoint module, when I use trackpad, my hand still starts moving in right direction and prepping a finger to move a cursor.
As a result of those two things, I really rarely experience dissonance using my different keyboards. The only thing I do notice is how it's terrible to use non-split, so I just try not to do it as often as I can.
Just keep both network interfaces fired up, and sort them by priority in Network preferences panel (I assume ethernet, then wifi for you use case). Then you can forget about everything and do work, tethered or not.