Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
BlueSky75152dAs a matter of fact in many companies delivering features are of more importance than writing clean code.
Lor-inc433852dJust be glad there wasn't any $$. I used to bump into it frequently. That shit exists exclusively to improve job security.
From what I've seen, developers of that kind roll in as a group, and therefore arrive with a form of herd immunity. If you have enough shitty developers, the business types assume that shitty code is actually good code.
1) Object chain transversal for data lookups, saved in configuration. e.g. dashboards, "trigger ___ when any of these change," etc.
2) In a risk engine: per-merchant rules to call
Both whitelisted, obv.
You could argue that the actual object path or asset names could/should be shielded, and you would be right for public / semi-public info, but for internal only it's actually better because it's less confusing and therefore easier to maintain.