An author might write a story with lots of twists that are meant to be exciting, but this can actually end up confusing readers more than it entertains them.
"2. Try trimming the fat, can your work still stand strong without the extras?"
We usually need to wait a day or two to revisit the work to provide better criticism. However, in reality, when we complete the first pass of the work, the Jira task is marked as DONE (QCs might have even completed their tests), and we don't have time to return and refactor the code.
The solution, in my opinion, is to communicate with the team leader or PM, indicating that if they want the code to become more maintainable, they should allocate more time so that developers can revisit and refactor the code.
Both revisiting and refactoring code are not ideal.
Although they are indispensable, we can minimize the need for them through careful design, abstraction, and modularity. Project managers or team leaders are not concerned with the intricacies of your work, they primarily focus on results, functionality, performance, and bug-free output. Why don't we take these factors into account when estimating to allocate more time?
(Also, this post is not about refactoring or criticizing old code, it's about simple winning over clever)
"2. Try trimming the fat, can your work still stand strong without the extras?"
We usually need to wait a day or two to revisit the work to provide better criticism. However, in reality, when we complete the first pass of the work, the Jira task is marked as DONE (QCs might have even completed their tests), and we don't have time to return and refactor the code.
The solution, in my opinion, is to communicate with the team leader or PM, indicating that if they want the code to become more maintainable, they should allocate more time so that developers can revisit and refactor the code.
Great post, by the way!
Both revisiting and refactoring code are not ideal.
Although they are indispensable, we can minimize the need for them through careful design, abstraction, and modularity. Project managers or team leaders are not concerned with the intricacies of your work, they primarily focus on results, functionality, performance, and bug-free output. Why don't we take these factors into account when estimating to allocate more time?
(Also, this post is not about refactoring or criticizing old code, it's about simple winning over clever)