@thinkerqaq

ThinkerQAQ

@thinkerqaqJoined October 2026

Backend & Infrastructure Engineer | Go, Distributed Systems, Concurrency & AI Engineering

About

I'm a backend and infrastructure engineer focused on distributed systems, concurrency, Go, and developer tools. I write technical deep dives that connect first principles with practical implementation, including my Concurrency Programming series. Technical blog: https://thinkerqaq.com/en/ GitHub: https://github.com/ThinkerQAQ

Available for

Open to remote software engineering opportunities, open-source collaborations, and technical discussions. Areas of interest: - Backend & Platform Engineering - Distributed Systems & Infrastructure - Developer Tools & Open Source - AI Engineering & Infrastructure Happy to connect with engineers and teams working on interesting technical challenges.

ThinkerQAQ's blogs

ThinkerQAQthinkerqaq.hashnode.dev6 posts

Concurrency Programming (4): How Mutexes Are Implemented — From Runtime to CPU

Table of Contents 0. What Does This Article Answer Next? 1. How Does HotSpot Implement synchronized? 1.1 Layers 1.2 End-to-End Implementation Path for synchronized 1.3 Guarantees at the Runtime / Lan

1d ago · 11 min readthinkerqaq.hashnode.dev

Concurrency Programming (3): Mutexes — Atomicity, Visibility, and Ordering at the Language Level

Table of Contents 0. Continue from the Previous Article 1. What Guarantees Do the Lock Rules in Each Language Provide? 1.1 Java: synchronized and Monitors 1.2 Go: sync.Mutex 1.3 CPython: threading.Lo

2d ago · 7 min readthinkerqaq.hashnode.dev

Concurrency Programming (2): Language Memory Models — Rules Programmers Can Rely On

Table of Contents 0. Continue from the Previous Article 1. Why Does the Language Need a Memory Model Layer? 2. How Should Programmers Understand Memory Model Rules? 2.1 Java Memory Model 2.2 Go Memor

5d ago · 13 min readthinkerqaq.hashnode.dev

Concurrency Programming (1.5): The Operating System Layer — Threads, Schedulers, and Runtime Scheduling

Table of Contents 0. From Language-Level Execution Units to the CPU 1. How Does Java Schedule Threads? 1.1 From Platform Threads to Virtual Threads 1.1.1 The Simplest Model: One Java Thread per OS Th

6d ago · 31 min readthinkerqaq.hashnode.dev

Concurrency Programming (1): Start with the Hardware — From count++ to Atomicity, Visibility, and Ordering

Table of Contents 1. Start with the von Neumann Architecture 2. What Does count++ Become? 3. Why Do We Need Caches? 4. Concurrency on One Core: Why Can count++ Lose an Update? 5. From One Core to Mul

Oct 19 · 14 min readthinkerqaq.hashnode.dev

@thinkerqaq

ThinkerQAQ

@thinkerqaqJoined October 2026

Backend & Infrastructure Engineer | Go, Distributed Systems, Concurrency & AI Engineering

Website

About

Available for

ThinkerQAQ's blogs

ThinkerQAQthinkerqaq.hashnode.dev6 posts

ThinkerQAQ

About

Available for

ThinkerQAQ's blogs

Concurrency Programming (4): How Mutexes Are Implemented — From Runtime to CPU

Concurrency Programming (3): Mutexes — Atomicity, Visibility, and Ordering at the Language Level

Concurrency Programming (2): Language Memory Models — Rules Programmers Can Rely On

Concurrency Programming (1.5): The Operating System Layer — Threads, Schedulers, and Runtime Scheduling

Concurrency Programming (1): Start with the Hardware — From count++ to Atomicity, Visibility, and Ordering

Search Hashnode

ThinkerQAQ

About

Available for

ThinkerQAQ's blogs

Concurrency Programming (4): How Mutexes Are Implemented — From Runtime to CPU

Concurrency Programming (3): Mutexes — Atomicity, Visibility, and Ordering at the Language Level

Concurrency Programming (2): Language Memory Models — Rules Programmers Can Rely On

Concurrency Programming (1.5): The Operating System Layer — Threads, Schedulers, and Runtime Scheduling

Concurrency Programming (1): Start with the Hardware — From count++ to Atomicity, Visibility, and Ordering