Microsoft Flight Simulator 2024 is coming to Playstation 5 on December 8th
flightsimulator.com
Quicksort explained IKEA-style
idea-instructions.com
Huntington's disease treated for first time
bbc.com
Björk on nature and technology (2016)
thecreativeindependent.com
Terence Tao: The role of small organizations in society has shrunk significantly
mathstodon.xyz
Python on the Edge: Fast, sandboxed, and powered by WebAssembly
wasmer.io
SedonaDB: A new geospatial DataFrame library written in Rust
sedona.apache.org
New bacteria, and two potential antibiotics, discovered in soil
rockefeller.edu
Engineering a fixed-width bit-packed integer vector in Rust
lukefleed.xyz
Launch HN: Flywheel (YC S25) – Waymo for Excavators
Learning Persian with Anki, ChatGPT and YouTube
cjauvin.github.io
How fast is Go? simulating particles on a smart TV
dgerrells.com
How to Lead in a Room Full of Experts
idiallo.com
Driving Complex Decisions
garrettdbates.com
Yt-dlp: Upcoming new requirements for YouTube downloads
github.com
That Secret Service SIM farm story is bogus
cybersect.substack.com
How AWS S3 serves 1 petabyte per second on top of slow HDDs
bigdata.2minutestreaming.com
SonyShell – an effort to "SSH into my Sony DSLR"
github.com
Zed's Pricing Has Changed: LLM Usage Is Now Token-Based
zed.dev
US airlines are pushing to remove protections for passengers and add more fees
travelandtourworld.com
Ask HN: Local hostnames without root/admin
EU age verification app not planning desktop support
github.com
The point about how the expected decision timeline is often a small part of the total decision timeline really resonates with me. Often (in my big tech experience) we say we can get a design done in a week, and then we spend three more weeks running the design up and down the leadership chain and through stakeholders elsewhere in the company, at which point you're three weeks past the date everyone expected and you finally have a plan.
It really helps to front-load the controversial questions. That way, if the team/organization/leadership gets mired down in that discussion, it's (1) determining constraints to reduce your search space early, and (2) it isn't setting false expectations about how long the decision will take because the design work hasn't even started!
One thing I miss about working in a startup is that you didn't have that many stakeholders to go through, so there wasn't nearly as much communication/stakeholder overhead to work through.