> There is value in providing good defaults, but users will and should be encouraged to go beyond them. That's what the documentation is for. >Being frustrated

> There is value in providing good defaults, but users will and should be encouraged to go beyond them. That's what the documentation is for. >Being frustrated is also normal. It's a natural part of the learning process. If everyone was always expecting everything to "just work" and gave up the moment they encountered the smallest bit of frustration, nothing would ever get done. Sorry but this is a backwards way of thinking about the usability of APIs and tools. User experience is critical, even if that user is a developer. The lower the friction the more adoption and productivity will exist with your project. User experience isn't only a "front end" thing and all developers really need to think about this when designing APIs and software in general. If you produce something that can't be reasonably executed with just a couple of steps you have failed. You should NOT feel frustrated just trying to start something. That is not part of the learning process.