“No it’s better this way, it’s an enterprise grade architecture design” - someone who was no idea how to build an app

I imagine the meeting thusly:

*PM stands in front of dev team*
“In order to maximize our ROI and springboard from our current product into higher market awareness we need to optimize certain siloed workflows and synergies between departments.”

*@practiseSafeHex Raises hand*

“Does this mean I have to work with you?”

“Yes, we’ll all be working much closer together to facilitate -“

*@practiseSafeHex interrupts by standing up* I have to go now. Have fun filling your job vacancy.

@Diactoros more like:

Me: Hey could I get access to your repo? I'd love to see how the other mobile teams are building apps, what libraries, tools, process etc you use.

Other lead: Sure, here you go.

*Few days later*

Other lead: So what do you think?

Me: eh, i've never used this architecture before. Could you explain it? It looks like there is a lot of code, is that all necessary?

Other lead: Well we've done it this way because its more modular, flexible, segmented

*insert 3 other buzz words he lied about*

Me: ... right ... but like, there is A LOT of code. Like to add a button and link it to a new screen, I had to modify like 9 files. Is that really necessary?

Other lead: Ah see this is an enterprise grade architecture design. It's probably a bit more complex than what you are used to. But trust me it needs to be this way.

... the iOS project is 3gb, has 90 dependencies and takes 3 - 4 minutes to launch the app when you click run. Not one inch of that code makes any sense