@Brunno Santos I think calculated fields are still the devil encoded. If one of them only relies on other values in the same record, that should be even easier to maintain with a Business Rule instead.
Another recent example that cost a customer, Support and me too much time: a dotwalked calculated field in a list does not get its value calculated fresh on list render, so you can see a different value in the list vs. the form when you drill in. This is due to a rather important bit of performance optimization done for lists, turns out. Combined with an ill-advised i18n customization the admin had no way of knowing might be problematic, it was a bit of a mess to untangle if you didn't already know what was happening and why.
