HN user

eiopa

314 karma
Posts2
Comments48
View on HN

In San Francisco restaurants, I’ve seen this tactic applied liberally. Maybe AirBnb and DoorDash are rubbing off on them:)

A common one sees the restaurant charge you separately for the employee health benefits, cynically marketing it to consumers as “healthy SF” and “SF health mandate”.

What’s sort of fun is that like cryptocurrencies, you can always materialize new ones out of thin air. One popular establishment demands that you pay a separate “carbon offset fee”.

OMG, "The Screener" is something I've always wanted. There's a lot to love about this.

Something I am nervous about is using a @hey.com email. Similarly to domain, it's a world-visible and sticky, but unlike domains, it isn't portable, the only options are: pay Basecamp forever, or lose access. gulp

State of Loom 6 years ago

This reminds me a lot of python’s gevent.

I often wish the language had adopted it instead of the C#-like await async, since it’s just more straightforward.

The 24/7 support sounds promising. This has been their Achilles heel for many years.

Anecdotally, I once checked into an Airbnb with a leaky roof. After spending a good 20 minutes trying to get to a human (a small eternity when you’re in an unfortunate situation), Airbnb asked that I spend hours negotiating with my non-responsive host on a solution, which is obviously nonsensical given the situation.

Being able to instantly talk to someone and feel like I am being taken care of would have made all the difference in the world. Instead, I churned from their platform.

My personal experience with Airbnb is that they simply don't know how to do support. Even basic issues take multiple days to resolve, and usually involve many phone calls.

HotelTonight has been awesome there. You can get a representative on live chat and resolve most issues while you're still en-route from the airport.

On one hand, I am hopeful Airbnb will be able to learn from HotelTonight, but in reality, it seems most acquisitions end up with the acquired company diffusing into nothingness :(

I'm based in SF, and I've taken over 200 rides with Ford GoBike (operated by the same company).

It is awful.

The bikes: big, heavy and ugly. Due to their sheer weight, peddling up the gentlest of hills will make you question your life choices, and consider other, much faster options, like walking, or just gently slithering around the pavement.

Additionally, Motivate's chosen method of bike cleaning - a dude hosing them down - tends to leave the bikes drenched with ice cold water. I suppose the feeling of freeze gnawing at your body does act as a replacement for caffeine for some, but I find it very unwelcoming.

The stations: Sparse, not well maintained, and honestly, an eyesore. They're this giant, lumbering object that takes away precious public resources, and is only available for Motivate's usage. You also constantly have to plan around them -- is there one next to where I want to go? Is it almost full?

E-Bike deployment: what a joke. They are rarely available, and even you've spotted one of these precious unicorns, you'll often by greeted by a beaming red dot, indicating that the bike is unwell, likely due to the battery giving up in the middle of day.

Other than that, the app spams you with ads, many of which are strangely enough for buying an e-bike. I thought this company is about bike sharing??

I understand people who want more expressiveness in their reviewing, but the reality is that the 5-star system just leaves too much ambiguity.

It's like how in Uber/Lyft, most people just default to 1/5 star ratings. In that case, the average rating a driver has to maintain gets skewed to a a pretty high number, like 4.5, and people who think "oh, this was a pretty good ride! 4 stars!" end up unintentionally boning the driver.

Reminds me of gitx (a good thing!) :)

Is there a way to only view commits that belong in the current branch (like git log)? The commits from the other branches are distracting when you're trying to read the history of a particular branch.

Our own experience with ECS has been similarly negative. While this was 6 months ago, I am not aware of significant improvement.

In general, the whole thing feels rushed and duct taped together. Networking model (inherited from Docker) doesn't play nice with ELB.

- The built-in AWS tools for monitoring are not container aware.

- We've had multiple occurrences of the ECS daemon dying.

- Very little visibility into the progress of deploys. The API/console will report something as "running", when it in fact was still loading up.

If you watch their videos, they promise integration with Marathon, but if you look at the code, it's in "proof of concept" stage.

At this stage, GCE is significantly ahead of AWS. Out of the box, you get a top notch container story, logging and monitoring.

VSCode is so good.

I do wish it had a global symbol search, similar to Sublime's (cmd+shift+r). It's indispensable for code navigation.

It's always been strange to me that tech interviews tend to check for basic CS, rather than deep engineering.

When was the last time you had to implement bsearch() in a real project?

This kills it for me too. I rely on pypy, and I just can't see myself sacrificing my productivity by using Six.

Also, Python 3 neglected to fix one of the most annoying things about the language - default arg value

  def foo(x=[]):
      x.append(1)
      print x
  
  foo() # 1
  foo() # 1 1
Why is this still busted??

there is a huge difference in what they can bring to the table in vendor vs p2p plays.

p2p will presumingly work almost exactly like venmo, or more accurately, iMessage. Not only are they not bringing anything new to the table, they are also not leveraging anything from them controlling the hw+sw, other than being preinstalled.

A vendor play is much more interesting, since this is where they can really shine (completing a transaction without ever unlocking your phone or typing anything).

I feel that they have missed that train. There are ubiquitous products (Venmo), and powerful competitors (Facebook Messenger Pay, or however they call it). If they want Apple Pay to gain traction, they need to make it more useful.

My personal wishlist item is being able to pay at a restaurant with my phone, without ever asking the waiter for the tab.

Right now this requires multiple legs:

  1. Ask waiter for check (first trip)
  2. they go print it out and come back with it (second trip)
  3. I hand over my CC, and they take it to the register (third trip)
  4. They return with my credit card, and now I can finally leave the restaurant.
This is annoying for everyone. The waiter has to do multiple trips to just handle the transaction without providing any meaningful value (as opposed to recommendation entres, for example). For me it's annoying because I want to leave, but I am essentially trapped until the whole dance completes.

A beefed up Apple Pay would be so cool for this scenario.

I really love these, and I desperately wanted to be a Backblaze customer, but I was put off by the abysmal desktop software :(

Storage execution seems top-notch. End-user software deserves some love.