3 ms·
How much have those 'most complicated' options created the ability to build such a vast increase in expectations in relatively small amounts of work? Without a
by Groxx 15y ago
How much have those 'most complicated' options created the ability to build such a vast increase in expectations in relatively small amounts of work? Without a few several-thousand LOC gems, my Rails code would take longer and be more error-prone, and wouldn't play well with gems A through Z (excepting maybe Q). The fact that I can grab 5 random interesting gems, try them out, and then discard them with a very small amount of work on my part is phenomenally valuable, and wouldn't be possible if they weren't as well encapsulated as they often are.
- mistermann 15y agoThis would be an example of where putting significant thought into design and extensibility would be well worthwhile, because the target audience is so massive. The typical enterprise code will never be reused, it will never be "extended", but there's a decent chance it will have to undergo slight modifications. Most enterprise programmers, perhaps contrary to their image of themselves and their projects, are not working on the next ROR, are not sending a rocket to the moon, are not building an app that requires google-class scalability.
- Groxx 15y agoMany enterprise programmers have to deal with lots of other programmers, who they may not talk to, who are of vastly varying skills. They might literally need to protect their code from someone else's misuse, so it can be fixed later if needed without far-reaching complications. Which sounds a lot like an open source project, except that those involved may not be interested in what they're doing. I'd argue that makes them more dangerous, so a greater level of encapsulation may be warranted.