4 ms·
I see this attitude a lot that after 5-10 years devs think they no longer have to worry about writing maintainable code. I respect that once you reach a certai
by only_as_i_fall 5y ago
I see this attitude a lot that after 5-10 years devs think they no longer have to worry about writing maintainable code.
I respect that once you reach a certain level of competence you can probably coast by without thinking too much, but let's not pretend comfortable stagnation is the same thing as mastery.
- withinboredom 5y agoHeh. I feel that all that mumbo is interesting. But for the most part it’s just dogma. I got my own dogma, but I’m not selling books about it and I’m not interested in teaching anyone. I also don’t care about anyone else’s dogma, and pretty much dismiss it if you try to use it as an argument in a code review. I’m writing code to solve problems, I’m not here to discuss the abstract art of code patterns and structure.
- only_as_i_fall 5y agoThis isn't about "abstract art of code", the original comment was that the guy literally didn't care about best practices or code style. Like it or not part of the job is writing code that the rest of the team can read and understand. Ignoring these things is just showing a lack of respect for your co-workers
- mbrodersen 5y ago25+ years of experience here. I see this problem with inexperienced developers much more than experienced ones. Which makes sense. Experienced developers have more experience feeling the pain of having to deal with unmaintainable code. So they care more about it.