4 ms·
Sure, because poor management, crippling technical debt, and a toxic work environment are totally plainly presented to you in an interview. /s
by throwaway9475 9y ago
Sure, because poor management, crippling technical debt, and a toxic work environment are totally plainly presented to you in an interview. /s
- inopinatus 9y agoNot plainly, no, but easily inferred.
- throwaway9475 9y agoYou should publish because I know I and a lot of other people would be incredibly interested in divining this information during a job interview.
- flukus 9y agoThe best I've come up with is a few proxies, like their deployment process. Someone doing continuous or frequent deployments probably have pretty decent code quality. A company that takes several weeks, several rounds of QA and a dozen release documents that need to be signed in triplicate, they have that process because they've been burned and need scapegoats when the inevitable happens. The best part is that most people at companies like this aren't aware that it's not normal, so they'll be open about it.
- inopinatus 9y agoYeah, that's basically all it takes. Talk to engineers about their everyday processes. (If the company doesn't let you talk to their engineers during the interview process, or if they're unwilling to discuss, consider that the huge red flag).
- tianlins 9y agoThis might not be true given just a couple of hours staying in the office and talking to people. Management issues / technical debt are not visible until you work for the company.