It's the difference between knowing you'll grow and graduate together with your classmates vs knowing you're only going to see them for that one month before you move away.

I don't understand, if you've got easy to delete copy-pasted code, then delete it. It'll be a nice and cathartic exercise.

But sounds like what you're really talking about is code that isn't easy to delete.

Distributing power across a group of communities over the same topic (e.g. like seats in a congress/parliament) is a nice thought.

However, my second thought was how vulnerable that is in a fediverse. To continue the analogy, an adversary could create new states (server/communities) of arbitrary population (accounts) at will.

Whiskey

IMO folding to hide is about equivalent to moving all contents to another file/private function:

def bad_function(args):
    return _hide_elsewhere(args)

i.e. does nothing. Real solution to pyramids of doom is to fix the code.

That's changing the goal posts to "not static"

Sounds easy to simplify:

Use one of: constructor A(d), function a(d), or method d.a() to construct A's.

B and C never change, so I invoke YAGNI and hardcode them in this one and only place, abstracting them away entirely.

No factories, no dependency injection frameworks.

IMO factory functions are totally fine -- I hesitate to even give them a special name b/c functions that can return an object are not special.

However I think good use cases for Factory classes (and long-lived stateful instances of) are scarce, often being better served using other constructs.

Dedicated incremental static type checkers for dynamic languages already exist. In particular, Pyright for Python is fantastic and in many ways surpasses the type systems of classic typed languages

But would you pay for it?

My employer's paying for my access, and I only find it a bit useful here and there

Maybe my company gets a great discount or something, but if they would pay me the subscription cost to give up Copilot, I wouldn't miss it

You can reference envs from the host in docker compose, so code it in instead of manually passing tribal knowledge in: https://stackoverflow.com/a/73826410

Simpler to keep everything in one compose file if you can, under a test service that doesn't build unless explicitly named

Un-weird that env var and use the normal, boring feature of defining environment under your test service