A practical backend engineering roadmap with interactive explainers and visualizations.
Topics include networking, HTTP, databases, queues, caching, distributed systems, and real-world outages.
Feedback welcome.
This should hopefully reduce the spread of the recent Shai Hulud attacks on npm but they are reliant on you catching the bugs in transit meaning you need to assume still that packages are compromised (I know, bummer). Think of it more as a reduction in spread rate the a treatment or cure.
I wanted a library like vis.js but needed it canvas-based for server-side rendering without a headless browser in node, so I built one. I'd love to get some feedback.
MikroORM 7.1 is out — the first minor on top of v7, and it's a big one.
New features:
Full blog post: https://mikro-orm.io/blog/mikro-orm-7-1-released
Changelog: https://github.com/mikro-orm/mikro-orm/releases/tag/v7.1.0
Happy to answer any questions!
Most React conferences try to cover everything. React Norway 2026 focuses on the things frontend teams are actually struggling with right now.
AI agents running in the browser
Modern React architecture and async patterns
React security and how apps get hacked
Dead code elimination and healthier codebases
etc.
350 people. One stage. 10 speakers. 3 bands. Great food and even better networking.
📍 June 5th, 2026 — Rockefeller, Oslo
I’m working on pack, a simple way to deploy self-hosted apps.
I always liked the old Zeit/Vercel now flow: run one command in a project and get a URL that is persistent, immutable and does not need platform specific code.
I wanted something similar for myself, so I am working on pack.
The approach I chose is single-file executables. It builds your app into one file, uploads, and runs it.
Node, bun, deno, go, rust, zig and c/c++ all support single file executables so that part was actually pretty straightforward. The most complex part was handling port pooling, caddy setup and inactive instances.
Using single-file executables keeps server setup very minimal and makes it easy to run many small apps on a cheap VPS. It also removes the need to configure node or any other runtime on the server.
Feedback and PR's welcome!
​
Notes:
---
- Create, view, search, edit, archive, and delete plain-text notes from a tile-based dashboard.
- Live sentence, word, and character counts (Unicode-aware via `Intl.Segmenter`) while reading or editing.
- Per-note undo / redo history while editing (up to 100 steps).
- Sort notes by **Updated**, **Created**, **Title**, or **Sentence/Word/Character Count**, ascending or descending.
- Archive notes you want to keep but not see on the main dashboard; unarchive them at any time.
Import / Export:
---
- Import any plain-text file, having any extension, as a new note. Files are content-sniffed before import and unsupported files are rejected.
- Multiple files can be imported in one go.
- Export a single note as a `.txt` file.
- Export selected notes or **Export All** as a `quick-pad-notes.zip` archive.
PWA / Sync:
---
- Installable as a Progressive Web App.
- Sign in with Google to back up notes to your Drive's app-data folder (the app cannot see any other files in your Drive).
Full Disclosure: I have vibe-coded parts of it. There was a short window when I had virtually unlimited access to Claude Opus 4.7 and I wanted to make the most use of it. I must say, while I am really pleased with the results, it's not a magic wand.
Issues: The auth flow is entirely client-side, with no server-side token refresh, so you might occasionally see a pop-up window if you use Google sync.
EDIT: Forgot to link repo. Here it is: https://github.com/FlameWolf/quick-pad