Remote Troubleshooting
I listed the methods one by one. Troubleshooting over the phone often runs up against a lack of shared vocabulary, yielding potentially random results.
Providing a list of instructions to someone who lacks the necessary background is a gamble, and remote desktop support is much the same, especially when a PC gets stuck in a boot loop or loses network connectivity.
Given all the situations I had already encountered and the known hurdles involved, I realized it would be necessary to adopt new methods, even if it meant building them upon existing ones to broaden the realm of possibilities.
What Already Existed and What We Knew
- command lines in the terminal to perform all sorts of tasks
- users’ looks of incomprehension when seeing us type in the terminal
- CD-ROMs, DVDs, and USB drives prepared to run Linux in live demo mode
- online documentation (which is unavailable when the only PC in the house is broken)
Finally, I knew that many Linux applications are actually just command-line tools wrapped in graphical user interfaces.
A First Draft
Shortly after conceiving the idea, an acquaintance of mine with no technical skills agreed to read my initial draft of the documentation and share her thoughts.
During our subsequent discussion, she raised an objection regarding parts of the document that recommended calling a repair technician if a user hit an absolute roadblock. What would be the point of buying the tool only to end up at a repair shop anyway?
Not for “Everyone”
This remark completely challenged my initial perspective. I had to rethink the problem and look at it from a different angle.
After all, what is the point of targeting the general public as a whole, only to risk having a large number of isolated individuals fail when facing the machine?
It wasn’t just about troubleshooting for the “lost user.” There was also another phenomenon driving computer waste: a lack of familiarity with free software systems and an unawareness of the potential PCs hold through RAM upgrades and hardware swaps.
To scale up the rescue of older, still-functional computers, other channels needed to be found.
A Second Path Discarded
A few years later, in 2024, I spoke with several refurbishing companies across various regions to learn about their organizational models and workflows.
I quickly realized that very few of them use free software, and that they rely on highly rigid processes using institutional proprietary tools to test and sort the hardware they recover.
Consequently, they generally weren’t my target audience either.
The right path, therefore, was neither the isolated individual nor the established professional outfit with a locked-in operational model.
Other Avenues
Alongside established refurbishing companies with their set methods, many other types of organizations exist.
For these groups, a semi-artisanal approach combining free software, physical documentation, and remote support can be an appealing fit.
This method can find a natural home among IT technicians within businesses, associations, community education groups, clubs, and beyond.