Usama Sohail

Founder of Check Can I Run It | Developer and Technical Content Writer

I’m Usama Sohail, a developer and technical content writer with more than ten years of experience building websites, developing online tools, researching technology, and writing technical content for general readers.

I founded Check Can I Run It to give PC gamers a straightforward way to find a game’s recommended system requirements. A visitor selects a title and receives the recommended hardware and software requirements, along with information about the game. The checker does not ask visitors to enter their PC specifications and does not scan or benchmark their computers.

My work combines development, technical research, and writing. Development helps me understand how information should be structured and presented through a tool. Technical writing allows me to explain what that information means without assuming that every reader already understands processors, graphics cards, memory, or gaming performance.

Development and Technical Background

I began working with websites more than ten years ago. My work expanded from website development into specialised tools, structured technical content, and projects focused on helping people understand technical information before making a decision. Much of my current work centres on PC hardware and gaming. The subjects I regularly research and write about include:

  • PC game system requirements;
  • Processors and CPU performance;
  • Graphics cards and GPU performance;
  • VRAM and system memory;
  • SSDs and storage;
  • Power supplies;
  • Cooling and thermal behaviour;
  • Displays and refresh rates;
  • PC component compatibility;
  • Laptop and desktop hardware;
  • Graphics settings and resolution;
  • Ray tracing and path tracing;
  • DLSS, FSR, and XeSS;
  • Frame generation;
  • Drivers and graphics APIs; and
  • Gaming performance limitations.

My development work also covers the technical side of online tools, including data organisation, interface behaviour, code integration, responsive design, and presenting technical results in a form that visitors can understand.

My Work in PC Gaming and Hardware

PC gaming performance cannot be judged from a component name alone. A graphics card needs to be considered alongside its architecture, VRAM, supported features, resolution, graphics settings, and the workload created by the game. CPU performance depends on more than a Core i5, Core i7, Ryzen 5, or Ryzen 7 label. The exact model, generation, architecture, cache, clock behaviour, power limits, and game workload can change the comparison.

Laptop hardware requires another level of care because components with similar names can operate at different power and thermal limits. I apply this context when researching system requirements and writing about hardware. The objective is to explain the specification accurately rather than make a conclusion from a model name or a single benchmark number.

How I Research Game Requirements

For Check Can I Run It, I give priority to information published by the game developer, publisher, official game website, official support documentation, or authorised digital store where suitable requirement information is available.

I check the game edition because an original release, remaster, enhanced edition, expansion, or later PC version can have different hardware requirements.

I also consider whether the information belongs to the current game version. A major update can change storage requirements, operating-system support, graphics features, or other technical conditions.

The checker focuses on the recommended system requirements available for the selected game. It does not convert those requirements into a claim that every computer with similar hardware will achieve the same FPS.

If an official source states a resolution, graphics preset, frame-rate target, ray-tracing configuration, or another performance condition, that context matters. If the source does not provide a performance target, I do not present an unsupported target as confirmed information.

How I Research Technical Content

My research process depends on the subject being covered. Sources may include developer and publisher documentation, hardware-manufacturer specifications, driver documentation, technical standards, game patch notes, benchmark results, product documentation, and other evidence relevant to the question.

I consider the conditions behind a technical result before using it. A benchmark at 1080p cannot automatically answer the same performance question at 4K. A laptop GPU should not be treated as identical to a desktop card simply because their names are related. A benchmark produced with one game version may also become less useful after a substantial patch.

When sources disagree, I compare what each source actually measured or published, when it was published, and whether the hardware and software conditions are comparable. This distinction helps separate a confirmed specification from an interpretation of what that specification may mean.

Testing and Source Attribution

I distinguish my own testing from testing performed by another person, publication, benchmark provider, or hardware company. When I conduct a test myself, I can use that experience to explain behaviour that a specification sheet does not show. The relevant hardware, settings, or testing conditions should be identified when they materially affect the result.

When I have not personally tested a game or component, I do not describe third-party measurements as my own hands-on findings. If a performance figure comes from an external benchmark source, I treat it as external evidence and consider the methodology and test conditions before drawing a broader conclusion.

This distinction matters because an FPS figure, benchmark score, temperature, or power measurement has little meaning when the conditions behind it are missing.

Research and Automation Tools

Research and automation tools can assist with source discovery, organising information, comparing terminology, or identifying a technical question that needs further investigation.

They do not determine what I ultimately publish. I review the relevant evidence, check important factual claims against appropriate sources, add the technical context needed to explain the subject, and take responsibility for the final content published under my name.

Repeated information is not automatically reliable. Several pages can repeat the same incorrect specification because they originated from the same secondary source. I therefore consider where a claim came from rather than relying on repetition as proof.

My Writing Approach

I write for the person who needs to understand what a technical specification means and what should be checked next. That means separating facts from assumptions, explaining why a component or requirement matters, and identifying conditions that can change the conclusion.

I avoid presenting an uncertain estimate as a confirmed specification. I also avoid treating a benchmark number as universal when the result depends on resolution, settings, test hardware, game version, or another variable. The aim is to make technical information understandable without removing the details that make it accurate.

Other Work

I am also the founder of The PC Bottleneck Calculator, a separate project focused on PC hardware, component balance, compatibility, performance, and upgrade research.

My work there covers processors, graphics cards, RAM, storage, displays, power supplies, cooling, and other areas connected with PC building and gaming performance.

My author profile and published work provide another reference for my work in the PC hardware niche. The two websites serve different purposes. The PC Bottleneck Calculator focuses on relationships between PC components and hardware decisions, while Check Can I Run It focuses on games and the recommended PC requirements published for them.

Editorial Responsibility

I take responsibility for content published under my name. Game requirements, drivers, hardware specifications, software support, and benchmark evidence can change. When reliable new information materially changes an article or game entry, I review the existing information and update it where necessary.

I also welcome evidence-based corrections. If you find an incorrect game requirement, outdated source, factual error, or statement that needs clarification, send the relevant page address and supporting evidence through the Contact Us page. I will review the report and correct the content when the evidence supports the change.

Contact

If you have a question, correction request, or concern about this page, please contact us through our Contact Us page or email us directly at editor@checkcanirunit.com.