While PDX-published games may suffer from the decouplement of features between DLCs, at the very least PDS-developed games have a built-up expertise when it comes to managing this.
As for MMO model, it’s a hard sell because purchased things get made “free” for new comers. It’s one of the crux that EU4 faced when they rolled many DLC features into the base game.
I first thought it was a paradise parasite of some kind, but I ended up understanding it’s a perfectible sensible conversation between a conscious pre-born and their mother, where the former jokes about using their mother as a suit that repurposes every drop of moisture into their body.
Not knowing much of Dune, this led to me reading quite a lot of resources online.
I was just scrolling in the World feed and thinking of how true this advice is, and that I should make more garlic bread. Then your comment hit with a different perspective that makes somewhat sense.
My company pays it for me. My use cases are split between new development, refactoring and debugging.
For new code, given that our code base is proprietary but very extensive, it provides nice code snippets that would be a pain to write by hand (it’s mostly C code) such as test code
I can focus on the concepts and have the autocomplete do the rest for me. I swap keypresses for reviewing code, which is not bad.
For refactoring, I seldom use it because I haven’t found an use case for it. Most of the changes involve moving code around, adding glue or deleting dead code.
For debugging, I sometimes use the chat to get documentation on public APIs from Microsoft or other places. I use this documentation to check for invariants and to reduce the scope of what I’m trying to find out.