It can, but you have to have at first a clue of what you are doing. To know how to scale back a 100 MByte code base, you have to know the 100 MByte code base first, and you have to have lots of experience from coding within the 100 MByte code base, or from coding in a similar environment and with a similar goal.
To know how to scale back a large government, you have to know first what the government is doing, how it is doing what it does and why it does what it does, at best from your own experience in this government, or from working in another government.
Some outsider with big words but no experience is very likely screwing up big time, because he has no clue about most of the very important details. Yes, sometimes you find that wunderkind who is able to pull the stunt and get a new new code base working. But it surely has coded before, it has a general idea what's the point of the whole thing, and it is able to fastly get a strong team together pulling in the same direction. And sometimes you find that person who is able to redo a government as a relative outsider, but that person needs strong experience in how to govern something, and it has to be able to get a strong team together which pulls in the same direction.
And here the parallel between the government and maintaining a code base ends. Because you can create a new codebase while the old is still running. But you can't start a new government and get it up to speed while the old one is still running.