Earlier quoted context omitted.
> "… do not put my name on it or associate it with me in any way." If you invented it, then they have to put your name on the application as the inventor. There’s also a declaration that the inventor is supposed to sign as part of the application. If the inventor is dead or otherwise unavailable (e.g., refuses to sign), there’s an alternative form that can be filed.
I'd be willing to bet lots of companies play fast and loose with the "inventor" names on patents anyway. I've looked up software patents issued to companies I've worked for, and sometimes the "inventors" listed were just eng managers and likely had nothing to do with the actual grunt work of writing the code.
The inventive step is the actual decision of 'we will do this thing in this way', or rather determining the 'method'. In fact, the guidelines we follow are that someone implementing the design based on some instructions, i.e, just working on a ticket, is explicitly not to be included as an inventor - unless they actually decided that's how it should be done.
Of course, it's nice to work in a place whereby you get to design and implement the system and become an inventor. In my opinion and experience at least. But I can see some organisations whereby developers are popping off tickets in sprints and implementing them - but that is by definition not an inventive step.