3 ms·
I'm not so sure I would be so negative on the code in isolation. Yes, I think I would personally like to get my code out there more with/for others. However,
by taeric 13y ago
I'm not so sure I would be so negative on the code in isolation. Yes, I think I would personally like to get my code out there more with/for others. However, I see no real reason to think this should be a moral imperative that is given to others. To the point that, while I would love for it to happen, I more want to make sure I just write more programs. Even if they are of the "I ran them exactly once just to see if it worked" variety.
- gedrap 13y agoI've had to maintain some codebases where the previous developer was working alone for 6-30 months. They often share the same issue that bad practices get repeated over and over and over again, not knowing something turning into a habit because no one pointed out. Also, knowing that someone will go through gives some extra motivation and makes you think twice before doing something lazy or stupid. Also, another person can recommend you a tool, library, etc which you wouldn't have thought of. For instance, at my early days as a developer I didn't know that things like SQL schema version control exists. I got introduced to liquibase which saved me from many many hours of work making sure all environments are using the same schema. It all depends on who sees your code and the way they approach with comments, and how do you deal with criticism.