If it would be less trouble (because of customs and other external factors), and assuming it can help, maybe a phone keyboard can also be considered? An OTG cable plus a normal USB keyboard might also be a solution if portability is not a requirement.
While I gladly embrace the shift to solid state, I find the mechanical engineering in old electronic devices, cameras in particular, quite fascinating.
The name, monocle, also further misleads those expecting the physics topic. They actually have a nice logo with a lens and the lambda symbol which is often the symbol used for wavelength.
Opportunities that require big risks is also another factor. My academic acquaintances abroad may be doing well financially and travel-wise, but they all have to live their foreign bosses' ambitions despite being very bright people. It's far easier to take crazier entrepreneurial risks with the safety nets in one's own home-country.
Entrepreneurship sure may be difficult as a whole. However, some difficulties are not really necessary. For me, it's a matter of seeing the end goal and removing as much obstacles as possible to get there faster (optimizing for time). I see the need to have a proper job or chase funding as additional obstacles if you are abroad.
Having built both desktop-native and browser-based apps, I think there is an efficiency in doing the widget layouts textually via code/markup once you get over the learning curve. I believe Qt and wxWidgets also have automatic layout features, but doing this on top of C++ maybe makes the experience less smooth. So far form designers in Visual Studio require manual pixel layouting, which becomes tedious as the GUI evolves to be more complex. This is great for beginners as dragging and dropping controls is so easy to learn. But as soon as you have a dozen or so controls, you start to notice the time spent manually dragging/aligning/sizing that is absent in markup-based or procedurally generated GUIs that do the layout calculations for you.
mfc has resizable ui layouts called Dynamic layouts (since the 2015 update?), and for wxwidgets there is wxformbuilder. Most stuff for mfc can be set in the dialog builder wrt to resizing, or in code.
I cant remember doing manual pixel layouting ever, there are dialog base units or sth like this. People have been setting the ui to 120dpi from the 96dpi standard already decades ago. And the dialogs automatically readjusted without recompiling.
I also recently found out my mfc tools are per monitor high dpi aware without any interference from my side.
It gets worst when these users/students run to others when the AI generated code doesn't work. Or with colleagues who think they already "wrote" the initial essay then pass it for others to edit and contribute. In such cases it is usually better to rewrite from scratch and tell them their initial work is not useful at all and not worth spending time improving upon.
My personal/work files for which the physical media of origin no longer exists. Source codes, mine and of others that I care about. Compilers. Lots of books and Wikipedia.
Build/make something. Preferably something new to you and preferably on your own as much as possible (even if you're following someone else's instructions).
