Rails is better low code than low code (via MatheusRich) — discussion
#ruby
Rails is better low code than low code (via MatheusRich) — discussion
#ruby
Shaping a better future for Bazel C/C++ toolchains (via kaycebasques) — discussion
#c #c++ #compilers #hardware #practices #scaling
Ucacher: Speeding up GitHub Actions via syscall instrumentation (via vladaionescu) — discussion
#devops #performance
pgroll - Zero-downtime, reversible, schema changes for PostgreSQL (new website) (via tsg) — discussion
#databases
the return of glfighters: porting a 23-year-old game to webassembly (via wizardishungry) — discussion
#games #retrocomputing #wasm
Supply-chain attack analysis: Ultralytics - The Python Package Index Blog (via yossarian) — discussion
#python #security
Select dropdown for polymorphic associations (via pushcx) — discussion
#ruby #web
A brief history of Mac servers (via lproven) — discussion
#historical #mac
FP For The Working Programmer: Why Is null Bad? (via bitfield) — discussion
#plt
Counting up concurrency (via lizmat) — discussion
#compsci #math
Render README.org as HTML on Sourcehut (by breatheoutbreathein) — discussion
#emacs
The new Vim project - What has changed after Bram (via MaskRay) — discussion
#video #vim
ASK: How are smaller teams handling multi-repo testing? (by rtpg)
#ask #practices #testing
The Google Willow thing (via orib) — discussion
#programming
How to build an exchange (via danthegoodman1) — discussion
#distributed #finance #video
Turbo morphing woes (via MatheusRich) — discussion
#web
Understanding DiskANN (via emschwartz) — discussion
#ai #databases
The Death of the Stubborn Developer (via duncan_bayne) — discussion
#ai #programming
Nobody Gets Fired for Picking JSON, but Maybe They Should? (via emschwartz) — discussion
#api
Forced to upgrade (via j3s) — discussion
#hardware