I don't know if my job will still exist in ten years (via lalitm) — discussion

#vibecoding

Your LLM Doesn't Write Correct Code. It Writes Plausible Code (via kitschysynq) — discussion

#vibecoding

Rust-like Error Handling in TypeScript (by csomar) — discussion

#javascript #programming #rust

Production query plans without production data (via sjamaan) — discussion

#databases #performance

Returning To Rails in 2026 (by mdr) — discussion

#programming #ruby #web

AI will fuck you up if you’re not on board (by rmoff) — discussion

#vibecoding

Open Sores (via animesh) — discussion

#culture

ASK: What are you doing this week? (by caius)

#ask #programming

Linux Internals: How /proc/self/mem writes to unwritable memory (via git-bruh) — discussion

#linux

Thinnings: Sublist Witnesses and de Bruijn Index Shift Clumping (by philzook) — discussion

#formalmethods #plt

Coding Agents Wrote a Chess Engine in Pure TeX (via azhenley) — discussion

#vibecoding

WebPKI and You (by bryce) — discussion

#security

Getting started with ClickHouse? 13 mistakes and how to avoid them (via knl) — discussion

#databases

Cambridge Battlecode: Code bots that compete in a turn-based strategy game (via azhenley) — discussion

#programming

Why octal notation should be used for UTF-8 (and Unicode) (2016) (via dzwdz) — discussion

#programming

Cakelisp (via veqq) — discussion

#lisp

Interpreting whiteout files in Docker image layers (via AccidentallyInvited) — discussion

#devops

Ensuring correctness through the type system (via kamila) — discussion

#clojure #gleam #java #testing

z80-sans: OpenType font that disassembles Z80 instructions (via indigo) — discussion

#assembly

Solving Regex Crosswords Without Z3 (by daniel_alp) — discussion

#compsci