← Feed

Posts

• Post #4466632

  Want to work in a very nice environment adjacent to my team (we'll also solve some interesting challenges together)? #Kubernetes in the public sector: https://jobs.fernuni-hagen.de/job/Container-Platform-Engineer-Linux-IT-Administratorin-%28wmd%29/2060-de_DE

• Post #4466631

  3D software visualisation never failed for technical reasons. It fails for perceptual ones: occlusion, an arbitrary Z axis, dying labels – and depth is one of the weakest visual encodings we know (Cleveland & McGill, 1984). Thirty years of beautiful demos nobody uses twice. The bottleneck is the visual cortex, not the GPU. I still want to build one. I might. It'll be beautiful, and it'll fail: https://kore-nordmann.de/blog/why-3d-software-visualisation-keeps-failing.htm...

• Post #4466630

  We assume the network is stable because day to day it works. It isn't: it fails, delays, delivers twice, delivers out of order. In-process, one compiler spans both sides of an interface and won't let the two ends drift. Move the call onto the network and you throw that arbiter away for drift, partial failure, and cross-process debugging. Pay that for a runtime reason, not to show two things are separate. https://kore-nordmann.de/blog/hexagonal_architecture_vs_microservices.html

• Post #4011251

  Long-lived feature branches are a problem you create for yourself. I have watched teams split into separate repos, carve out services, even go to micro-frontends, all so parallel work stops colliding. That is a process problem dressed up as a structural one. The collisions are not telling you to break up the system. They say: integrate more often. https://kore-nordmann.de/blog/feature_flags_over_branches.html

• Post #3826887

  A team next to us just split a working monorepo into ~80 repositories. It will cost them dearly, and slowly. You wanted a boundary. A directory is a boundary. A repository is the most expensive way to draw one: cross-repo PRs, version pinning, a deploy matrix, drifting style. Velocity does not collapse, it bleeds. If the polyrepo tax bends Google toward one repo, it matters at your scale too. https://kore-nordmann.de/blog/always_go_with_a_monorepo.html

• Post #3339434

  Your `` is invisible to keyboards and screen readers. Nothing made you write it, but nothing in your framework's workflow ever asked you not to. The browser ships `` with focus trap, Escape, and correct semantics, built by people who do nothing else. Your component library re-implemented it in userland, with its own bugs. The cheapest accessibility work is the work the browser already did: https://kore-nordmann.de/blog/htmx-and-web-components-instead-of-react.html

• Post #1911594

  Ten years ago I started writing a book about software design. Then I co-founded a company, scaled to 70 engineers, got acquired, and the manuscript sat untouched for years. Last year I picked it back up. The decade in between proved the ideas worked. "Nothing Shared, Everything Gained", minimal side effects, strict dependency direction, code that stays changeable. PHP examples, universal principles. Pay what you want, starting at €0: https://codethatships.com

• Post #1628936

  RE: https://narrativ.es/@janl/116407288886097413 Thank you, Jan ❤️ Your foreword, your review, and especially your notes on inclusive language helped shaping this book. Coming from someone whose work on CouchDB I've admired for years, "made me excited about programming again" is a review I'll remember.