There's a balance though. In your free time, you should be the mad scientist, but on the job, correctness and maintainability is crucial in your final product. You can even play the mad scientist at work, but production-quality code has to be clean and professional, and that should be your code's final form.
Yes, this is so true. Too often someone wants to learn a new technique and throws it in production code without fully understanding it. Others get stuck maintaining it, also without fully understanding the technique, and because a full refactor is usually too expensive to justify.
It's great for learning on your own time, but hurts so many others when doing it professionally.
Comments
There's a balance though. In your free time, you should be the mad scientist, but on the job, correctness and maintainability is crucial in your final product. You can even play the mad scientist at work, but production-quality code has to be clean and professional, and that should be your code's final form.
Yes, this is so true. Too often someone wants to learn a new technique and throws it in production code without fully understanding it. Others get stuck maintaining it, also without fully understanding the technique, and because a full refactor is usually too expensive to justify.
It's great for learning on your own time, but hurts so many others when doing it professionally.