Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
p100sch15771yNever, as there is always something new and a different strategy to implement that system that works better without that balast.
Voxera97611yNot to often, but on the other hand I read a lot about new developments so if some old truth really needs changing, for example if an exploit has been found, I quite often find that out.
Reverifying everything you have learned over the years would take ages and even if there is a new better way, the extra time to research and learn might not be worth it? Especially if its a more complex thing as you are more likely to do something wrong ;)
I'll refactor bits to improve it.
But "recommend way"....hell if I know what that is...
I always check how I have done it first, directly copy if I can. If there is a chance to improve, i will take it. I won’t beat up myself over it to achieve perfect solution though.
One problem is shortage of time.
Second is dependency, when muliple people are working on a project refactoring becomes really a problem. Thats why we have code reviews and static analysers to check if we are following best practises in place as much as possible.
That being said, if the changes are relatively small or causing a vulnerability, I do refactor to make it sync with the current development processes.
Anything I did as a junior dev, I would check.
As a senior dev, generally have the belief in oneself that I did a good and full implementation as code reuse is one of the fundamental tenants of software development (not all would agree, but hey, some people have the time and inclination to re-invent the wheel. I'm not saying that's a bad thing. Some wheels are shitter than others!)
Only if my code involves anything regarding security or encryption.
Don't see why I would otherwise.