

No, it definitely does not cover almost all software. Most software does not aim to allow a random user to build something that usually requires a dev.
When you use an OS, you build nothing. When you use a browser, you build nothing. When you use a game, you build nothing. When you use a graphics editor, you build something, but it’s not something that a dev could do.
I could go on with a list of almost all software like this, but that’s not a good use of my time, and I hope it is not necessary.
I am a dev as well, and to build a website you traditionally need a dev. Well, nowadays, you can build a website with a “no code” website builder. That’s the most common “no-code” use.
Not that it’s relevant to this conversation, but that doesn’t stop people from hiring me to build their website, because “no code” also means “limited customization” and/or “low quality”.
“Building something” and “Building something that traditionally requires dev work” are not the same thing.
The software you use always needed code to make, but it doesn’t aim to skip the “hire a dev” phase of your project. If it does, it is “no code”.
And for the sake of argument, let’s say that Blender doesn’t exist and no other software fulfilling the same purpose exists. Then you’d have to commission a dev (team) to create that software so that you can train people to create 3D models. But the dev building your 3D modeling software doesn’t typically have the skills to use the software afterwards, so it does not fit the “no-code” definition.
TL;DR: It is a “no-code” software when you can skip the “hire a dev” phase of your project and use said software instead.