3 ms·
I've been in the same situation and here's what I learned: You will mostly never be able to revisit and refactor code 'once and for all' when it's deployed int
by kelvin0 8y ago
I've been in the same situation and here's what I learned: You will mostly never be able to revisit and refactor code 'once and for all' when it's deployed into production. The choices you make now will affect you in the future.
Instead your focus should be to take some time regularly and make some changes to keep your code from becoming a chaotic vengeful mess of a spaghetti bomb. The best analogy I have is something akin to gardening: it's through constant care and weeding out of bad vegetation that you have a great garden. You can't leave your code unattended and must always tend to it...
- megous 8y agoNot necesarrily true. I managed to do the most refactorings while under a non-technical leadership. You just take complete ownership for the code in that situation and do it along the way. You say no to features that would mess up the code or make the UI inconsistent, and you offer cleaner alternatives instead. As a single tech person you also have a lot of power.
- kelvin0 8y agoWe are saying the same thing. Take ownership, plan and grow your code base intelligently with refactor and tests included in every estimate.