There are many security and business risks in developing and releasing software (eg. supply chain attacks, misconfigurations & security-relevant bugs), and many ways to manage them. For companies, this is just another risk to be managed.

Indeed. This is very much the way I use it at work. Present an idea of a design, iterate on it, then make a task/todo list and work through the changes piecemeal, reviewing and committing as I go. I find pair design/discussion practical here too. I expect to see smaller teams working like this in the future.

For small personal projects, it's more vibey.. eg. Home automation native UIs & services for Mac & Windows, which I wouldn't otherwise start.. more itches that can be scratched in my limited time.

Why learn to play the drums, when there are drum machines? Or play any music, when there are MP3s? Or cook, when there's microwave dinners?

If you can't answer the above, you might want to have a chat with a psychologist. We can and do create meaning in our own lives.

Programming will change, but I won't miss creating the same boilerplate again and again. I expect to focus more on translating the business & technical requirements to decent quality results. I expect good interfaces and separation of concerns will be even more important, as whole modules might be rewritten from scratch rather than being modified, changing the way we think about maintainable code.