I think you are conflating simple and easy. They aren't the same. Simple suggests less code, fewer pieces, and a shorter path between code and solution. Easier suggests least effort and less to look at. Simple isn't easy.
The primary difference between simple and easy are decisions. A good senior will spend more energy on considerations for appropriate decisions than the actual work.
This is surprisingly often not understood, even by people I showed the video. And I am not sure why.
But I do think it's necessary in out field to start understanding this much more deeply, especially for senior engineers.
Good definition of 'Simple'. Simple and easy may not be the same but there are situations where they are similar.
For e.g. - for production deployment, I could either put the entire office upside down. Fires across the departments. Broken applications. Rollbacks. Or, I can automate all of our QA test cases and have a one-click deployment. No huss or fuss. I'm sure after having this experience, someone will definitely say - well, this was easy.
The primary difference between simple and easy are decisions. A good senior will spend more energy on considerations for appropriate decisions than the actual work.