3 ms·
I write code on a whiteboard, when discussing how to solve a problem with colleagues. Almost exactly like in an interview. Do people really not do this?
by IshKebab 8y ago
I write code on a whiteboard, when discussing how to solve a problem with colleagues. Almost exactly like in an interview. Do people really not do this?
- overgard 8y agoI have literally never done this in a job outside of interviews, and I haven't had anyone else do it either. They might draw class diagrams or concepts, but writing code by hand is error prone and pretty pointless. Regardless, most modern offices have a projector or a TV in conference rooms. I just don't understand why you'd use a white board when you can easily project a text editor. The problem with writing code in handwriting is you can't move it, so you have to do it all linearly. If you need to introduce a variable or a new scope it gets messy incredibly quickly. When I code I almost am never thinking linearly, and I'm constantly adding things above and below, and doing that on a white board is a NIGHTMARE.
- ravenstine 8y agoI don't ever do this, and none of the teams I've worked on have ever used whiteboarding. Even pair programming is more common. Morevover, testing a candidate on whiteboard is like expecting all your candidates to be good with Emacs, even though that says zilch about their coding skills. Whiteboarding is just a tool like any other, and you(the interviewer) are limiting your talent pool by expecting everyone to not only be comfortable whiteboarding but to approach whiteboarding just like you do.
- samatman 8y agoI have frequently done whiteboarding, which is different from coding on a whiteboard. Working through approaches to solving a problem at a high level, or workshopping a schedule for a feature. That sort of thing. It’s also a decent skill to test someone on if your team uses it and the role requires it. But coding on a whiteboard is pointless, don’t do this to people please.
- itronitron 8y agoI've written code on whiteboards before, especially if I'm discussing an invasive code change with a coworker. It helps as a reminder of conclusions that were reached as the work progresses. One nice thing, maybe the killer feature, of whiteboarding for this use is that there are no distractions.