Knowledge creates technical debt (via isuffix) — discussion

#programming

Software can be finished (via edwardloveall) — discussion

#philosophy #practices

Micro Machines BIC-23 PCB with hardware ROM patch (via JordiGH) — discussion

#games #hardware #retrocomputing

Scheme Reports at Fifty: Where do we go from here? (via amirouche) — discussion

#lisp

The design space of AI coding tools (by azhenley) — discussion

#ai

Ripgrep 15.0.0 (via telemachus) — discussion

#release

An open letter to the Obsidian team (via topicpartition) — discussion

#practices

On Perfetto, Open Source, and Company Priorities (via rayhaan) — discussion

#performance #visualization

Joe Decuir Engineering Notebook 1978 (via weinzierl) — discussion

#retrocomputing

Solving the NYTimes Pips puzzle with a constraint solver (via calvin) — discussion

#compsci #games

Flowistry: An IDE plugin for Rust that focuses on relevant code (via justinpombrio) — discussion

#design #editors #plt #rust

ASK: If you could redesign Linux userland from scratch, what would you do differently? (by runxiyu)

#ask #linux #osdev

Using CUE to unify IoT sensor data (via mvdan) — discussion

#go

Building an Agent That Leverages Throwaway Code (via cgrinds) — discussion

#vibecoding

Fast calculation of the distance to cubic Bezier curves on the GPU (via polywolf) — discussion

#graphics #math

Exploring PostgreSQL 18's new UUIDv7 support (via eduard) — discussion

#databases

Scaling Postgres to the next level at OpenAI (via topicpartition) — discussion

#databases #video

Why formalize mathematics - more than catching errors (via evmar) — discussion

#math #plt

TXR Bytecode Optimization Case Study (via veqq) — discussion

#assembly #lisp

How Tailscale is improving NAT traversal (Part 1) (via yashgarg) — discussion

#networking