Small chunks of code language. Don’t try to change multiple code language sections in one proposal. If you change 10 sections and there’s a single section that isn’t well received. You’ll likely lose all 10 proposed changes. Not worth it. Better to have many proposals.
Technical reasoning. Be concise. If you feel the need to write a dissertation or vent, step away from the computer. Less is more. More doesn’t help.
Technical testimony. Cover the technical points in support and negate the unintended consequences of your proposed code language. The opposition is going to argue about the unintended consequences, so you might as well do it first.
