Re:What are red flags that signal you should walk away from ...
by shoo on Saturday May 23, 2015 @08:34PM
(#9594929)
See Peter Naur's essay "programming as theory building".
link:http://www.dc.uba.ar/materias/plp/cursos/material/programmin...
Re:What are red flags that signal you should walk away from ...
by witten on Saturday May 23, 2015 @02:53PM
(#9593913)
So absolutely true. But I think the best programmers strive to minimize the portion of the program that resides in their heads, and maximize the ease with which it can be recreated in someone else's.
Re:What are red flags that signal you should walk away from ...
by bandushrew on Monday May 25, 2015 @12:08AM
(#9598608)
That is a really insightful comment, thanks.
When you've got both portions, everything is awesome. I'd worth with a guy for years, and never had a problem with them. If I was working with some code they wrote and didn't get what was going on, I'd ask them, they'd explain, it'd make sense, and everything would be fine.
Then they'd leave, and I'd no longer have access to the portion of the program in their head, and the code they'd left behind would become worthless crap. The structuring was all wrong, the choice of variable names idiotic, the corner cases they handled seemed trivial and the ones left unhandled, crucial.
Maybe there's something wrong with everyone I used to work with (as I tended to think the first time or two this happened), maybe if we were better and writing documentation this wouldn't happen. But it is very, very easy to be given a codebase from a former employee -- a perfectly fine codebase written by a perfectly competent employee -- and conclude they are an idiot, because you're missing the portion that's in their head.