39 ms·
As someone who likes to "get under the hood", I'm used to grumbling about developers these days who just glue together existing frameworks. But the real cause
by cannam 11y ago
As someone who likes to "get under the hood", I'm used to grumbling about developers these days who just glue together existing frameworks.
But the real cause of my dissatisfaction is that I find it harder to glue together existing frameworks -- I don't know where to begin, until I've dug in a bit to find out how something works underneath. Meanwhile other people whose approaches I think of as simplistic are able to leap in and get things done more quickly than I can.
(Similarly I find it almost impossible to learn much of a foreign language without studying the grammar, while some other people can immerse themselves and become quite conversant without ever thinking about grammar.)
Maybe the "non-engineer" developers are just working at a higher, and more immediately useful, level of interpretation.
- bphogan 11y agoI 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.