Nope, sorry. I just break my code into neatly grouped chunks, and I'm very consistent
I regularly go "I need something to do X", and when I go to write it it's already there. It does exactly what I need it to do, otherwise why would I name it X and not X_for_situation_y? I would never
My utility functions are reusable, my classes handle their own logic internally, and so my business logic is clean and readable. My code flows straight and clear, along a single path whenever possible
So yeah... When I start working with people, there's the initial confusion then this moment where they go "Oh! That's really easy to understand"