3 ms·
I sometimes describe it as “framework envy”. I've worked with a fair number of developers who learned library design by looking at the standard library or popul
by acdha 11y ago
I sometimes describe it as “framework envy”. I've worked with a fair number of developers who learned library design by looking at the standard library or popular frameworks and thought it was a model for everything, unaware that in many cases those were either poor examples (e.g. AWT / Swing) or complicated by offering a general solution usable for a wide range of projects and thus overkill for an internal app which would never be used elsewhere, especially when the core structure was still being determined.
- TeMPOraL 11y agoIt's something to grow out of. I had that "framework envy" towards game engines in my early years, and was designing overcomplicated architectures for a while.
- sbov 11y agoI think this hits the nail on the head. I would say that more generally, a not insignificant number of OO design concepts were developed in an environment of coding modules meant to be used by other people (either in the form of frameworks, or multi million line monoliths). For a large number of developers, neither of these environments apply, but they are still abiding by the same rules.
- acdha 11y agoYeah, it's like reading about some cool thing Google or Facebook is doing and then recognizing that your problem is much easier because the data fits in RAM