6 ms·
I thought it was just Martin but apparently my lack of being able to quickly grok these articles extend to the contributors on his site. There has got to be a
by Yhippa 14y ago
I thought it was just Martin but apparently my lack of being able to quickly grok these articles extend to the contributors on his site. There has got to be a way to communicate the kernel of what he's saying without pedantic language, lots of acronyms, and way too abstract language.
- jfb 14y agoUse of stupid jargon is strongly correlated with fuzzy thinking; sometimes, particularly where there's a dollar at stake, confusion is the intent.
- specialist 14y agoI've met Martin Fowler. Super nice guy. I don't question his intent. It just seems to me that "software architects" see the world in abstractions. Another friend calls this world view "enterprisey". Fowler and I would likely agree on the principles of reducing the cost of change, DRY, YAGNI, etc. But we wouldn't agree on the mechanics for achieving those goals.
- jfb 14y agoI don't have an opinion about Fowler, but whenever someone is pushing this sort of bafflegab, it can be a useful exercise to ask them: why can't you speak simply and directly? None of these concepts are difficult -- it's not a lecture on topology or Lie algebras or something. So why so much impenetrable jargon?
- specialist 14y agoTotally. My thesis is that some people truly think that way. What I find to be obtuse, obfuscated, tortured, overwrought is apparently pure poetry to others. On the flip side, I know that how I work drives many other people absolutely nuts.
- stonemetal 14y agoThe TL;DR is there are two levels of code high level domain relevant code, and low level implementation specific code. Your high level code should depend on interfaces not the low level implementation specific code. It is kind of no shit these days but it was the first cave man to add smart back when it was introduced.
- zaptheimpaler 14y agoMy summary: Your code should not deal with things at a lower level of abstraction than itself. External libraries tend to expose lower level interfaces than you need (because the API needs to be flexible enough to deal with a variety of use cases) , so build an abstraction in the middle between your code and the library that gives you exactly the functionality you need and nothing more.
- atc 14y agoThank God it wasn't just me! So many buzzwords, over-engineered paragraphs; obsessive abstractness. I wonder what his code's like!