TDD comes up with some really novel designs sometimes.
Like, I expect it should look one way but after I'm done with a few TDD cycles I'm at a state that's either hard to get there or unnecessary.
I think this is why some people don't like TDD much, sometimes you have to let go of your ideas, or if you're stuck to them, you need to go back much earlier and try again.
I kind of like this though, makes it kind of like you're following a choose your own adventure book.
Good design evolves from knowing the problem space.
Until you've explored it you don't know it.
I've seen some really good systems that have been built in one shot. They were all ground up rewrites of other very well known but fatally flawed systems.
And even then, within them, much of the architecture had to be reworked or also had some other trade off that had to be made.
Windows is a bit better these days, if you create an EFI partition it'll just use that even if you've made it much larger than it normally creates for itself.
This means you can just partition everything from Linux and then install windows safely into where you select.
The patent system is the problem. None of this should have been granted but when you really try to define what software patents are novel it becomes incredibly difficult.
Just because you think this is trivial does not mean a layperson does.
Is an encryption algo novel? What's novel about it, it's just a hashing function with some new parameters.
The reality is, software patents are a joke and should be dropped entirely. Copyright is enough protection for most use cases.
Aka, don't hate the player, hate the game. And ideally, do something to fix it instead of complaining about "trolls" as if that'll ever fix the issue.
The most hilarious outcome of this is the paper straws at places like Starbucks.
Feeding you coffee from a plastic cup through a cancer causing paper straw served to you wrapped in plastic.