tdooner

Joined 12 years ago

Karma

Submissions

Member since

Oct 4

Recent submissions

Agreed. The change was made to conform to ICAO standards[1], which the article alludes to, but doesn't examine the implications of remaining unstandardized. Surely having different phraseology in the US is a separate risk and cognitive burden!

To me the main issue is not "wait" vs "hold"... it's that either way, pilots may misremember having been issues the takeoff clearance. The best defense against this, IMHO, is ground radar to detect the movement as early as possible.

[1]: https://www.faa.gov/airports/runway_safety/resources/luaw

Comment · 2 years ago

Here is my favorite ATC mouthful. Flying in the Bay Area is full of these kinds of complicated instructions that will burn anyone unfamiliar:

https://www.youtube.com/watch?v=zQYZtPhK-mg

The controller expects you to hear, interpret, and read back the following clearance:

> N1234, you're cleared to airport XXX via fly runway heading until past the diamond-shaped waterway. Then turn right heading 120. Keep your turn within 2 miles of the airport. Radar vectors Woodside, then as filed. Maintain VFR conditions at or below 1100 feet until crossing the Oakland 165 radial, then climb and maintain 2100. Expect FL350 five minutes after departure. Departure frequency 135.65. Squawk 1234.

No wonder the pilots messed it up.

Comment · 6 years ago

Code for America | San Francisco, CA and REMOTE | Engineers (1x Security Eng, 1x Senior Eng with Java), Community Organizers | https://www.codeforamerica.org/jobs

Code for America is a non-profit that builds a government that works for the people, by the people, in the digital age. We believe government services need to be simple, effective, and easy to use, working at scale to help all Americans, starting with the people who need them most.

Especially in the time of Coronavirus, millions of Americans are about to rely on government assistance to support themselves and their families. We help governments across the country deliver this assistance with user-centered, iterative approaches. For example, our GetCalFresh product (https://GetCalFresh.org) processed a quarter of all CalFresh (food stamps) applications in California in late 2019, and our application volume has skyrocketed in the last week. (https://twitter.com/trapeeze22/status/1240731890941702144)

We are hiring for a few key roles:

* Security Engineer (Staff or Principal Level) - Lead our organization's security culture

* Software Engineer (Senior level, with Java experience)

* Network Coordinator (Remote)

* Program Manager - Brigade Network (Senior level)

Also, there are 85+ local volunteer groups across the country that are doing this work that could use your skills, and help you find a local job doing this kind of thing. Find one near you at: https://brigade.codeforamerica.org

Happy to take questions at tdooner AT codeforamerica.org.

Comment · 9 years ago

Code for America | Lead Software Engineer | SF or Remote | Full time

Code for America builds technology to help government services work for the people who need them most.

Be the founding engineer for a new technology team with a bold mission to provide SNAP & Medicaid benefits to every eligible American who needs them. This work seeks to improve the experience of 100M people that access the safety net each year, and tens of thousands of public servants.

We’ll accomplish this by developing a simple, respectful and relevant digital experience for every person seeking government assistance in a time of need, in all 50 states.

(I'd add that CfA is uniquely positioned in this space to have a huge impact on peoples' lives through access to nutrition assistance and healthcare.)

Here's the job post: https://www.codeforamerica.org/jobs?gh_jid=794135

Feel free to email me if you have any questions about this: [email protected]

Comment · 12 years ago

In case it's not loading for you, it looks like there's a mirror in the CoralCDN: http://swartzfiles.com.nyud.net/

Comment · 12 years ago

Cool, thanks for all your hard work on FF dev tools!

One thing I could really use is something that helps me understand how Firefox treats TCP/TLS/SPDY connections. It would illustrate the benefit of using CDN and maybe, with enough instrumentation, would help me tune asset sharding.

I put some thoughts in the uservoice here: https://ffdevtools.uservoice.com/forums/246087-firefox-devel...