FWIW, I think it is very useful for embedded/bare metal programmers to have an understanding of the machine architecture and it's assembly code. I have seen people get by with a C compiler and printf, but being able to look under the hood and understand what is going on helps a lot. For example, when you get a Data Abort, being able to look at the stack and see where it occurred, or if you have to work with startup code etc.
I just wouldn't write the whole application in assembly, even for small projects. By lines of code, the Linux kernel is about 3% assembly code. EETimes surveys puts the percentage of projects written "mostly in assembly" at about 5%, but 60% of programmers use assembly code as part of their project. Those figures include all those small 8/16 bit projects which are still done in assembly.
So there you go, your software should be 97% HLL, 3% assembly. Real Programmers of course, use FORTRAN. On punched cards