26 korrents from this recording
Every claim below is a statement made in this recording, quoted word for word and linked to the second it was said, so you can hear it rather than take our word for it. The wording comes from the transcript published alongside the recording; the sentence above each quote is our reading of the claim, not their wording.
0:07:24 · watch on youtube.com↗
Our reading
Team output is still what matters, however hard the industry pushes to measure individual output.
Their wordsI also believe that, you know, there's been this whole push towards individual output, but teams are still what matter. Teams output.
0:08:01 · watch on youtube.com↗
Their wordsWe can go fast. Let's do same thing faster, you know, just boom. And I've come to feel like that is a very immature description of what better is.
0:10:31 · watch on youtube.com↗
Their wordsAnd it wasn't actually the models. It was the harnesses. It was all the tooling.
0:12:04 · watch on youtube.com↗
Their wordsWhat I was saying in that piece though was, I think we were right to be skeptical that time. But now, I see the same thing playing out with would you be willing to ship it some code you didn't read? There's no point in arguing about if it will happen or when it will happen. Talk about what it would take.
0:14:55 · watch on youtube.com↗
Their wordsI mean, if you if you think about it, you could generate 10,000 variants of a function faster than you could write it once.
0:17:03 · watch on youtube.com↗
Their wordsLike that just does not seem like the ideal artifact. We should be able to store them somewhere. We should be able to have architecture diagrams that we can review and discuss that generate that code to spec.
0:20:22 · watch on youtube.com↗
Their wordsit's always weird to me just how much software engineers really seem to believe that the world exists in the repo. It doesn't. It's production, you know?
0:21:02 · watch on youtube.com↗
Their wordsProduction is not what happens after development. It is a stage of development.
0:22:03 · watch on youtube.com↗
Their wordsAs soon as you merge, it should be going out. You like you should have to stop the train to make your code not go into production as soon as you've merged.
0:26:36 · watch on youtube.com↗
Their wordsIt's like they have all the wisdom of their most senior engineers looking at every single diff and that is fantastic. Which means that you don't have to worry about remembering and looking and nitpicking and all the things that we're not good at anyway
0:28:02 · watch on youtube.com↗
Their wordsOkay, if I'm not going to read this code, how do I know it's going to perform within boundaries of the last code that I generated? That is conformance testing.
0:28:26 · watch on youtube.com↗
Their wordsIf you're debiting from this trust account in the creation of the code, it has to get built up somewhere else.
0:32:00 · watch on youtube.com↗
Their wordsAnother another thing we point out is just there is no human in the loop. You own the loop. The loop is yours. The loop is mine. It would not exist if it was not for me. So I am the owner, right?
0:34:55 · watch on youtube.com↗
Their wordsHere's a baseline. Uh you cannot send anyone something you haven't read. And in fact, if it would take them longer to read it than it took you to make it, it's probably slop.
0:36:42 · watch on youtube.com↗
Their wordsYou can use AI as a shortcut to help you not have to think too much. And you can use AI to help you think more deeply and more rigorously. And both of those use cases have their place. But when it comes to your core job function, we primarily want the second one, right?
0:38:17 · watch on youtube.com↗
Their wordsSee, the problem is that neither side is making it up. Like they are seeing really scary trends.
0:39:28 · watch on youtube.com↗
Their wordsOne of the things that's ironic though is that both of these sides feel like they are the tiny minority and they're outmanned and they're being suppressed and they are standing up for what is truth and valor in the face of the big AI folks or the big skeptics.
0:42:30 · watch on youtube.com↗
Our reading
An account of an AI win is not worth publishing unless it is coupled with what that win cost.
Their wordsIt's like we need to hear the wins. We need to hear what's We need to hear about what's possible. We need to hear what's exciting. But you got to couple it with the costs.
0:44:49 · watch on youtube.com↗
Their wordsSoftware is made of logic and language. AI is made of logic and language. And because of that, we can bake in guardrails.
0:47:20 · watch on youtube.com↗
Their wordsAnd I have decided not to sink anymore because writing is thinking on paper. And there's no shortcut for doing that thinking.
0:50:27 · watch on youtube.com↗
Our reading
You cannot really understand the code you write unless you are also the one operating it.
Their wordsThat was always a bad idea because it's split brain. Half of you are writing the code and the other half are understanding it. I would argue that you can't really understand the code you write unless you're operating it.
0:51:07 · watch on youtube.com↗
Their wordsBut I also think that in my mind, 20 years of DevOps was really about one thing. Trying to create one feedback loop that connected people writing code to that code in production. And it failed.
0:56:00 · watch on youtube.com↗
Their wordsAuto instrumentation has gotten so good in recent years. If you're using Open Telemetry and everyone should be using Open Telemetry. All of the common patterns like all of the models are trained on them. So, it is literally faster and easier to build with instrumentation than to than not to.
1:09:15 · watch on youtube.com↗
Their wordsIf we don't do it ourselves, meaning hold ourselves to a high standard, build with efficiency, constantly be like trying to get better, if we don't do it ourselves, someone will come and do it to us.
1:10:10 · watch on youtube.com↗
Their wordsit's it's not enough to be a good person. I believe that people who are kind and care about people can and and usually do do better than sociopaths in the same roles, but only if they're good at business.
1:16:34 · watch on youtube.com↗
Their wordsThe hardest thing about quantifying the value of junior engineers is that we don't know how to quantify the value of any engineer. So it's all vibes.