I think that this would be particularly useful to gauge the approach of the engineer to coding. Is it practical and no-nonsense? Is it abstractions are everythi

I think that this would be particularly useful to gauge the approach of the engineer to coding. Is it practical and no-nonsense? Is it abstractions are everything and having variable called a and b are a “good idea” because it makes for clever code? Is this architecture tending towards growth or being so unwieldy that in a few months there’ll be nothing better to do than rewrite it? The more time I spent coding the more I realize that I don’t code for myself, I code for my team and if what I’m making is not painfully obvious somebody (including future me) is very likely to break something in the future because they didn’t understand what the code I wrote was supposed to do and how it was doing so.