06:40 It's been it's been steady, and it's been steady enough that I will keep it up. That's why, I rewrote it, and I rewrote it with the intent of making sure that it was, it wouldn't go out of date fairly fast, and then it would I could be able to keep it up. And it does reasonably well, but it's not like I can quit my day job or anything. So, okay. So that was number 1.
31:38 Yes and no. So like I said, so most of these things you can set up with a config file. And so when I was adding support, I was like, you know, I was like, okay. I'm gonna work on deployment this month, and I'm gonna, like, I'm gonna go figure out what the top five platforms are, and I'm gonna support them all. And each one took, like, you know, like, a day to sort of troubleshoot and and figure out how to get it working.
35:45 Like, tail end is, like, you should never have a class for, like, a card or, you know, a button, And instead, you should have, like, 20 classes that say, like, prime text color red, you know, margin 2 REMS, padding this much, shadow this much. So, like like, literally, like, a button in tail end will often have, like, these, like, you know, I'm not even exaggerating, maybe, like, 20 class names, which sounds crazy and and is often very jarring for people who who start development. It is somewhat mitigated by a library called Daisy UI, which Pegasus uses, which Daisy UI is kind of like a bridge between tailwind and bootstrap. And so Daisy UI will actually provide a button class and, like, a primary button and a error button and whatever. And behind the scenes, it it just maps that to, like, you know, the 20 tailwind classes that you would want.