Ie. amortize expensive work over many requests.
754 karma · joined January 4, 2019
Ie. amortize expensive work over many requests.
It introduces a whole distinct type of complexity into operating the server.
The latency of a request to your server is not just caused by the code that is ran to serve that request (which is how people intuitively would think about it), it can be caused by GC pauses that are happening because of the memory pressure caused by previous requests.
I agree with that. I think looking back on it, Go arrived on to the scene at a perfect time where lots of people were rearchitecting so there was lots of natural appetite in the industry for a new language. Go vacuumed up a lot of this opportunity but ultimately hasn't really evolved the practice of software engineering all that much.
Im glad you said that and I was not just imagining that myself. I remember following the Go language closely in its earlier days and it was often spoken about as a "systems language" but it actually seems to have ended up settling as a language to write servers for people who are sick of OOP but still like their imperative C style code.
What vision? People in Europe drive cars. The cars are smaller and things are less sprawled out than in the US, but people still drive. Europe is not just central London or Barcelona.
Thanks for sharing this, I think you are probably "right" even though what you said is not an easy/popular thing to say.
What is your observed sample size on this? Could you elaborate on how you see people stagnate, and why you think this might be?
The defending team is then forced into either committing more defenders into the overloaded side (and leaving 0 or 1 defenders to cover the lone winger) or staying symmetrical and thus likely not impeding the buildup enough.
This is basically how Italy played in the Euros, overloading the left and leaving Chiesa open on the right thus creating valuable opportunities for him to take on a defender 1:1 with lots of space behind them.
This is probably the best you can do if you want to have high possession without constantly running into brick walls.
Impossible to achieve for a broker, yes. Combination of at least once delivery everywhere upstream and deduping in the consumer gives that consumer exactly once processing.
Lots of people don't grok that and they can be duped into buying certain products with claims that they offer "exactly once". Kafka does or used to do this, SQS (FIFO) also gives this false impression although they are a little more subtle about it. As soon as 1 vendor does it, they all have to do it.
"Did you hear Rabbit doesn't dedupe messages?!"
I am just speculating here but I doubt that YouTube migrated to Spanner so that they could do cross-server transactions. I would think consolidating the Ops burden into the GCP org and also serving as a trophy "customer" were higher on the list of reasons. But again, just speculating...
"the following question comes up a lot:
“So… do you use Kubernetes?”
This has been asked by current and potential customers, by developers interested in our platform, and by candidates interviewing for roles at Ably. We have even had interesting candidates walk away from job offers citing the fact that we don’t use Kubernetes as the reason!"
Why do you think this is an "edgy blog post"? This is a piece of Marketing, both recruitment and regular. The implied subtext of the post is: "we don't use Kubernetes but its not because we don't know what we are doing".
Separately, what does having studied distributed systems or not have to do with Kubernetes?
Maybe "Logical-Request-Identifier" and "Physical-Request-Identifier"?
Idempotency is an emergent property of a system so it doesn't make sense that a client would dictate the key that's used to provide that behavior. So if the Idempotency-Key is quite likely not to be the actual "Idempotency-Key" in any sufficiently complex system, then don't name it that.
Totally agree. "Don't burn bridges" is also such common, banal advice that it's strange the OP is writing it as if it's a contrarian opinion.
For every story like the OPs there are probably hundreds or thousands of people who tacitly perpetuated bad work conditions instead of "burning bridges".
Why can't the auditors explicitly state what needs to be auditable about io_uring? Instead of guessing and debating.
It was a satirical observation (based on my experience) that "the business" tends to scoff at unsexy foundational rework of existing tech. The trendiness of Kubernetes is used effectively to "trojan horse" that kind of work in.
I am jokingly suggesting that at this stage maybe that's the real value of Kubernetes.
"I need X million USD in engineering spend this year because we need to be on Kubernetes".
"I need X million USD in engineering spend this year to fix half a decade of awful technical execution and decision making (that all happened under your watch, BTW)".
It's very draining and I resent that the industry classifies this type of work as technical IC work. A small subset of these higher "IC" roles do get to focus on technical IC work, but for most people a staff/principal role is basically going to be that of a co-manager with no authority.
I've been considering down-leveling or getting into some software niche where technical expertise is actually valued and existentially necessary to the business.
I don't even mean to single you out because I've seen this type of thing countless times on here and especially on Twitter over the last week or so.
"What's more interesting is the awkward situation they have created, which I'd argue is a false dichotomy - where does "societal politics" end and "politics that directly relate to our business or products" start?"
That can be tricky, which is why the policy is not zero tolerance and they already anticipate and are OK with people sometimes getting it wrong.
Why do you think that's the policy? Did you read the blog posts?
According to DHH's post, political discussion that is related to the business is allowed. Any other political discussion is encouraged but must take place in a dedicated non-work channel. The policy is also not zero-tolerance.
No it's like raising a baby using advice you read from books that are peer reviewed and revised over time vs. just listening to what your parents say.
If it's disseminated via oral lore it's expensive to change and is often misinterpreted across a large enough org.
A silent killer of engineering orgs is bad practices that stick around because that's the way it's always been done. No one knows why because it wasn't written down. The only way to fix that is for someone high enough to provide blessing, but maybe none of those things are individually disruptive enough to get the CTO involved. So everyone eats the costs in perpetuity.
Much easier to just write everything down.
Increased difficulty for juniors to ramp up when you are remote is a symptom of a culture with lots of overly complicated processes that are not well documented.
If you are doing rent to buy but living in frothy areas where rents are always rising and apartments rent for 4k then obviously it's not going to be a winning strategy for you.
Once devs have worked on a particular system for long enough, they become a nuisance because they know all the (good) reasons not to do something. Not necessarily because they are lazy / don't want to grow.