I think that's part of it. I'm the kind of person you'd find frustrating at first. I don't want to know all the internals of what I'm doing before I dive in. I

I think that's part of it. I'm the kind of person you'd find frustrating at first. I don't want to know all the internals of what I'm doing before I dive in. I want a nice API and good docs, and I want to build some stuff right away. And if I can't do that, I give up and move on to something else. If I like it, and it gives me quick wins, then I'll dive into the guts of how it works. Because I'm a responsible developer. But I have learned that with all the things out there to learn and absorb, I don't have time to deep-dive a framework before choosing to use it. There's something else coming that I have to do next week that uses something I don't know. So the more I build stuff, the faster I get at picking it up.