I broke my wrist a month ago which prompted me to follow through on thoughts I'd been having for about 6 months about switching to a split ergonomic keyboard (I landed on the Kinesis 360 Pro) and a different keyboard layout (Colemak-DH) to help with RSI I get while programming.
I've got a little bit of mobility back in my wrist now (enough to type on a standard layout keyboard), so I gave the new split keyboard a try, and the switch was less than smooth to say the least. I looked online for different resources to learn mainly just the Colemak layout, and while each had their strengths, they didn't all do what I wanted.
To that end, and because I don't have the time or wrist at the moment, I vibe coded a desktop program that merges aspects of MonkeyType, Keyzen-Colemak and Colemak Academy. Mainly to give myself a tool to learn with, but also to see how useful vibe coding something from scratch like this is. So far I've been impressed with how far it got on the first go. Only a few times have I needed to guide it to fix behaviors, but most of my time has been spent extending the program in ways that make it more useful to me.
Once I've got the ability to, I might consider giving a rewrite of this tool a go by my own hands. I haven't looked at the code it's produced, but I'm sure there will be aspects of it that I would prefer be done differently.
I use surname.id for my domain. A main concern for me (and apparently others in this thread) was making sure that when I had to dictate the email over the phone that it wasn't confusing to the person on the other end.
Beyond that, I just host my email with Proton which has been a really pleasant experience.
I largely prefer an 80 column limit. On my external monitors with no file tree open, I perhaps could utilise more columns comfortably, but that really falls apart if I need to work on my laptop's screen.
The side effect of this that I don't particularly love is having to split a function's arguments on to multiple lines. Usually if I'm at that point though, I'll probably end up having to split those arguments up event at a ~100 character column limit.
To me, splitting the arguments is the preferable of the two situations. I always want to be able to see the whole line.
Very cool project! The company I work for is building a similar sat/cell GPS tracker for civil aviation. In fact we're using the same GPS and Iridium modules.
The costs for satellite SBD messages is definitely eye-watering though. Our device transmits position data every 2 minutes while relying on satellite connections, which we definitely notice the costs of during development. We'd like to look at other providers, but for various reasons (excluding costs) they end up being less ideal than Iridium.
I've got a little bit of mobility back in my wrist now (enough to type on a standard layout keyboard), so I gave the new split keyboard a try, and the switch was less than smooth to say the least. I looked online for different resources to learn mainly just the Colemak layout, and while each had their strengths, they didn't all do what I wanted.
To that end, and because I don't have the time or wrist at the moment, I vibe coded a desktop program that merges aspects of MonkeyType, Keyzen-Colemak and Colemak Academy. Mainly to give myself a tool to learn with, but also to see how useful vibe coding something from scratch like this is. So far I've been impressed with how far it got on the first go. Only a few times have I needed to guide it to fix behaviors, but most of my time has been spent extending the program in ways that make it more useful to me.
Once I've got the ability to, I might consider giving a rewrite of this tool a go by my own hands. I haven't looked at the code it's produced, but I'm sure there will be aspects of it that I would prefer be done differently.