This is also one of the reasons I have really grown to dislike convention-over-configuration approaches.

Boilerplate code sucks, but there are ways to minimize it, and when something breaks you can follow the path through your code to see why.. you don't have to try to discern the interaction between the framework code, your code, defaults/convention and values you do have configured.

As a long-time ASP.NET developer, I definitely find the VSCode approach worthwhile. The new platform is definitely much more commandline oriented, but it's refreshing to be able to develop in such a lightweight text editor, compared the the usual Visual Studio experience.