I might be a bit contrarian here, but > In particular, add assist/code action/(bulb) as a first-class UX concept already. It’s the single most important UX inn

I might be a bit contrarian here, but > In particular, add assist/code action/(bulb) as a first-class UX concept already. It’s the single most important UX innovation of IDEs, which is very old at this point. Its outright ridiculous that this isn’t a standard interface across all editors. In the grand scheme of things, this particular super-local tactical optimisation seems like entirely the wrong problem to focus on with all the inefficiencies that come with badly designed software. Whether I write public double Hours { get { return _seconds / 3600; } } or public double Hours => _seconds / 3600; is really not going to make a big difference to the quality of my software. Is this where we want to focus our attention? The day I get a little pop-up that says - "are you sure you need to invent your own time abstraction here?", or - "this is a derived value that should only be used in presentation and not business logic or persistance", or - "the customer has not been using the feature that this code is relevant for in six months, are you sure you want to spend time on this?" then we can start to rave about the single most important UX innovations.