4 ms·

Your comment on the device being dev friendly and the fact that you wrote your own utilities is really making me consider to preorder RM2. I saw all these comme

Your comment on the device being dev friendly and the fact that you wrote your own utilities is really making me consider to preorder RM2. I saw all these comments and wish I can somehow integrate my own workflow into it.

nicoburns 7y ago
Apparently the CTO is a KDE dev, so it's properly open. Has definitely made me very interested in one too.
jonahbenton 7y ago
Yeah, regarding workflow, I commented elsewhere but despite being a preorder of the RM1, I failed to establish a good "rapport" with the device when I first got it (late in 2018), and basically set it aside for a year until suddenly late last year, struggling with my paper workflow, a switch was flipped and I saw how I could adopt it, and I did, and now I love it. The software had improved dramatically- they seem to be doing a good to exceptional job at getting incremental features out on a regular tempo without breakage, no simple task- but I think a certain amount of "hammock-time" plus increased awareness of non-digital pain points was necessary for a new perspective to flip into place. (This is re: seemingly small things like using distinct per day notebooks and per week folders, rather than a single monolithic notebook with paper-like day headings etc) And my workflow is still limited- I am not using the writing recognition at all as yet- and there are plenty of use cases I come up constantly that it doesn't address- smart task lists, various kinds of copy paste, maps (!!!). If one has any kind of paper-based or digital habits adopting the device will be a challenge and involve frustration until it clicks, and probably even after. But I have confidence both in the device's trajectory and moreover in the ergonomics of a community developer's engagement with the org. There is a lot of open space for patient, flexible developers to build cool stuff in. Cheers.

nicoburns 7y ago

Apparently the CTO is a KDE dev, so it's properly open. Has definitely made me very interested in one too.

jonahbenton 7y ago

Yeah, regarding workflow, I commented elsewhere but despite being a preorder of the RM1, I failed to establish a good "rapport" with the device when I first got it (late in 2018), and basically set it aside for a year until suddenly late last year, struggling with my paper workflow, a switch was flipped and I saw how I could adopt it, and I did, and now I love it. The software had improved dramatically- they seem to be doing a good to exceptional job at getting incremental features out on a regular tempo without breakage, no simple task- but I think a certain amount of "hammock-time" plus increased awareness of non-digital pain points was necessary for a new perspective to flip into place. (This is re: seemingly small things like using distinct per day notebooks and per week folders, rather than a single monolithic notebook with paper-like day headings etc) And my workflow is still limited- I am not using the writing recognition at all as yet- and there are plenty of use cases I come up constantly that it doesn't address- smart task lists, various kinds of copy paste, maps (!!!). If one has any kind of paper-based or digital habits adopting the device will be a challenge and involve frustration until it clicks, and probably even after. But I have confidence both in the device's trajectory and moreover in the ergonomics of a community developer's engagement with the org. There is a lot of open space for patient, flexible developers to build cool stuff in. Cheers.