i can't imagine the code at any company would really be bad. i _know_ i've inherited shit codebases before, but it's been so long i canny remember. :-D i coul

i can't imagine the code at any company would really be bad. i _know_ i've inherited shit codebases before, but it's been so long i canny remember. :-D i could see certain pieces/modules being shit, but not most of it. i got it - if the interviewers (who are coders) ask you stupid fucking questions, then they're probably stupid/incompetent/lazy/etc. - so i'd worry about their code quality, and the quality of everyone and everything at the company - products, processes, people, etc. outside of that, you just have to get in there and convince them to start coding the _right_ way -- that is, _your_ way. :-D lastly, i have to question the premise a bit - as cliche as that may be. take your hypothetical -- you've got three offers -- how far down the list of pluses/minuses is 'code quality'? * company brand (resume) * pay * location/remote/commute * industry * position * vacation * manager * advancement * potential pay/ipo/etc. * tech stack * etc. * etc. * etc. * maybe codebase quality is here??