@tedu @lanodan @hj well, why I expected it to be sarcasm. Writing nice software is one of the most complex industry problem. It is one of the reason why there is a lot of tech universities, books etc, that's why people argue in stackoverflow comments etc and still there is no silver bullet. Maybe I was triggered by the word "guidance" which I interpreted as giving enough instructions (holy shit, corporate life kills my brains).
The word "nice" applied to software is subjective - nice to who? Author? Third party developers? Operating system(s)? PC's memory or cpu? End users? Novice or advanced? Every answer creates limitations which prevent software being nice for part of the users. Leaving the answers unanswered often prevents software from being nice for everyone.
Op's idea of "just writing nice software on his own" is one of the ways to give answer to the most of such questions - author is the only user so he know everything about users. And it is a good way. I love DIY-software, there's lot of fun, but I think of it as of ugly bullshit, but still love it :D
To make it NICE I need to invest about 200 hours into learning modern front-end (and even after learning it I will still think of it as of ugly bloated shit).