blaisio

One could argue that all they did was move most of the complicated logic into the blob store. Not that it's a bad thing.

Haha I meant panic as in become scared, not the go panic.

Go is my default language for any non-client-side project. That said, I agree with all the criticisms, except for the one about unused variables/imports and the lack of warnings in the compiler. I'd also add one of my own - I'm an expert go programmer, but I still panic sometimes when dealing with error handling. It is still not as easy as it could be to produce useful error return values.

No, sorry but I don't think you understood the article. Readiness probes don't fix this. In fact, they could exacerbate the problem (although you obviously need them anyway). The problem is Kubernetes and the Load Balancer react to pod status changes at different times. (In fact, it's worse - different Kubernetes components also react to status changes at different times.) The load balancer is almost always too slow to react, so, it sends traffic to an instance that has already started shutting down.

Yes! I think this is a really under-reported issue. It's basically caused by kubernetes doing things without confirming everyone responded to prior status updates. It affects every ingress controller, and it also affects services of type "Load Balancer" and there isn't a real fix. Even if you add a timeout in the pre stop hook, that still might not handle it 100% of the time. IMO it is a design flaw in Kubernetes.

Op should really delete this blog post. It has a lot of details that could be used against them in court.

Actually, it is normal for there to be dilution in each funding round, including an IPO.

I agree spanner and cockroach are the future. Most people don't need a database that can scale that well, and spanner is too expensive to use unless you really truly need it. Also, google and cockroach have not done enough marketing. Look at all the marketing mongodb did - they actually managed to convince people to use a database that would regularly lose data.

The WJACTV article you referenced literally includes a response from the department of state and an explanation of the discrepancy.

Either they are too stupid to know you can't attack people and break into buildings, or they did it on purpose. Either way they can't be effective as CEO after that.

People were indeed arrested and fired for looting in protests earlier in 2020.

In case someone is curious, the optimization they describe is trivial to do in Kubernetes - just enter a resource request for cpu without adding a limit.

I'm not sure what you're trying to argue for here, but if we had allowed a huge initial spike, many hundreds of thousands would have died needlessly. We are still doing much better than that.

Yeah space really isn't the problem at all. It is nurses and doctors and oxygen. They have nurses - who are supposed to treat 2, maybe 3 at a time - treating 30 people at a time.

Prop 22 is a tremendous success for Uber and other companies. The courts and legislature in CA went out on a limb to force Uber and others to do the right thing, and prop 22 erased all their work.

If you don't live in California, you may not know - they added a $1.50 fee to every order, in addition to all the existing service fees and delivery fees, which often add up to 20-30% of the order. (Also by the way, uber and grubhub already artificially raise the prices of items on the menu and keep the difference, and restaurants can't do anything to stop it). They can blame it all on Prop 22 even though they spent millions to pass it.

Now obviously people are paying all these fees, so it appears that drivers are being paid a lot, so no need to tip. But most drivers don't even qualify for the money! We are paying money on orders that probably won't even go to our own driver.

Personally I've decided to stop using these food delivery apps. I can't stop using Uber, but I can pick up my own food. It is depressing that so many delivery drivers didn't understand what they were voting for and did nothing to stop this

I disagree that it is overkill.

You have to think about it like this: the average skill level of engineers at a large company will always move to the true average across all engineers outside the company. This means they have engineers that don't know what they're doing, and there's not much they can do to prevent it. The average "security" skill level is very very low, and even people who are good at it make huge mistakes constantly.

If you accept that, then it makes sense to spend time and money on preventing people who don't know what they're doing from hurting everyone else. It is therefore essential that mitigations like this are applied, even though if everyone did their job perfectly, they would not be necessary.

Hmm one thing that jumped out at me was the organizational mistake of having a very long automated "grace period". This is actually bad system architecture. Whenever you have a timeout for something that involves a major config change like this, the timeout must be short (like less than a week). Otherwise, it is very likely people will forget about it, and it will take a while for people to recognize and fix the problem. The alternative is to just use a calendar and have someone manually flip the switch when they see the reminder pop up. Over reliance on automated timeouts like this is indicative of a badly designed software ownership structure.

