eshyong

I think they meant the scooters have firmware which can limit the top speed of the rider.

This recently happened to me as well - Venmo tried to invalidate my payment method and pushed me to go through their "instant verification" process. Note that "manual verification" (i.e. the deposit method) is still an option on their app, though you may have to remove your current bank credentials and re-add it.

I see, thanks for the detailed reply. Yeah it's sad that companies have no incentive nowadays to support open protocols (besides the ones that already exist). I wonder if regulation could solve this problem or at least encourage healthy competition into the marketplace.

I see this argument made often on HN, but it's not clear to me how an internet protocol would make social networks more accountable towards their users. Do you mind explaining your reasoning here? Specifically, how would a protocol prevent motivated companies from tracking your personal information?

I think the issue isn't that they're spending money on an order in the moment, it's an auto-renewing subscription that users may not even remember about.

From the last paragraph:

> Strict modules are still experimental. We have a working prototype and are in the early stages of rolling it out in production.

Sounds like it's in-house to me.

What language was the team counting in nanoseconds using?

It's satire written by a disgruntled engineer :P

It seems like payment/e-commerce companies in general are shifting towards offering "express checkout" experiences nowadays - Shopify, Paypal, Amazon Pay, are a couple prominent examples. My former employer Affirm was also very concerned about owning the checkout experience/acquiring users up-funnel. It's a smart move, really.

My impression is there are a segment of technically-minded backend engineers who look down on frontend work - who cares what the damn thing looks like as long as it works?

I think the truth is, most engineers just aren't comfortable with A) working with stakeholders and translating requirements to specs, aka soft skills, B) any sort of design (which is actually hard!) or C) learning the HTML/CSS/JS ecosystem. Also, I found learning how to write frontend applications to be just as challenging as writing CRUD apps.

Except that in Go, you always return the error alongside the value, like this:

    return 0, errors.New("unable to get price")

It's less elegant than Options but still, very common practice. GP's company clearly hasn't bought into Go if they're using a library that doesn't follow well-known conventions.