HN user

zackbloom

3,638 karma
Posts82
Comments565
View on HN
blog.cloudflare.com 4y ago

Announcing the Cloudflare API Gateway

zackbloom
5pts0
blog.cloudflare.com 4y ago

Two Weeks Later: Finding and Eliminating Long Tail Latencies

zackbloom
37pts0
twitter.com 5y ago

“Curious what appearing on the TODAY show does for your startup?”

zackbloom
3pts0
stratechery.com 5y ago

Cloudflare on the Edge

zackbloom
4pts1
blog.cloudflare.com 5y ago

Expanding the Cloudflare Workers Observability Ecosystem

zackbloom
1pts0
sendheirloom.com 5y ago

Show HN: Send Videos Physically in the Mail

zackbloom
1pts0
blog.cloudflare.com 5y ago

Cloudflare Launches Machine Learning-Based API Abuse Detection

zackbloom
3pts0
www.infoq.com 6y ago

Using Edge Computing to Build a Faster Web

zackbloom
1pts0
docs.google.com 6y ago

Pneumatic Pandemic Ventilator Project

zackbloom
5pts0
blog.cloudflare.com 6y ago

JavaScript Libraries Are Almost Never Updated Once Installed

zackbloom
74pts32
blog.cloudflare.com 6y ago

JavaScript Libraries Are Almost Never Updated Once Installed

zackbloom
3pts1
www.peoplespolicyproject.org 6y ago

The Leisure Agenda

zackbloom
1pts0
blog.cloudflare.com 6y ago

Public keys are not enough for SSH security

zackbloom
7pts0
blog.cloudflare.com 6y ago

The Technical Challenges of Building Cloudflare Warp

zackbloom
1pts0
blog.cloudflare.com 6y ago

Faking the Filesystem: Building Workers Sites

zackbloom
3pts0
theregister.co.uk 7y ago

Cloudflare goes big on serverless with new CLI, lures devs with free tier

zackbloom
7pts0
blog.cloudflare.com 7y ago

Just Write Code: Improving Developer Experience for Cloudflare Workers

zackbloom
2pts0
blog.cloudflare.com 7y ago

Cloudflare's distributed database is out of beta

zackbloom
5pts3
blog.cloudflare.com 7y ago

The Climate and Cloudflare

zackbloom
67pts35
blog.samrhea.com 7y ago

A guide to overanalyzing your media habits

zackbloom
2pts0
workers.dev 7y ago

Show HN: Workers.dev

zackbloom
1pts0
workers.dev 7y ago

A New Serverless Compute Platform Enters The Fight

zackbloom
2pts1
blog.cloudflare.com 7y ago

SSH Access through Cloudflare

zackbloom
68pts40
blog.cloudflare.com 7y ago

Cloud Computing Without Containers

zackbloom
663pts241
medium.com 7y ago

The Cloud Without Containers

zackbloom
9pts3
www.eff.org 7y ago

ESNI: A Privacy-Protecting Upgrade to HTTPS

zackbloom
5pts1
blog.cloudflare.com 7y ago

Expanding DNSSEC Adoption

zackbloom
2pts0
medium.com 7y ago

Serverless Pricing: AWS Lambda and Lambda at Edge

zackbloom
2pts0
blog.cloudflare.com 7y ago

The Road to QUIC

zackbloom
141pts48
blog.cloudflare.com 8y ago

Cloudflare Workers is 4.6x faster for CPU-bound tasks than Amazon Lambda

zackbloom
30pts5

Just to give a little context as a pilot: It is the job of the tower controller to decide who uses the runway when. There are often multiple planes waiting to take off, and multiple planes nearing the airport to land. It's not uncommon for a tower controller to allow a plane to takeoff while another is approaching the runway. The theory is, of course, that the flight will depart in plenty of time.

In this case, the controller failed to tell the departing flight to hurry (the references to 'no delay' or 'immediate' in the blog post), AND frankly timed things pretty close given the weather. Without the ability to actually see the approaching plane, or perhaps even the plane on the ground, it will probably be found that timing a departure that close at all was reckless. That said, I feel for these tower controllers, it's not common for many planes to get stacked up waiting to depart, and it is their job to get them out. What may have worked just fine on a clear-weather day simply became too dangerous on that day.

The official manual for air traffic controllers in the US is the FAA Order JO 7110.65W [1], if anyone cares to review it.

1 - https://www.faa.gov/documentlibrary/media/order/atc.pdf

Has anyone actually tried the experiment posed in the article? If I go to Amazon and search 'spatula', I get pretty reasonable results:

- A Kitchenaid spatula for $7.99

- A similar set of two knockoff brand ones for $13.99

- Some editorial recommendations including one from OXO, a wooden option, a fish spatula, etc.

I wonder what weird state the person writing this has on Amazon.com, or maybe it's all hyperbole?

Unlike the NOTAM outage, a METAR outage will and should actually affect flights. Without weather at your destination it becomes impossible to know if it’s safe to land there. The forecasts (TAF) are actually used more in flight planning, but actual weather is very valuable while enroute, when not close enough to hear weather over the radio from the destination airport.

