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.
Readit Newsblaisio commented on Husky, Datadog's Third-Generation Event Store datadoghq.com/blog/engine... · Posted by u/louis-paul
blaisio commented on Experience Report: 6 months of Go typesanitizer.com/blog/go... · Posted by u/eatonphil
Indeed. panic is not overly recommended but there's a few places you can nudge it in that just make sense, rather than ensuring the error will successfully propagate up the chain.
Haha I meant panic as in become scared, not the go panic.
blaisio commented on Experience Report: 6 months of Go typesanitizer.com/blog/go... · Posted by u/eatonphil
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.
blaisio commented on Problems with “graceful shutdown” in Kubernetes (2019) philpearl.github.io/post/... · Posted by u/richardfey
btw. this can be fixed with readiness probes. and applications should implement them.
i.e. application still gets traffic, readiness probe fails because of SIGTERM, application will respond with an error on the probe, the loadbalancer/service sees that and removes the endpoint/service the application can still respond to the inflight requests since it should not stop directly on sigterm, if everything inflight was done it should stop.
(this also works with non http, if SIGTERM is handled)
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.
blaisio commented on Problems with “graceful shutdown” in Kubernetes (2019) philpearl.github.io/post/... · Posted by u/richardfey
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.
blaisio commented on I will not exercise my Gitlab stock options (2017) web.archive.org/web/20170... · Posted by u/Elof
They would get diluted if the company did something like a three for one trade (which happened to me and I know Gitlab did not), but in the case of an IPO there isn't dilution. Dilution matters when a company is getting bought by another company.
Actually, it is normal for there to be dilution in each funding round, including an IPO.
blaisio commented on GCP Outpaces Azure, AWS in the 2021 Cloud Report cockroachlabs.com/blog/20... · Posted by u/mohangk
I don't quite understand why, but much of the tech industry seems to be sleeping on Cloud Spanner. Google quietly completely revolutionized managed+consistent+available+scalable RDBMS and very few people seem to have caught on yet. Maybe it's too much of a threat to job security?
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.
>you didn't agree with the outcome of an election?
There were numerous attempts to have the government look into possible cases of voter fraud. Most court cases were thrown out due to issues of standing and not because presented evidence was rejected. There are real irregularities which are either ignored or given the "nothing to see here" response by the people who should be investigated.
For example, these allegations were met with a non-response by the Pennsylvania Department of State: https://wjactv.com/news/local/pa-republican-lawmakers-analys...
You might like this analysis of mail-in ballot discrepancies for the Michigan county where Detroit is: https://mapthefraud.atlassian.net/wiki/spaces/DATASCIENC/pag....
The WJACTV article you referenced literally includes a response from the department of state and an explanation of the discrepancy.
So he walked inside the capitol building, a building that protesters have walked into without repercussions many times in the past, and got fired for it. Does he have a history of violence, or was he in the wrong place at the wrong time? Cogensia sounds like the kind of company that cares more about skewed-optics than about the truth of the matter. I didn't see news articles about rioting looters getting fired for their participation in "mostly peaceful" protests.
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.