From backend to bedtime
Supabase, Terra Charge, Lumio, and more raised funds this week.
We haven't written up this one. Tech in Asia has the full story — the link below goes straight to it.
More in Tech
The Epistemology of Quality
Should we expect human software developers to review code written by AI? For many the answer is clearly yes: how else will we maintain accountability?
- Traditional code review focused on syntax and standards, lacking teaching opportunities.
- Pair programming combined various evidence types, providing stronger defect detection.
- AI-generated code may lack real-world proof, making manual review critical.
2026's OLED monitors can nearly recreate the sublime clarity of a '90s CRT, but Windows will have to change before we can achieve true nirvana
All you need is a ridiculously fast monitor and endless patience for tinkering to get a glimpse of how good retro games looked in motion back in the '90s.
This mini PC with a 5.7-inch touchscreen drops to $480
An all-in-one solution at a great price
adagents.json vs ads.txt and schain: Four Files, Two Supply-Chain Questions
In early October 2026, IAB Tech Lab's programmatic supply-chain leadership pushed back on the idea that adagents.json should replace ads.txt , sellers.json , and the OpenRTB SupplyChain object.
- adagents.json could replace ads.txt, sellers.json, and OpenRTB SupplyChain object
- Adagents.json lists authorized agents with agent URLs and property scope
- Adagents.json does not replace ads.txt, sellers.json, or schain
How I built a PWA barcode scanner that pairs your phone to a desktop spreadsheet
The problem Small retail teams either buy a $100+ USB barcode scanner per workstation or type codes by hand. The scanners work, but they are tethered and priced per seat.
- Desktop and phone connect via WebSocket relay, streaming real-time scan data to a table
- Optimizations include enabling specific barcode formats, debouncing, and versioning script URLs
Login Is Not Order Ownership: A Small Authorization Review Worksheet
A successful login tells an application who is making a request. It does not, by itself, decide whether that person should see a particular order.
- Successful login identifies user but doesn't grant order view permission
- Separate authentication from authorization, check permissions on each request
- Support accounts need specific permission to access orders within scope