Who Builds Toolsque

Toolsque is a small, independent site. Three people stand behind it: one builds and tests the tools, one writes the WiFi and network guides, and one reviews everything before it goes live. Here is who they are and what each of them does.

Zeeshan

Founder, builds and tests the tools

Software engineer with 17 years of experience. Zeeshan writes the code behind every Toolsque tool: the QR code and barcode readers, the blurry and damaged code repair, the WiFi and eSIM decoders and the free generators.

Each reader is tested on real photos and screenshots from Android phones and iPhones before it goes live, and every tool runs in your browser, so the images you scan are never uploaded.

Toolsque on GitHub →

Najeeb ur Rehman

Reviewer

Director at GoPro IT, which provides white-label field IT services for MSPs and OEMs across the US, UK and EU. He has more than 10 years in IT operations, managed services and service delivery.

Najeeb reviews Toolsque's tools and guides for accuracy and for how they hold up in real IT work. Based in the UK.

Najeeb on LinkedIn →

Ali Lone

Writer, WiFi and network guides

Director of Global Partner Management at GoPro IT, based in London. Before that he spent over 10 years in hands-on IT: network technician, network administrator at the Virtual University of Pakistan, and L3 systems and virtualisation engineer in Saudi Arabia, running servers, firewalls, VPNs and WiFi networks.

BS in Computer Engineering (Data Communications and Networks) from COMSATS. VMware VCP6-DCV and Cisco CCNA certified. Ali writes and checks the WiFi guides on Toolsque.

Ali on LinkedIn →

How a tool gets onto Toolsque

  1. We look at what people actually search for when a QR code or barcode gives them trouble, and check what already ranks for it.
  2. Zeeshan builds the tool so it runs in the browser, with nothing uploaded.
  3. It is tested against a set of real codes: sharp, blurry, inverted, damaged and screenshot images, on Android and iPhone.
  4. Najeeb reviews the tool and its guide before release.
  5. Every tool keeps a dated changelog and a bug report address, so fixes are visible.

The full test method is on how we build and test. To report a problem or suggest a tool, use the contact page.