There is a difference between over-engineered and unfamiliar

The problem is that a lot of people come across these modern things that we're doing and um we saw a lot of them yesterday, but people come across them and they're unfamiliar and the first thing that comes up is that's hard to read. I don't even want to know what's going on with it because I don't understand it on first glance. So that's why I really think that these types of things need to be normalized. And this can happen with lots of education, lots of showing people what they are. Patterns like this can become normalized. We just expect them. I know that the this min function used this way is going to be a really good way to help people not run into overflow issues. That's a really cool thing. You can use it all over the place anytime you need it and it's going to work. And if that becomes something that we just see all the time, people know what it is and there's no more issues with it. This is a really big problem though because there's so much friction and as soon as people see code that looks unfamiliar, they put their backs up. I talked to people yesterday in the hallway in between on breaks and stuff and they said they were using logical properties in their code and during, you know, they'd submit their pull request and be told to change it because people didn't know what it was. That's a problem. It works. Just do it, right? And the more we see it, the more we do it, the more it gets normalized.