Marc Brooker

Um, and so I saw one of, you know, your early conversations with, was with Leslie Lamport, who kind of takes that a step further and say, Hey, you know, it's formal mathematics.

That is the next step there.

And I, I love that point.

Um,

But I think writing is this really accessible thing for people to do that does force a level of thinking.

And so I do a lot of writing sometimes just for myself, right?

Like I'll write a doc, not ever intending to share it with anybody,

but just to sharpen my own thinking on a particular point.

And so it's some of that combination of three things, right?

Like I just have something to say and I want to say it.

You know, I have something to say and I want to scale it out in time and space.

And I want to sharpen my own thinking on a subject or the thinking of a small group on a subject in a way that writing is just a super powerful tool to do.

Yeah, and that's a great point.

And I think it really depends on the level of problem you're trying to solve.

And so if I look at

I'm going to pick on UML for a minute here, right?

Like it's a sort of semi-formal software design process and not one that I've ever found useful because I think it just happens at the wrong semantic level.

I think it's bothered with details at a level that aren't helpful.

And I think a lot of the let's go off and document this has a similar problem, right?

Like, does this actually require that level of reflection and thinking?