> Interviewing is mostly a different skillset from day to day work. > It’s not, really: Funny -- I'm halfway down the page now, and haven't seen your top-leve

> Interviewing is mostly a different skillset from day to day work. > It’s not, really: Funny -- I'm halfway down the page now, and haven't seen your top-level post stating how and why the entire point of TFA is wrong. > this could be true if your day to day work is writing very basic websites without real performance or scale constraints, but if you are building large, performant systems, a good technical interview will give you a chance to show those skills. Yeah, that was the point: Most day-to-day jobs are writing basic websites without huge scale constraints (or equivalent), but interviews are usually conducted as if those huge scale constraints were relevant. Do you have some particular reason to believe that most actual jobs do involve "real performance or scale constraints"? Or that interviews aren't conducted as if they did? (Or did I somehow miss the point, and that wasn't what TFA was all about?)