Ambiguity in Technical Terms

It's been 3 years and 5 months since I started my professional journey. And I've noticed one thing from the very beginning. And that is the ambiguity surrounding the different terms in the industry. From the very basic terms to the more abstract. 

You will find people use Instantiation to mean Initialization and vice varca. Some will mean architechture diagram, but say data flow diagram. Some will confuse the external entity sign from data flow diagram to mean it somehow represents one to many or many to many relationship. 

I think in the abstract level, it means very little. Each team will have their own lingo and their own catchphrases but at the more root level it just gets confusing. Specially for someone who's just coming out of academia. 

One of the reason of these ambiguties I think is just our language. Bangla(or any other language other than English) is not really suitable to describe or explain programming or system design terminolgies. Because these terminologies have transcended any language and their native meaning. We all translate a term in bangla in our head to make the fog clear. But in the process of clearing up the concept, we confuse the terminologies. In the more abstract level however, I believe a lot of the companies or teams have their own systems which amalgated from different basic things and doesn't really matter on the long run(If you are involved enough in the initial SDLC phases).

Comments

Popular posts from this blog

Spring Data Jpa: What's underneath

Postgres 18 Upgrades

27th June , 2023