3 ms·
Asking someone with your amount of experience a coding exercise is silly. You wouldn't have lasted 15+ years if you didn't know how to code. Spend more time eva
by madrox 8y ago
Asking someone with your amount of experience a coding exercise is silly. You wouldn't have lasted 15+ years if you didn't know how to code. Spend more time evaluating the "softer skills," since more experienced engineers have a bigger impact on culture and process.
- ordinaryperson 8y agoRight? Ask me about past projects. Want GitHub examples? Fine. But whiteboard coding some non-real-world problem? I get that companies need some sort of filter, but whiteboard coding is not the answer, IMHO.
- bcassedy 8y agoLength of tenure is definitely not a good enough gauge. I've worked with folks with 15+ years that could technically code but they took eons to deliver and their solutions were unmaintainable. Some of them with advanced degrees too. Small sample size, but the few folks I'm thinking of were such bad hires that could have been avoided if we had them write some code or put the proper emphasis on the coding exercise we had them do.
- ordinaryperson 8y agoBut being a slow worker is going to be revealed during a whiteboard coding test? All small programs are maintainable, no interview process will tell you if a developer can deliver large, complex programs that are clean, modularized and easy to maintain because there's no time to do something of the requisite size. It's true there are experienced devs who suck, but that doesn't mean whiteboard coding is the process that filters them out.