4 ms·
Some people are never happy and always judge others. How do I know if my coworker will ever be happy with my code? What if he just hates me? I can't tell the di
by sadjuniordev 10y ago
Some people are never happy and always judge others. How do I know if my coworker will ever be happy with my code? What if he just hates me? I can't tell the difference :(
- EnderMB 10y agoIt's a tricky one. I can tell a chef when their food tastes like shit, but I can't cook like a chef can, and I probably couldn't tell him/her what he needs to do to make their food taste better. It might not even be a bad meal! It might just be different to what I'm used to. It's entirely possible that your co-worker doesn't know what would improve your code, but simply knowing that it can be improved can be a useful thing, as it urges you to explore other options. Since your co-worker has said that your code is "WET" (I assume the opposite of DRY?) this should lead you to look into what makes code DRY in your language, and through this, learning if your code is repeated for a reason or not. As a personal anecdote, on a recent project a junior developer slated some of my Razor code because I wasn't using EditorTemplates for the forms on the site. After a month or two on the project, that developer quickly learned why I didn't bother with EditorTemplates. Fields that seemed similar weren't similar at all at times. The project requirements were changing weekly, and ultimately I was able to make changes quickly while he was fiddling with his DisplayTemplates/EditorTemplates, trying to make them work reliably across multiple different scenarios.