sky_rw

You don't find this creepy at all? She googles something on her phone. Gets near me, and my phone suggests driving to the location she googled? We aren't on the same account or anything. Google just assumed that I wanted to go where she wanted to go and shared her private searches with me. What if she had gotten in the car and planned parenthood had come up as suggestion?

If you listen to it and get your knowledge first hand, you will hear a detailed explanation of exactly what he was doing with all these powerful people.

It's not wrong, but the mob has come for him and having any contrarian or critical opinion of this movement is career suicide.

My gf googled a Mexican restaurant neither of us had been too on her phone and when we got in my truck literally 5 minutes later android auto maps on my phone suggested it as a destination. If they can do this, they can get your other email addresses.

Superhuman paying customer here. For starters, they are not equivalent products because Hey.com is client + server. Superhuman is an app that sits on top of an existing Gmail account.

I have no problem paying for Superhuman. I use it exclusively for my business email and the way I see it, if improving my email management lands me one single customer it more than pays for itself.

As far as paying in general, I enjoy the feeling that this product won't die off in the same way so many clients have before. Hopefully they are able to build a sustainable business and support a reliable product. Superhuman also has outstanding customer support.

Secretive?

Sadly a valid point. However, I would submit that as a business you are less susceptible to the "silence is violence" attack than an individual would be. But who knows, the times they are a-changin.

It's always fascinating to me how the most liberal and progressive areas of our society are the ones who exhibit the most functional racism.

This is the manifestation of the bigotry of low expectations that is so engrained in Silicon Valley. When you live your life grouping people of a certain skin color into a protected class that you the hero white person need to save, you automatically assume that every person you see of that class is of diminished status.

:shrug: people are mad because they don't want to admit that that Trump still has a real shot. Or they just assume that anybody who even tables the idea is racissss. Oh well.

My friend, you may not be aware that there is an election in a few months. This chaos will continue to escalate all summer and into the fall. Then once Trump wins re-election your really gonna see some slacktavism.

The best thing about running your own business is never having to deal with people like this. It's vastly under appreciated equity.

I had originally signed up due to the availability and pricing of bare metal servers and the mixed Windows/Linux server offerings. Their windows server licensing was better than AWS and I didn't want to be on Azure for a variety of reasons.

Currently on them because we have an OpenVPN based infrastructure that is very challenging to migrate.

Lastly the majority of our customers are in the midwest or Texas, and the proximity of their Dallas DC was a huge performance win for us.

Their status page also seems integrated into their internal support ticketing system. It's not a traditional status page. They wanted to maintain a consistent garbage interface to keep it inline with the rest of their administrative service.

These are the same people who recently published a white paper on how they guarantee zero downtime: https://cloud.ibm.com/docs/overview?topic=overview-zero-down...

The idea that they could even get to this point probably seemed unfathomable. It does to me.

The most infuriating thing about this is the ZERO communication coming out of IBM Cloud. No emails. No updates to twitter. Status page down. Support lines clogged.

At least give me something I can point my customers at to show them this is not due to my incompetence.

I can't think of a better comment to prove my point.

Every time I see comments like this, and no direct offense intended, It always strikes me as coming from somebody who has never filed large insurance claims before. Been seeing this so much with riots lately, "oh you have insurance right, why you mad about your business getting destroyed?". If only it was that simple.

Important distinction lies between "life-or-death" and "perceived life-or-death". The leeway given to police over civilians in this matter seems at the root of a lot of these issues.

Similarly, I have several friends working on wall street who flat out refuse to discuss anything related to a stock over email. Every discussion with them no matter how trivial is on the phone.

This was likely just as much about credit card fees as it is about data.

Stripe's amazing service also comes at a substantial premium. For a high-volume thin-margin company like Lyft where every penny counts, per transaction fees at 2.9%+ are killers. Furthermore, large companies prefer to own the raw card data themselves as the interchange rates for card not present debit cards is different than card not present credit cards. Once you hit a certain amount of scale this .15% difference is substantial.

(edit: I missed that parent comment was about trust in a 3-person startup, but point is still somewhat valid)

The fundamental concept that is missing from this post is that it's not the billing method that determines the success of the business, it's the value you bring to your customers. The service provider isn't going to update anything if they shut down 6 months after launch.

People seem to have forgotten or not realize that SaaS is just a sales model to sell a $2,400 software product for $100 on a payment plan without requiring manager approval. If you can't find anybody who will pay you $2,400 for this product, then you won't be able to build a business selling it for $100/month.

This is not at all like when restaurants throw away food. The key distinction here is is that the bikes are getting recycled. They will be broken down and sold as scrap materials.

I believe this was heavily referenced in his original 4-hour work week book, where he describes his early businesses.

Yeah, it's far from a black and white issue. I am by no means against single tenant database structures, and for our initial use case it was likely the correct decision. I have not run into anything that stopped us in our tracks.

My pushback focuses on two things:

1: The Rails implementation of this, specifically with off the shelf gems and integration with ActiveRecord. Presents a lot of unknown framework complexity down the road. We are currently running on a fork of the Apartment gem as it breaks under newer versions of Rails.

2: Long term support for evolving business case. Now, this is very much a problem unique to our company and how our business/product has evolved. We started out with a very clear separation of account concerns, and as we've grown and pivoted things have changed. You are unlikely to experience the same evolution we have. HOWEVER, all startups face these unknowns, and giving yourself as much flexibility early in the game will pay off down the road. There are no right answers here, you just have to think it through and weigh the costs/benefits. Maybe for you that flexibility is found in single tenant. For us it appears in hindsight that multi-tenant would have been the best long term choice.

For me it falls into the category of decisions that are easy to make and difficult to un-make. If for whatever reason you decide this was the wrong choice for you, be in tech needs (e.g. rails) or business needs, merging your data and going back into a codebase to add this level of filtering is a massive undertaking.

My startup currently does just this 'at scale', which is for us ~150 b2b customers with a total database footprint of ~500 GB. We are using Rails and the Apartment gem to do mutli-tenancy via unique databases per account with a single master database holding some top-level tables.

This architecture decisions is one of my biggest regrets, and we are currently in the process of rebuilding into a single database model.

FWIW, this process has worked well for what it was originally intended to do. Data-security has a nice db level stopgap and we can keep customer data nicely isolated. It's nice for extracting all data from a single customer if we have extended debugging work or unique data modeling work. It saves a lot of application layer logic and code. I'm sure for the most part it makes the system slightly faster.

However as we have grown this has become a huge headache. It is blocking major feature refactors and improvements. It restricts our data flexibility a lot. Operationally there are some killers. Data migrations take a long time, and if they fail you are left with multiple databases in different states and no clear sense of where the break occurred.

Lastly, if you use the Apartment gem, you are at the mercy of a poorly supported library that has deep ties into ActiveRecord. The company behind it abandoned this approach as described here: https://influitive.io/our-multi-tenancy-journey-with-postgre...

Happy to expand on this if anybody is interested. It's currently a cause of major frustration in my life.

Honestly I thought this article would be one line: "Rewrite everything to something else."

It's turtles all the way down.

"one of the worse economies of all time". What economy are you referring to? Are you launching a SaaS in Venezuela?