There is really no way around that.
As for "messing it up on developer machine" - that's not really possibly if the build is really reproducible. If the users get the same binary after building the source, they can be sure they have the source matching the binary.
If the binary they get is different from what the developer built on their machine, there is a good chance they don't have the source matching the binary, which is exactly what reproducible builds aims to protect them from.
That means that some commonly-used practices like embedding current timestamps into files become unacceptable.
It does tighten the development constraints -- although frankly, that's similar to many other secure coding practices. Better tooling, linting and frameworks will help to reduce the developer friction.
Indeed, a lot of the stuff you need to do to achieve reproducible builds can definitely make your build process more robust and secire.