3 ms·
Tip #1 — don't try to write clean code. Try to solve the task with best quality possible. The quality of outcome (how reliable, performant and stable to edge
by aristofun 5y ago
Tip #1 — don't try to write clean code.
Try to solve the task with best quality possible.
The quality of outcome (how reliable, performant and stable to edge cases your feature is).
Clean code will eventually and naturally come.
Don't waste your energy starting from wrong side.
- thescribbblr 5y agoI try to achieve the same but my manager always forces me to write code cleaner so that it doesn't affect the other person who is reviewing it. I am kinda feel like hell when he say so.
- codingdave 5y ago> I am kinda feel like hell when he say so. That may be the bigger problem - listening to feedback is a great way to improve. If receiving that feedback makes you feel bad about your work, fix that response. Embrace the feedback as mentoring towards being a better developer, and be thankful for it. Easier said than done, but if you can adopt a positive attitude towards receiving feedback, odds are you'll be more comfortable taking the advice from your manager and get to a place where you both are happy with your work.
- aristofun 5y agoThen just take each his feedback as a lesson (as long as the feedback is specific) and grow from it. Nothing to feel bad about. It plays excellent together with my tip.