3 ms·
I'd rather use the perl project of the guy who loves perl than the project of the guy who chose it "because he had to". Not sure if I'd want him as a coworker t
by noonespecial 13y ago
I'd rather use the perl project of the guy who loves perl than the project of the guy who chose it "because he had to". Not sure if I'd want him as a coworker though...
- StavrosK 13y agoI'm confused. Your original comment discusses a way to beat analysis paralysis, and now you're talking about someone who loves Perl. Is your original comment about a project that needs to get done, and about a way to get it done, or is it about a side-project that one starts just because they love writing it? It doesn't seem like these two are very similar.
- watwut 13y agoWhy? It is quite possible that "because he had to" guy will produce more readable code. There is no reason to care about developers personal relationship with whatever technology. Important question is whether he is able to produce functional, readable, well-designed code in acceptable speed. In case of projects under time pressure, the important question is whether the developer can do reasonable trade-offs between those expectations (eg. sacrifice the right one).
- lostcolony 13y agoAgreed. I want the person who hates the language; they're not going to write their code with all the 'neat' things Perl has, so it comes out looking like someone banged their head against the keyboard a few times, or as poetry (Black Perl). They may not write idiomatic Perl (if such a thing exists), but I bet I can follow it.