Adam Leventhal

rigorous artifacts and i think that you can make an argument that that the world that the software rewrite is going to kind of bifurcate adam some of it is going to be your javascript in your static site generator which which to quote your own language back to you you quote do not give a shit about my my mistake correctly i stand by that uh and but then in order for like the

Underneath that is now these rigorous artifacts that we actually, in a world where we're doing much more software, we actually need these rigorous artifacts to actually work much better.

And, you know, I think that like, because Adam, I mean, I, and I think this is like with the, for, this is like the fossil time hour, Gen X fossil time hour, where maybe we can knock down some things on people's bingo cards.

But when you talk about like software in the 90s sucked,

And operating systems had bugs that you would hit frequently.

Compilers had bugs that you would hit frequently.

And the, I mean, what ultimately like the day I put C++ down is because I was dealing with two different compiler bugs simultaneously.

And just like the, and then getting basically random results.

I was just, and that was common in the 90s.

And, man, like, go have a compiler bug to really, like, take the wind out of your sails, let alone two of them.

And we needed to get to a world where we had open source artifacts that we could make much higher quality.

And the quality of software went way, way, way up.

As a result, we could do more of it.

And, man, boy, do I see that happening vividly here.

Yeah, totally.

I think, and Rainer, but you're also right about the dominant narrative.

And I was trying to think about, I mean, clearly it is truly a dominant narrative in that it's dominating kind of everything.

And Adam, I was trying to think back in terms of our careers.

When have you had these kind of like big narratives where it feels like it's reductive?

You know, one thing I was thinking about was the rise of Java was that way.