Where does maintaining a 25MB perl script fall into.

Documentation should be larger than code.

Tests as well.

Where does "Suddenly realizing why they call it DLL hell" fall on the scale?

the tests are now larger than the thing itself

The purpose of the code is to make the tests pass.

I miss why... he was what everyone really needed, and the industry destroyed him. I haven't seen anyone like him since.

50,000? thems rookie numbers.

the tests are now larger than the thing itself

Is such a weird complaint. You should aim for your codebase to be as small, simple and readable as possible, while your tests should be a specification that guarantees behavior is consistent between refactors. When you add behavior, you add tests, when you remove a behavior, you delete tests.

The size of either is independent of eachother. Small code bases that provide lots of features should be simple to read, but with a lot of tests.

I always tought that it's a norm to have more code in tests than in tested program

I was building up some packer stuff. Vsphere-iso plug-in. Tests were going fine and then for reasons I didn't understand it said it could no longer find the cd creation tool it has just been using.

So I try a few things, nothing works. So I figure I have nothing to lose, I make a new folder to house all the tools in one place. Update Windows system environment path. Restart everything. VScode didn't have my path statement, Google is of 0 fucking help, and now packer doesn't work. I least it's the weekend now.