szigand

Many years ago, as a former LogMeIn developer, starting my own remote desktop system from scratch seemed like an interesting idea and a good challenge, especially since there were more and more complaints about the existing ones. I saw no point in developing yet another identical system, but rethinking what I could, putting in new ideas, and polishing every detail with proper implementation - while respecting future users' time, nerves, and private data - seemed like a good task. It should just do its job simply, cleanly, and unnoticed as it should: removing distance, making remote work easier and a better experience, and simplifying connections while taking care of security. For now, this is what came out of it. This is just a first incarnation of the engine; many kinds of products can be born from this.

But meanwhile we learned that anything can be analyzed, understood, and fixed. Mainly because no one else was going to do it for us.

I always think back to my grandmother in the '90s. When her old black-and-white TV stopped working, we bought her a new color TV with a remote control. A few weeks later I saw that she had taped over the buttons, leaving only the power button exposed so she wouldn't mess anything up accidentally. I've been programming for 40 years, but even I struggle to grasp sometimes what goes where and why - so what is someone with zero coding background supposed to make of it? I sometimes talk about tech stuff - internet, cookies, security - with my hairdresser, and she just listens with wide eyes. I'm convinced most people have no idea what they're actually doing with their devices, and that's on us developers. It's our job to tailor systems to users by serving them with our knowledge, not confusing them with it. I doubt anyone wants to mess with the ECU settings on their car's dashboard - they just want to press the gas pedal, because that actually makes sense.