4 ms·
>One person at work put it best: "layers are only ever added, never removed." Find this in the software world as well. Something about the java culture seems
by tyingq 9y ago
>One person at work put it best: "layers are only ever added, never removed."
Find this in the software world as well. Something about the java culture seems especially fascinated with multiple layers of abstraction.
Edit: Ok, some factions of the culture. "Convenient proxy factory bean superclass for proxy factory beans that create only singletons"
- nebabyte 9y agoComputers don't understand concepts and people only do. Our gradual ascent from hardware to intuitively-usable mechanisms involves abstracting away the repeated "okay, given these primitives, here's how we'd use them" to go the next layer up.
- beagle3 9y agoBut that's non necessarily a good way. It's the easy way out of "I don't like these details, so I'll try to hide them under something". A good abstraction is worth its weight in gold. A bad abstraction (the vast majority) is worth its weight in dung.
- Terr_ 9y agoHopefully some of the static-strictness features in the language will offer people tools to remove layers of abstraction... if they can get permission from humans to do the refactoring :p
- aidenn0 9y agoSome infamous examples of such java classes (For some reason Spring always seemed to have more verbose names than other DI frameworks, which is saying something): SimpleBeanFactoryAwareAspectInstanceFactory SerializedEntityManagerFactoryBeanReference And this is totally not related to that sort of naming scheme, but in trying to remember those spring names, I stumbled upon this gem: http://git.eclipse.org/c/aspectj/org.aspectj.git/tree/org.aspectj.matcher/src/org/aspectj/weaver/patterns/HasThisTypePatternTriedToSneakInSomeGenericOrParameterizedTypePatternMatchingStuffAnywhereVisitor.java http://git.eclipse.org/c/aspectj/org.aspectj.git/tree/org.as...
- floatboth 9y agohttp://java.metagno.me/ http://java.metagno.me/
- moomin 9y agoSpeaking as a fan of C#, Clojure and Haskell, I'd say the problem is caused by having insufficiently powerful abstractions in the base platform. Phil Freeman has said that there are entire libraries on npm that just implement traverse.
- kqr 9y agoThat is funny. I am doing some temporary consulting work in a Java shop. I created a layered and complicated solution to a complicated problem. I spent a lot of time defending the complexity of the solution as the necessity it was. When the requirements appeared to change, I was all like, "Are you sure about that? That's great news because that means we can remove these layers from my solution and simplify the code a lot." Apparently they had never heard about someone wanting to get rid of their own layers, because they just sat there in silence trying to come up with reasons to keep the (now) unnecessary layers. In the end, I think they agreed that the new requirements must be incorrect, and the old ones still cover both cases. Imagine that! Throwing away new requirements solely to keep layers.