I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made.
I’m more and more convinced that all of AI engineering is Neijuan (内卷, meaning curl inwards). In China it describes a system that demands ever more effort and competition without improving output.
The language now is English. It's a cliche, but it's also true. Like I've been programming in English for the last three months. I've been reading a lot of code, but I'm programming in English. I'm telling the computer what to do, and I'm using natural language, and it is shockingly even more delightful. If there is one programming language more beautiful than Ruby, it is the English language.
We did the the numbers and the numbers are more like 0.3%. We scanned all 67,000. We shipped the we shipped the paper. But you know a correction never travels as far as a scare.
You know features are the fun part. A new feature is is just a prompt away. The real cost comes after every feature we shipped of course with a configuration option because we didn't want to break everyone's setup.
for us design actually has always operated as like a bottleneck at the company, which is incredibly important, right? It's intentional that things need to be approved by design to ship.
But I have come to realize that as a web developer, Linux is just better. Linux is just better. It's closer to what I deploy on. The tooling is actually phenomenal.
Their words now
anyone who's working with the web, who's working with Ruby, who's doing DevOps, they should be on Linux because first of all, that's closer to what we deploy.
The joy of a programmer, of me as a programmer, is to type the code myself. If I elevate myself, if I promote myself out of programming, I turn myself into a project manager. A project manager of a murder of AI crows as I wrote the other day.
Their words now
I have been hyper accelerated as a programmer. It's a different kind of programmer, but it still has the same affinity to aesthetics, at least when I'm producing Ruby code.
Let's say if my requirement for the engineer was build a system that will scale infinitely to the test of time, it might take a year. We never get there. We'll die before then.
In fact, innovation died on the vine like all together and since I don't know, 2008, there has been no innovation from Google. It's all been acquisitions. They have they've created nothing new.
When applications can generate capabilities on demand, the definition of "what this product does" becomes more fluid. Features aren't just what shipped in the last release, they're also what users will ask for in the next session.
And then I found a smoking gun: October 1943. Kuhn acknowledges that he receives half a gram of ergotamine, which is the precursor drug to LSD. And so it's highly likely that the Nazis used LSD together with mescaline in Dachau.
static typing is the one thing I will literally die on the hill for for Ruby
Their words now
It's the essence of what makes Ruby Ruby. This is why I don't fully understand when people call for Ruby to add static typing. 'Cause to me, it's the bedrock of what this is.
They could have shipped ChatGPT for example, I heard, in 2019. And they never shipped it because they were so stuck in bureaucracy. But they had everything. They had the data, they had the tech, they had the engineers and they didn’t do it.
And for a long time, I thought that's what had worked. That this was why Ruby on Rails took off, became one of the most popular full-stack web frameworks of all time, inspired countless clones, and created hundreds of billions in enterprise value for companies built on it. But I was wrong. It wasn't the crusade that did it.
That makes it essential to ensure that all synthetic DNA orders are screened to determine whether they contain hazardous sequences, which should be shipped only to legitimate researchers whose work has been approved by a biosafety authority.
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.