I think the title is using the word 'inevitably' where they mean 'eventually' or 'ultimately'. It's not inevitable that people who invest in Bitcoin lose money, for example, they could have changed their mind and sold then next day, making it avoidable. What they mean to say is that most people who invest _end up_ losing money, not that it was unavoidable (the meaning of inevitable).

It’s worth pointing out that the last row on a plane often doesn’t recline, so the idea of everyone reclining is a bit of a red herring. That said, you do know that when you book your flight (if you’re wealthy enough to pay for a specific seat), so it could be considered one of flyings many taxes on the less than wealthy.

I went out of my way to feed the Apple ][ video into the luminance pin of an S-Video port for this segment to make the text more readable at the expense of color.

I found this to be the most interesting part of the whole post, I'd love to see a schematic of how that works.

For the record, the 'Feels Like' temp usually takes wind speed into account. It's probably not necessary for the dev to include that factor manually.

For me it showed 79F and sunny as 'pants weather' (my Feels Like temp is 87F), I'm not sure I fully endorse this algorithm.

The most wild thing, to me, is how effectively it has been taken over by scam artists. The other day I tuned into a 'startup pitch' show where the premise is you pitch your company idea to an 'investor'. Unfortunately in practice the investor applauds your idea, and then claims he will 'invest' engineering time worth hundreds of thousands of dollars, but he needs you to 'prove you are serious' by investing tens of thousands of dollars of your own money.

I'm sure after putting up the cash you are handed some janky app worth nothing close to what you paid, much less his supposed investment. While maybe not being illegal, it was incredibly predatory. The 'entrepreneurs' weren't being asked the most basic questions about their business, and were clearly not financially in a place to invest the money he was demanding. Rather than helping them achieve an entrepreneurial dream, he is sucking up the limited money they have (perhaps even inviting them to take on debt) without any real hope of success.

It seems like every channel on Clubhouse is some version of exploitation, whether it's about crypto, your love life, or your money. I don't know how I would moderate that away if I was them, but it seems like the time to do it was several months ago, and now might be too late.

Cloudflare Tunnel will spin up a free tunnel for you even without a Cloudflare account. If you run `brew install cloudflare/cloudflare/cloudflared` and then `cloudflared tunnel --url http://localhost:8080` you will get a URL you can use to reach that local port from the Internet.

I use it to share in-progress work with co-workers, test webhooks, etc.

Edit: fixed command thanks to comment below :)

Hate to say it, but I'm not sure this type of visualization is ideal for this data. Given that the actual clustering is meaningless, I would think a simple histogram would expose the relationship between the different cities better.

My mind could be changed if this exposed a hierarchy, for example if the US was a single bubble which could be clicked-into. Or if there was a meaning behind the clustering, like if geographic proximity determined how close the bubbles were.

Tesla makes improvements at a much faster rate than conventional car companies, which results in what we might call 'hacks' as those changes matriculate through the other design components. It's not ideal, but decades of building software has pretty conclusively shown that agility and shipping quickly is a better practice than waiting for perfection.

You might say "well agility is great, except in my self-driving car" but I would remind you that people said the same thing about security software, infrastructure, etc. and were wrong every time. My believe is cars will get safer and better built faster with them innovating than with the traditional model of annual incremental releases. As a Tesla owner, I can also comment that the car feels no less well built than any other car I've owned.

The Model 3 was designed later than the original S and X, meaning it had a fit-and-finish which S and X lacked, at least until the recent refresh. I see that disparity as an example of Tesla disrupting itself, being willing to launch a lower-priced model which could compete with it's own luxury vehicles.

Since then, the S has been refreshed (including Plaid mode), making it more competitive. They are now in a situation where demand outstrips supply, with extensive delays to get hold of a Model X in particular. To me this signals that demand is now there, but Tesla is actively making the choice to focus on the 3 and Y production volume (which also contributes to the Cyber Truck, Roadster, and Semi all not being available yet).

It's also worth noting that much of JWST is now twenty year old technology. Assuming it isn't a total failure which needs to be salvaged for PR reasons, it will almost certainly make more sense to build a new observatory in ten years rather than rescuing this one. If Starship exists at that point it will also be a much less complex undertaking to get it into space, and it could likely use an even bigger mirror.

Empathy is a powerful thing. We make many little decisions during the work week around if it's ok to take something down, if an engineer's request needs to be handled immediately, etc. I think the goal of the company is to align everyone around empathy for the drivers (I presume you're all already customers), so that you make those decisions in ways which enable engineers to deliver software well.

We don't really know what happened here, because as far as I can tell the OP didn't actually engage with anyone to understand what was happening. It seems most likely that the company needed to focus more on one project than another for a little while. That is not the same as stalling something intentionally. It's hard for the company to have empathy if the person didn't elect to communicate their thoughts and feelings.

The company made an offer. The person accepted it. Nothing notable about the scope of the work changed (at least as detailed in the blog post). The person wasn't stiffed or otherwise cheated. They just... didn't like a job offer which they themselves accepted.