惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Engineering at Meta
Engineering at Meta
T
Threatpost
P
Palo Alto Networks Blog
NISL@THU
NISL@THU
O
OpenAI News
Project Zero
Project Zero
G
GRAHAM CLULEY
P
Privacy International News Feed
A
Arctic Wolf
Microsoft Azure Blog
Microsoft Azure Blog
H
Help Net Security
M
MIT News - Artificial intelligence
T
Threat Research - Cisco Blogs
S
Security @ Cisco Blogs
Google DeepMind News
Google DeepMind News
B
Blog RSS Feed
D
Docker
aimingoo的专栏
aimingoo的专栏
博客园 - 【当耐特】
N
Netflix TechBlog - Medium
云风的 BLOG
云风的 BLOG
雷峰网
雷峰网
W
WeLiveSecurity
P
Proofpoint News Feed
腾讯CDC
Cloudbric
Cloudbric
S
Secure Thoughts
C
Check Point Blog
博客园 - Franky
T
The Exploit Database - CXSecurity.com
T
Troy Hunt's Blog
GbyAI
GbyAI
Security Archives - TechRepublic
Security Archives - TechRepublic
Application and Cybersecurity Blog
Application and Cybersecurity Blog
月光博客
月光博客
C
Cyber Attacks, Cyber Crime and Cyber Security
I
Intezer
TaoSecurity Blog
TaoSecurity Blog
L
Lohrmann on Cybersecurity
V
Visual Studio Blog
F
Fortinet All Blogs
博客园 - 叶小钗
C
CXSECURITY Database RSS Feed - CXSecurity.com
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
Recorded Future
Recorded Future
C
Cisco Blogs
博客园 - 司徒正美
Stack Overflow Blog
Stack Overflow Blog
Y
Y Combinator Blog
Apple Machine Learning Research
Apple Machine Learning Research

Pierce Freeman

A browser for agents | Pierce Freeman The grey market of podcast appearances The way I travel | Pierce Freeman Fixing slow AWS uploads | Pierce Freeman Local tools should still use vaults We solved scratch content first Starting a podcast in 2025 Being late but still being early Automating our home video imports Adding my parents to tailscale A deep dive on agent sandboxes Language servers for AI | Pierce Freeman My simple home podcast studio We need centralized infrastructure | Pierce Freeman Coercing agents to follow conventions using AST validation My unified theory of social selling My personal backup strategy | Pierce Freeman July updates to the homelab How the KV Cache works httpx is the right way to do web requests in Python Reputation is becoming everything | Pierce Freeman Building a (kind of) invisible mac app Updated knowledge in language models Making an ascii animation | Pierce Freeman How speculative decoding works | Pierce Freeman Under the hood of Claude Code Doing things because they're easy, not hard Speeding up sideeffects with JIT in mountaineer Firehot for hot reloading in Python Misadventures in Python hot reloading How text diffusion works | Pierce Freeman The tenacity of modern LLMs The ergonomics of rails | Pierce Freeman How language servers work | Pierce Freeman Just add eggs | Pierce Freeman Unfortunately SEO still matters | Pierce Freeman The futility of human-only web requirements Setting up Input Leap | Pierce Freeman Checking in on Waymo | Pierce Freeman The react revolution | Pierce Freeman Speeding up many small transfers to a unifi nas Quick notes on swift libraries AI engineering is a different animal San Francisco | Pierce Freeman Debugging a mountaineer rendering segfault Local network config on macOS Building our home network | Pierce Freeman Introducing Envelope.dev | Pierce Freeman Legacy code and AI copilots Typehinting from day-zero | Pierce Freeman Generating database migrations with acyclic graphs Lofoten | Pierce Freeman Mountaineer v0.1: Webapps in Python and React Constraining LLM Outputs | Pierce Freeman Passthrough above all | Pierce Freeman Accuracy in kudos | Pierce Freeman How quick we are to adapt The curious case of LM repetition Costa Rica | Pierce Freeman Debugging chrome extensions with system-level logging Speeding up runpod | Pierce Freeman Inline footnotes with html templates Parsing Common Crawl in a day for $60 An era of rich CLI All or nothing with remote work The Next 10 Years | Pierce Freeman Adding wheels to flash-attention | Pierce Freeman LLMs as interdisciplinary agents | Pierce Freeman New Zealand | Pierce Freeman Representations in autoregressive models | Pierce Freeman Let's talk about Siri | Pierce Freeman Minimum viable public infrastructure | Pierce Freeman Reasoning vs. Memorization in LLMs Automatically migrate enums in alembic Greater sequence lengths will set us free On learning to ski | Pierce Freeman Dolomites | Pierce Freeman Using grpc with node and typescript Opportunity years | Pierce Freeman Buzzword peaks and valleys | Pierce Freeman Buenos Aires | Pierce Freeman Network routing interaction on MacOS Independent work: November recap | Pierce Freeman Debugging slow pytorch training performance The provenance of copy and paste Debugging tips for neural network training Patagonia | Pierce Freeman Santiago | Pierce Freeman My 2022 digital travel kit AWS vs GCP - GPU Availability V2 Independent work: October recap | Pierce Freeman Planning Patagonia | Pierce Freeman Relationship modeling | Pierce Freeman The power of status updates A new chapter | Pierce Freeman Give my library a coffee shop AWS vs GCP - GPU Availability V1 Switzerland | Pierce Freeman Headfull browsers beat headless | Pierce Freeman Webcrawling tradeoffs | Pierce Freeman
Busses can fool me thrice
2022-08-30 · via Pierce Freeman