I have nothing directly against cloudflare but I think it would be better to try to support one of the smaller analytics companies if possible. They are the ones who made products that got big companies like cloudflare interested in the space.

I do the same thing with the timer app. I've only worked more than 8 hours when there was a tight deadline. I was surprised by how exhausted I felt on those days. On a normal productive day I get 6 hours, on a day where I feel shitty I get 4 hours. I was actually surprised by the amount of work I get done with only 4 hours of focus per day - no complaints from my boss or anyone else

I had around $12K in savings. Enough to cover a year of expenses and a bit more. I stopped spending money on almost everything.

Yeah, that sucks. I'm sorry you had a bad experience.

I think one thing for the community to take away is you need to be in a good position financially before you can start a startup - unless you can get funding. Especially for indiehackers who don't usually take outside investment, $12k in savings is not enough. It is not normal to have to stop going out at all or to be pinching pennies. Not everyone can afford to start a startup. For some reason, this concept is almost never talked about in the startup community, but it's really important.

Are you seriously shaming them because you think they have social anxiety and you don't think they took a big enough risk?

Google Cloud Run doesn't provide nearly the same features as Heroku. For example, there is no easy way to manage secrets with Cloud Run. There is no way to run a worker process. Integration with other Google Cloud things like Cloud SQL is clunky. Cloud Run is okay to get started but almost all apps will need more.

The point is they create a huge amount of hassle for users by constantly killing/replacing/renaming products, and it also shows that they aren't doing any effective long-term planning. That's what makes people mad.

Angular: I agree that angular is not dead, people can still use v1 if they want to. This does not count.

Hangouts: the new version has different pricing, different features, different name, different URL, different apps... this absolutely counts (and is one of the most egregious examples)

Password checkup: the extension worked fine, but they intentionally disabled it. Any references to it on the web now have to be updated to refer to password checkup in the browser. Anyone who knows how to use the extension has to relearn how to use it in the browser. This counts.

Google Photos Print: yes the original was stupid, but it was still a product and is now gone. This counts.

Shoelace: yeah this never really launched in the first place. This doesn't count.

Google Chrome Apps: I mean really? Anything that requires rewriting parts of an app to make it work counts!

Dragonfly: this was never released, it doesn't count. But it is important that people know about this, it is an example of Google quite blatantly being evil.

How do Googlers actually feel about all this? It seems to me that a lot of the reason you work there is the benefits at their offices. If they are cut, then it's like getting a pay cut.

I don't think it's a big deal, but I was confused for a minute, because sus in English slang is short for suspect/suspicious.

It has to be written in Go because Cockroachdb is written in Go.

Realistically the biggest problem with Rust today is the biggest problem it has always had - it is too hard to write useful programs. Rust has seen some success in very targeted use cases, but that isn't enough. I am 100% confident that introducing Rust to my company would be a huge mistake.

TOML sucks in so many ways. It is about 8x better than YAML, INI, or JSON though. It is good enough that I can ignore its flaws.

I think this is meant to try and make it more of a political issue. Of course the problem is I don't think most regular people care at all if Microsoft or Amazon get the contract. Actually many regular people would probably prefer nobody get the contract.

In other words, this comes across as a hail mary.

To be fair, Trump probably did cause the contract to go to Microsoft.

I don't get the GitHub Container Registry, GitHub Package repository, or GitHub Actions. The only good thing about these products seems to be integration with GitHub. But in many ways they are inferior to other CI and artifact hosting options. The biggest problem is the latency will be significant outside of your own network. The other big issue is security. That's fine, they are new products... except they don't seem to be moving in a direction that would fix these problems. I think maybe a lot of programmers don't realize what they're missing, they're just using them because they're from GitHub.

GoodRx does not sell anyone's data.