It's not a case of "seeing the code isn't perfect" but rather, not understanding the myriad problems the code is solving or mitigating.

I'm reminded of this shitshow:

https://en.m.wikipedia.org/wiki/2010_Queensland_Health_payroll_system_implementation

Queensland is a state of about 3m people in Australia. Their health service employs about 100k people. They ended up spending about 900m USD to develop their payroll software and fix the fuck ups it caused.

I'm an accountant by trade, there's a classic "techbro does accounting" style of development we see a lot. Like if you hadn't spent a career learning how complex accounting can be, it would be easy to look at a payroll system and conclude "it's just a database with some rules".