Public transit is often framed as necessary philanthropy for cities. It cuts down on cars and pollution at the expense of convenience. If people can more efficiently get to their destination by other means, they will.

This is the wrong way to look at things.

Public transit at its best can be additive for individuals, not just the aggregate good. You don't have to worry about parking, you don't have to worry about traffic, and you know exactly how long it's going to take to get from Place A to Place B. London, Paris, and New York have this figured out - everyone takes the subway, even if they have other options. There is broad support for public transit because it fits into the everyday fabric of city life. But for public transit to really work, it needs trust.

I was waiting for a Muni early in the spring when I first moved to San Francisco. It was a beautiful day; sun was streaming and traffic was lazy. Green routes all across the city according to Google Maps. The bus schedule said to show up at 11:30 so I showed up at 11:23. A steady stream of cars cruised by. Seven minutes tick by - no bus. I double check the clock. One minute turns into five and then twenty. The next bus showed up early and took off immediately. I was on it but if I had gotten there on time for the official schedule, I would have missed it.

I tried again later that week. Same thing, different route. Citymapper said the bus had come and gone yet there certainly was no bus. Like the bus before, one eventually showed up. I wound up with a 25 minute delay and 10 minutes late to my appointment. This wasn't a big deal given my specific meeting but for someone's job interview, potentially career altering.

It left the impression that busses come when they want and adhere to no clear schedule. With something as integral as mobility, doubting the reliability of a schedule breaks public trust in the system. You might give it a few chances but after three you'll relegate public transit to a form of transport that you'll only use when you have no other options or otherwise have time on your hands.

Promptness is the sole and only KPI that matters for public transit. If you want to plan it into your schedule, it needs to be trustworthy. MUNI was on time 57.3% of the time in 2018, which was down from 59.8% of the time in 2016. Being on-time in their report also factors in some fuzziness: -1 minute to +4 minutes of scheduled time. This statistic is abysmal. It's a coin flip that your bus will come on time. And as far as I can tell there's no public tracking on the variance of delays. How often are busses delayed 10 minutes or more? 20 or more? The city's goal is for 85% of busses to come on time but the numbers have remained stagnate for at least the last decade. The 58% average just won't budge.

It feels like there are some easy things that metros (especially the San Francisco one) could do today to increase trust:

  • Every bus should have a GPS beacon with its current location, status, and projected delay. These are available on some routes but not all. Roll them out across the board. Go with the low-fidelity consumer hardware model like SpaceX. Don't use hardened infrastructure that charges an exorbitant markup. Just use an android cellphone with custom software.
  • Have busses been explicitly canceled? Publish cancelation notices online. List the date, bus number and time on one page, versus global announcements that cover multiple lines. More ideally integrate with the most used transit apps across Google Maps, Apple Maps, and Citymapper.
  • Avoid riders fiddling with the bike rack. Keep it always down to optimize the efficiency of boarding or deboarding without the variance of whether riders need to strap their bike.
  • Wait for arrival time. If a bus arrives at a stop before the scheduled arrival time, wait. It's better for a bus to be 5 minutes late than 5 minutes early and leave immedaitely.

Other actions to increase reliability are more impactful but more complicated. They also typically require public financing to change underlying infrastructure. However, cities need to start with trust. If more people trust the transit system, they'll be more likely to approve upgrades. Without trust, people are going to keep using their cars.