signaru

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.

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.

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.

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.

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).

This also applies when calculating losses from paying third party services.

I think there are evolutionary arguments for it, besides avoiding sickness:

* Generally, the opposite sex is physically attracted to fit individuals.

* Finding food prior to agriculture or paying others.

* As for sugar, I'm not so sure, but maybe the plant's benefits also have to be considered (e.g. propagating seeds through fruits).

Maybe cheating a bit if we allow compilers to run on more powerful machines, different from where the program will run. It could be possible to utilize more modern or "ergonomic" programming languages or rely on convenient libraries (assuming they are also efficiently coded). Programming languages in the 80s would not be as fun as what we have today partly because they were designed for limited hardware and partly because there's not a lot of other languages to learn from yet. IDEs, tooling and libraries have also come a long way.

Knowledge access is also something that has improved significantly. Programmers back then may not have had all the information that could have improved their work.