Yes you have point. Refactoring requires a lot of head scratch to implement the new standards without breaking the functionality and UX. Caniuse is my best friend :)
Besides - who has time to refactor old code? You should absolutely try to learn something new with each new project. But it's pretty rare to have to go back and rewrite working code.
Unless of course accessibility standards keep changing under your feet. But that's a rant for another post. ;^)
I agree you should try to learn something new as you progress from project to project, but there's absolutely a place for refactoring, unless everything you do is for throwaway short-term campaigns, but even then you should be looking into producing something that's a bit more flexible and reusable. I now work at a place where the code is long running, and constantly being refactored and added to over time, and building from scratch every time something new came out would be an impossible task. My last job was at a media agency, where most things existed for a few months at a time, but even there I could see the pattern of what was being produced and put together something that could be re-used for each new project. This itself was updated over time, and refactored to be better and offer more features as we needed them.
As for shifting accessibility standards, it doesn't happen ofter (we've had WCAG 2.1 for quite some time now) but WCAG 2.2 is round the corner (minor changes to what already existed, but 9 additional guidelines), and WCAG 3.0 is being worked on.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes you have point. Refactoring requires a lot of head scratch to implement the new standards without breaking the functionality and UX. Caniuse is my best friend :)
Besides - who has time to refactor old code? You should absolutely try to learn something new with each new project. But it's pretty rare to have to go back and rewrite working code.
Unless of course accessibility standards keep changing under your feet. But that's a rant for another post. ;^)
I agree you should try to learn something new as you progress from project to project, but there's absolutely a place for refactoring, unless everything you do is for throwaway short-term campaigns, but even then you should be looking into producing something that's a bit more flexible and reusable. I now work at a place where the code is long running, and constantly being refactored and added to over time, and building from scratch every time something new came out would be an impossible task. My last job was at a media agency, where most things existed for a few months at a time, but even there I could see the pattern of what was being produced and put together something that could be re-used for each new project. This itself was updated over time, and refactored to be better and offer more features as we needed them.
As for shifting accessibility standards, it doesn't happen ofter (we've had WCAG 2.1 for quite some time now) but WCAG 2.2 is round the corner (minor changes to what already existed, but 9 additional guidelines), and WCAG 3.0 is being worked on.