The name comes from a joke. One friend, one offhand comment, and apparently a domain name I couldn’t let go of.
He was a network engineer. I was on the collaboration side, and to him in the most affectionate way possible that made me a leftclicker. As in, all I did was point and click my way through GUIs while the serious engineers were out there typing commands like adults.
I loved it immediately. Still do.
Because here’s the thing: collaboration engineering sounds like you’re just configuring softphones and booking conference rooms. In reality, most of it ran on Linux. You were in the CLI constantly, managing services, editing configs, troubleshooting SIP trunks, chasing down call routing issues, and occasionally getting into arguments with the network team about whose problem it actually was. (It was usually theirs.) And then you opened the GUI on top of all that.
We weren’t avoiding the command line. We were just also clicking things.
As my career moved into automation, that perspective turned out to matter more than I expected. It’s easy to build something powerful. It’s harder to build something people will actually use. And if your automation is only accessible to the person who wrote it, it’s not really automation, it’s just a script with an audience of one.
Adoption doesn’t happen because the code is elegant. It happens because the experience makes sense.
A CLI junky running your automation? Give them a CLI interface; flags, pipes, the works. They’ll love it. But hand that same tool to a general user and you’ve lost them in the first thirty seconds. They need a GUI, or a chatbot, or something that doesn’t require them to remember argument syntax. Same automation, different front door.
That’s the part that gets skipped. And it’s usually the reason good automation sits unused.
So the name fits better than my friend probably intended. Leftclicker.io built by someone who understands both sides of the screen.