You should not do that. The right solution is to give the correct udev permissions to a specific group that you can add users to and those users would then have the correct access rights.
If you did it like described on that link and it did not work, it is most likely because your dev-kit for some reason has different vendor/device ids. Can you post the output of lsusb when the dev kit is connected?
Your method, unfortunately, is a security risk. Even without a malicious actor involved, it could result in bad things simply because Arduino is running as root (like you mistakenly overwriting the wrong file). It is great that it worked for you but, as I said, you should not do that. For your own sake.
Hmmm… It actually matches the ids from the link I posted. At the next opportunity I will see how the device is setup in my machine and you can compare to yours and check if anything is different.