Domain driven development. I will edit the question. :D

I found the use of the word "domain" confusing in it, but really the focus of it makes a HELL of a lot of sense. Generally when covering a topic, it helps to use the language associated with that topic. That's just the common sense of the matter -- and it 'needing' a term associated with it is more a declaration on how screwed up our industry is than it is anything new or innovative.

In some ways I think it 'needing a term' is just the backlash against SEO scam artists who have duped an entire generation into thinking their "keyword research" somehow made completely unrelated words "relevant" to the content generation process.

I remember about eight or nine years ago this one joker bragging about how his choice of terminology magically put him at the top of Google for results -- but the wording had dick-all to do with what the software the client was selling DID. It was a Photoshop plugin, so why were every other search result listed for his "magic search term" relating to powder-coating automotive engines? In marketing circles that's known as "non-competing competitors" -- a concept where you're wasting time and money targeting the wrong markets and companies who have nothing to do with your industry.

The "keywords research" SCAM being a perfect example where SEO "experts" would search for high volume search phrases they were sure they could rank #1 on, even if it had not the first blasted thing to do with the product or topic... then they could brag about that #1 ranking duping the client (who knows nothing about it) into thinking they did a good job.

Using the language of the product or industry just makes sense when you're making something FOR said topics! That shouldn't even be something that NEEDS explaining -- but here we are discussing exactly that.

... and that plays to something I'm always trying to drive home in web development: CONTENT FIRST Well written unique content of value relevant to the topic/product at hand -- or at LEAST a reasonable facsimile of future content... BEFORE you start dicking around with graphics, layout, goofy pointless animations, or any of the rest of the scam artist hoo-hah. Before anyone starts dicking around in Photoshop or even writes a single line of HTML, you should have that FIRST!

Otherwise what the blue blazes are you building?

Remember, on the web text is the first class citizen, everything else may as well have leprosy. Joe forbid you actually create text, or worse bother taking the time to have said text written in a manner that's actually relevant to the bloody topic in language those familiar with the subject matter might grasp.

Extending that into your codebase and construction plans should simply be a natural part of that process.

In that way, it's one of these things I read about, talk to people about, and think "well that's what I've been doing for 30 years... what the {expletive omitted} have you been doing?!?

Domain driven development. I will edit the question. :D