40 years on, Former Nintendo employees reveal what it took to launch the NES
hanafuda.report
Ask HN: What Are You Working On? (Nov 2025)
Itiner-e: the Google Maps of Roman Roads
itiner-e.org
Montana becomes first state to enshrine 'right to compute' into law
montananewsroom.com
Show HN: DroidDock – A sleek macOS app for browsing Android device files via ADB
rajivm1991.github.io
Drilling down on Uncle Sam's proposed TP-Link ban
krebsonsecurity.com
Open source has a growing problem with LLM generated issues
github.com
JVM exceptions are weird: a decompiler perspective
purplesyringa.moe
Building a 2.5kWh battery from disposable vapes to power my workshop [video]
youtube.com
The Manuscripts of Edsger W. Dijkstra
cs.utexas.edu
My Git history was a mess of 'update' and 'fix' – so I made AI clean it up
github.com
The Principles of Diffusion Models
arxiv.org
The Sega Master System
bumbershootsoft.wordpress.com
Bumble Berry Pi – A Cheap DIY Raspberry Pi Handheld Cyberdeck
github.com
Work after work: Notes from an unemployed new grad watching the job market break
urlahmed.com
How to maintain good vision amidst the myopia epidemic
ssathe.substack.com
Today I Learned: Binfmt_misc
dfir.ch
Reviving Classic Unix Games: A 20-Year Journey Through Software Archaeology
vejeta.com
How the UK lost its shipbuilding industry
construction-physics.com
Zensical – A modern static site generator built by the Material for MkDocs team
squidfunk.github.io
When your hash becomes a string: Hunting Ruby's million-to-one memory bug
mensfeld.pl
Email verification protocol
github.com
SQL-first analytic IDE; similar to Redash/Metabase. Aims to solve reuse/composability at the code layer with modified syntax, Trilogy, that includes a semantic layer directly in the SQL-like language.
Status: experiment; feedback and contributions welcome!
Built to solve 3 problems I have with SQL as my primary iterative analysis language:
1. Adjusting queries/analysis takes a lot of boilerplate. Solve with queries that operate on the semantic layer, not tables. Also eliminates the need for CTEs.
2. Sources of truth change all the time. I hate updating reports to reference new tables. Also solved by the semantic layer, since data bindings can be updated without changing dashboards or queries.
3. Getting from SQL to visuals is too much work in many tools; make it as streamlined as possible. Surprise - solve with the semantic layer; add in more expressive typing to get better defaults;also use it to wire up automatic drilldowns/cross filtering.
Supports: bigquery, duckdb, snowflake.
Links [1] https://trilogydata.dev/ (language info)
Git links: [Frontend] https://github.com/trilogy-data/trilogy-studio-core [Language] https://github.com/trilogy-data/pytrilogy
Previously: https://news.ycombinator.com/item?id=44106070 (significant UX/feature reworks since) https://news.ycombinator.com/item?id=42231325