You'd only need to do this in the scenario of an all day (or longer) interview, which in itself is something you should not enter into without some pretty good feelings developed from the preliminary/phone interview.
In this case it sounds like a fairly conventional "business" type guy didn't like the idea of working in a open environment with a bunch of kids wearing jeans. But that kind of basic "what's your work environment like" information should have been known or ascertained by him before accepting an invite for an all-day on-site interview.
In rare cases you may realize during the final screening that there's some fundamental incompatibilty, but if you do your due diligence in the preliminaries this really shouldn't happen.
Having to walk out of a final interview means that both sides executed the initial screening poorly.
I am a programmer with 10+ years exp who wares a tie every day to work. Reading though that though I see a lot of red flags that have nothing to do with the dress code. Honestly, using a custom ORM solution is a sign of incompetence. Frameworks seem easy and fun to people that don't understand them, but after a few years I think about such things a series of trade-offs not an interesting problem.
A few moths ago a coworker with ~5 years exp wanted to write their own simple graphing library to get around a few problems, everyone in the office said have fun do it on your own time, but don't add it to the code base. He had fun and it was a great learning experience, but the idea of working where most people where at that point has little appeal.
PS: 15 years ago there where a lot of great reasons to write your own framework, now days not so much.
My worst interviewing experiences have all involved HR initial screening. "The tortoise lays on its back, its belly baking in the hot sun, beating its legs trying to turn itself over, but it can't. Not without your help. But you're not helping."
My best interviewing experiences have all had no HR involvement at all (ex-coworkers introduce my soon to be future boss to me at lunch, met my future boss at a industry get together, etc)
In this case it sounds like a fairly conventional "business" type guy didn't like the idea of working in a open environment with a bunch of kids wearing jeans. But that kind of basic "what's your work environment like" information should have been known or ascertained by him before accepting an invite for an all-day on-site interview.
In rare cases you may realize during the final screening that there's some fundamental incompatibilty, but if you do your due diligence in the preliminaries this really shouldn't happen.
Having to walk out of a final interview means that both sides executed the initial screening poorly.
Edit: typos