Been using Astra for the last few weeks and it’s so good and proactive. There’s a bunch of PRs on vitest, tsx or SwiftPM where Astra debugged OC and ended up finding and patching issues in upstream dependencies.
Immigration depends greatly on who immigrates. And a country benefits when the people who immigrate are net contributors to the society, and in most cases, that they assimilate with the local culture.
go and take the comp required to have five L5s reporting to one L7 and then four L7s reporting to one VP and now total the comp of that product org and turn around and say, what if I had three people?
if you don't actually push yourself down to sit alongside your IC engineers and your IC designers and your IC PMs, you don't actually know that stuff. So you can't make good macro decisions without the micro.
We're now doing it in a much heavier way because we find that these like kind of bory enterprisey uh patterns end up being pretty useful because you have a bunch of idiots on your team now. The coding agents are a bunch of idiots and they are going to work 24/7 and they're going to like ship a lot of stuff. So you need way more guardrails than you used to.
I would say here that the Linux kernel is truly unique in this particular aspect in that they have thousands of contributors doing it on work time. I actually think that the Rust project is doing pretty well at having people do it and get paid for it like by their employer, but it's nowhere near the to the same extent as as the Linux kernel.
The topic of boilerplate code is an interesting one because the mere existence of boilerplate code is a failure of programming language and of the idea of creating software modules.
I started with a rather non-consensus hypothesis: companies want to pay for their critical open source dependencies, but most projects are not selling them a legible way to do so.
So almost if Codex or copilot are helping you, that actually probably means that your framework or library is bad and there’s too much boilerplate in it.
Rather, I think that “the foundation”, as a single point of failure, is structurally at odds with the idea of “the project”, which is inherently distributed.
not only did I buy the canonical reference (The Rust Programming Language by Steve Klabnik, Carol Nichols and community contributors), I also bought an O'Reilly book with a bit more narrative (Programming Rust by Jim Blandy and Jason Orendorff).
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.