so that team knows all future hire? I work on code bases that were written 15 years ago by a plethora of people in different imperative styles. where business requirements changed a lot over that 15 year period.

There's a lot of spaghetti code.

we found There's a strong correlation between method/function size and bugs.

There's not a lot of confidence because there's implicit mutable state and side effects all over the place.