About this IT guy

Technology makes more sense when you connect the layers.

Infrastructure depends on silicon.
AI depends on compute.
Compute depends on architecture, energy and economics.
And business decisions eventually shape the technology engineers have to build, operate and maintain.

This IT Guy explores those connections

The publication covers modern IT infrastructure, AI and compute, semiconductors, technology strategy and hands-on engineering.

The goal is simple: Go beyond announcements, specifications and marketing claims to understand how technology works, why it evolves, and what the consequences are for the people who build and operate it.

What we cover

Infrastructure

Datacenters, networking, storage, virtualization, cloud platforms, Kubernetes, security infrastructure and the systems that keep modern IT running.

AI & Compute

GPUs, CPUs, accelerators, machine learning, large language models, inference, training, distributed computing and the infrastructure required to operate modern AI workloads.

Silicon

Semiconductors, DRAM, HBM, NAND, foundries, advanced packaging, lithography and the supply chains behind modern computing

Business and Strategy

Technology companies, acquisitions, financial results, market dynamics and the strategic decisions that influence products, architectures and entire ecosystems.

Guides

Practical, reproducible tutorials for deploying, configuring, testing and understanding real systems,

From installing a server operating system to running an AI model on consumer hardware, the objective is to provide enough technical detail to actually build something.

How we works

Good technical analysis needs more than opinions.

Whenever possible, thisitguy.net relies on primary sources :

• Technical documentation
• Standards
• Scientific Publications
• Regulatory filings
• Annual reports
• Earnings releases and official company communications

Secondary sources are used to add context, compare interpretations and understand how technologies are being adopted in the real world.

When financial analysis meets engineering, both sides matter.

A product strategy cannot be understood only through architecture diagrams.

A balance sheet cannot explain why engineers adopt - or abandon - a technology.

The interesting part is often where the two meet.

No black boxes

Complexity is not an excuse for vagueness.

Articles and videos aim to explain the mechanisms behind a technology rather than simply describe the outcome.

That may mean going from a GPU architecture to memory bandwidth, from virtualization to corporate strategy, or from an acquisition announcement to several years of financial filings.

Sometime the answer is simple.

Sometime it requires going several layers deeper.

We prefer the second option when it matters.

Corrections

Technology changes quickly, and mistakes are possible.

If you find an error, an outdated reference of something that deserves additional context, please get in touch through the contact page.

Material corrections will be reflected in the relevant article whenever appropriate.

Follow thisitguy.net

New research, explainers and guides are published across :

YouTube · LinkedIn · TikTok · Facebook · thisitguy.net