Ad

Why Is Convention And Consistency Important While Working With Data Fields/names?

The issue is about good practice with database, form fields, and coding in general.

We run a content providing platform, much like Buzzfeed and Wired. I am currently implementing the OpenGraph meta tags for each posts, so that the post links are nicely presented in external websites such as Facebook.

A co-worker from the marketing team insisted that we should put something else other than title in the 'title' field for marketing reasons.

I argued that the Open Graph meta tags should truthfully represent the content of the link, to conserve consistency and convention - that the meta tags should not be considered 'one-off's.

However I couldn't further explain as to why I should! I'm not really good with words myself.

Most of the quarrels involve other workers wanting to 'hack' with perfectly fine APIs or implementations and I have to convince them why it is important to at least stay in the safe zone while possible.

I know convention and consistency is one of the most important practice with technology but I think I just got used to the fact and forgot my university lectures on why it is so.

Could I get some thoughts on this issue?

Ad

Answer

A co-worker from the marketing team insisted that we should put something else other than title in the 'title' field for marketing reasons.

That's a valid decision. Your job is to help save costs or make money for the business. It is not your job to maintain the Facebook ecosystem as a whole. That's not what you are payed to do.

If you don't have any business reason why this should not be done you have no case. Such a reason could be that Facebook would penalize this or that this creates some development cost or risk.

If this is not a technical decision at all, and I see no reason it would be in the question, it's his decision anyway. In that case you need to inform him of the concerns that you see and let him decide.

Ad
source: stackoverflow.com
Ad