System Changes and Gorillas

Here is how I feel my day goes on the system I'm trying to learn and fix at the same time:

Because I've dealt with scrum a lot, let's just say the person giving me the requirements is the Product Owner, or PO.

PO: Here is a new kind of animal we've found. If the naming department decides on a name, let's ask the review committee to check the name.
Me: Ok. *magic happens* System is now set up this way.
PO: Wait, there's a bug here. When the naming department decides on a name, we don't want the review committee to get it before the research department can decide what kind of animal it is.
Me: Hm. *Checks* Oh, well that's because when the naming department gives it a name, it automatically becomes a gorilla. Actually, when someone saves the animal, even if nothing is done on this animal, if the type of animal hasn't been decided on, it will always default to gorilla. ...Is that not supposed to happen?
PO: Oh yeah, I found out about that gorilla default last week. Does it have to have a default?
Me: *Checks* Well, teh system is all tangled together. If I change it to not have a default, chances are something else will break. And given that we're, oh, 2 days behind schedule, I vote for not changing this part.
PO: Agreed.

Success!

And this:

PO: Ok here's the update I need you to make. If the type of animal gets changed, the cage it gets assigned to needs to change as well.
Me: Ok. *Magic* Done!
PO: Well that's fine now. But now because the cage changes, the picture of the animal automatically got set to blank.
Me: ...I didn't even know there was a picture of the animal. Ok, so what do you want it to be?
PO: Let's ask the image department to confirm the picture of the animal is still right.
Me: *Magic* Ok! Check it out.
PO: Well yeah, that's fine. But since the image department needs to confirm it, we should also ask the writers to make sure the description still matches the image once they're done with it. You know, if it's an angry elephant vs a calm elephant, the writers may want to know that.
Me: ...There are writers?

And so on.

Don't get me wrong though - I love my job. But since I've only been here for about a month, there's a lot of the system for me to learn. That's not so fun. I wish I could just magically know everything about the system already so I could fix all the problems. Unfortunately, I just have to grit my teeth and learn it through.

When I do fix things though, those are the fun moments. And those are the moments when I love being a developer.