Hardware, software and routines, updated when something changes. Nothing sponsored.
- CATEGORIES
- 5
- EDITOR
- Modal, 180 lines
- SHELL
- zsh 5.9
- UPDATED
- Sep 2026
What’s on the desk.
The tools and habits behind the work. Nothing sponsored, everything used this week.
- user
- nkessling
- host
- rotterdam, nl
- uptime
- 9 years in production
- shell
- zsh 5.9
- langs
- rust go ts zig
- editor
- modal
- focus
- storage · build · queues
- status
- open from nov 2026
- Laptop
- 14-inch, 36 GB, the one with the good keyboard
- Desk
- Oak, standing, set to 104 cm
- Keyboard
- Split, 42 keys, linear switches
- Screen
- 27-inch 5K, one only
- Test box
- Old mini PC running the crash simulator overnight
What I build with, by years in production.
Read it like an order book. Left: tools I have shipped and supported in production. Right: what I am learning now, and where I use it.
HELP, before you ask.
The questions people ask on the first call, answered in plain words.
Yes. I am in Rotterdam (CET) and work with teams from UTC−5 to UTC+3. I keep four hours of overlap every day.
Fixed scope and fixed price for audits and sprints, monthly for advisory. You get the price before we start, in writing.
Most of the work is design and measurement, not language. I have shipped the same fixes in Java, Python and C#.
Yes, and case studies only mention clients who said yes in writing. Numbers are shared only with permission.
During an engagement, yes, as second line. It is the fastest way to learn where a system really hurts.
Check the status board above. A two-week audit usually starts within three weeks of the first call.