good chemistry is complicated, and a little bit messy -LW |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
As I have been working on an ongoing project that was written primarily by a whole different group of people, I've realized that I've been what I call "Ninja coding" for quite some time now.
Define Ninja coding you say?
Ninja coding: So, I go in make my fix, and voila, everything looks smooth as if I weren't even there. All fine and good for the time being. What happens later after repetitive ninja attacks, I find that I'm becoming more and more assimilated by this code. This is all fine and good, that is, unless the code is BAD CODE!! Then I find myself coding like that coder does without even knowing. Ninja coding can be good in some cases. It doesn't upset the other authors, and keeps the style flowing throughout the page. You know exactly where things will be once "learning" the style well. Like for example if a programmer decides to always declare his sql outside of the sub routine. You know that the sql will be right above it. OR if a programmer never uses parentheses on his method called.. $self->execute vs. $self->execute(). I'm a ninja coder. I admit it. But in the process, I'm afraid that I've lost my true self. How do I really code? In reply to Ninja style coding... is it bad? by thaigrrl
|
|