- Updates to CockroachDB’s security architecture between v20.1 and v22.1
- Nested transactions in CockroachDB 20.1 External blog post
- Local connection overheads in PostgreSQL and CockroachDB
- Authentication configuration in PostgreSQL and CockroachDB
- Data flows and security architecture in CockroachDB
- The acronym “DML” may not mean what you think it means
- My database has bugs — now what?
- The “PostgreSQL” in CockroachDB — Why?
- The “Open Source” in CockroachDB
- The “Wow” effect in CockroachDB
- Local and distributed query processing in CockroachDB External blog post
- On the Way to Better SQL Joins in CockroachDB v1.0 External blog post
- Memory Usage in CockroachDB External blog post
- Squashing a Schrödinbug With Strong Typing External blog post
- Modesty in Simplicity: SQL JOINs in CockroachDB pre-1.0 Beta External blog post
- Critters in a Jar: Running CockroachDB in a FreeBSD Jail External blog post
- Revisiting SQL typing in CockroachDB External blog post
- DYI Jepsen Testing CockroachDB External blog post
- How to get into computer security (2/2) Data & Dev S1:E7 — Transcript
- How to get into computer security (1/2) Data & Dev S1:E6 — Transcript
- CS PhD student in the Netherlands: to be or not to be?
- My “ideal” Bachelor of Informatics
- Proefstuderen Informatica
- Resources on writing and teaching
- Introductie Unix De eerste dag overleven
- One-on-one meeting questions
- You’re a Tech Lead. What now?
- Navigating and optimizing performance reviews
- Self-direction: navigating agency and responsibility
- Tech Career Progression for Beginners Everything you didn't learn at school about evolving in a corporation
- Understanding the Beginner’s Mind How to deal with different learning styles and anxieties
- Levels of Technical Leadership
- From $100M Offers to AI Misfires: Notes on Value, Hype, and Human Blind Spots
- Context Rot, Corporate Feudalism, and the Art of Weakening Belief Edges
- The Illusion of Thinking: LLM Cosplay and the Coming AI Class War
- Quintism, Friction Economics, and Building a Calm Companion in the Who Cares Era
- Hyperlegibility, Democracy Under Siege, and the Weight of Unseen Consequences
- The Bullshit Singularity: When the Internet Breaks Even for the Trained
- Essentialism, AI Skepticism, and the Moral Duty to Write Human Content
- Lullaby Language, Systematic Design, and Civilizations as Natural as Grass
- The Care Economy and the 70% AI Problem
- The Ambassador Matrix: A New Framework for Understanding Your Network
- The Multi-Project Mind: Why Some People Need 4-5 Important Things at Once
- From Reading to YouTube: Project Portfolio Explosion
- Notes on networking
- The Death of the Public Internet and Rise of Private Group Chats
- The Misallocation of Brilliance: From Phantom Stock to Self-Expression Traps
- Management Lessons from the Construction Site
- When Thiel Meets Covey: Technology, Politics, and the Art of Robust Tolerance
- Fractals, Trust, and the Limits of Teaching Wisdom
- Reading Renaissance: Books, AI Skepticism, and Corporate Games
- The Product Builder’s Epiphany
- From Cockroach Labs to Campaign Trail
- Unusual primitives in programming languages
- The machine does not (yet) think outside of the box
- Loss of input in Charm’s Bubbletea
- My Go executable files are still large What's new in 2021 and Go 1.16
- Errors vs. exceptions in Go and C++ in 2020 Why and how exceptions are still better for performance, even in Go
- The Go low-level calling convention on x86-64 (updated) What's new in 2020 and in Go 1.15
- Beyond fmt.Errorf()—everyday error objects in Go The CockroachDB errors library, part 4/
- The Go error printing catastrophe The CockroachDB errors library, part 3/
- The Go standard error APIs The CockroachDB errors library, part 1/
- Go’s formatting APIs The CockroachDB errors library, part 2/
- Cloud-Native Security has Two R’s, not Three How I saved $50k and how you can too
- Expressivity vs Tractability
- Ubuntu without Snap
- A tour of Emacs as my Go editor
- Why are my Go executable files so large? Size visualization of Go executables using D3
- Measuring errors vs. exceptions in Go and C++ Also, why and how exceptions are usually better for performance, even in Go
- Measuring argument passing in Go and C++
- Measuring multiple return values in Go and C++
- The Go low-level calling convention on x86-64
- The 4th law of programming language comparisons
- How good are you at programming? A CEFR-like approach to measure programming proficiency
- Rust for functional programmers
- Haskell for OCaml programmers
- Finding the right tool for the job - FAIL
- OpenRISC / de0 nano resources
- Time is a Range, Not a Point Introducing timecond
- The Share Web A manifesto
- The STRIDE threat model with examples
- Hacking week: hardware/software co-design for a UT-LEON3 extension
- The Dark Resistance
- Crazy research: bio warfare against mega corps
- Comments on the Mill CPU from OotB Computing
- Building computing systems for research and innovation
- Frustrated elements of symmetry
- How I met the Microgrids
- The Vaucanson story
- Proposal: high-level thermal modeling