Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "shitty translations"
-
WHY THE FUCK DO MY TEACHERS KEEP USING SHITTY TRANSLATIONS FOR PROGRAMMING CONCEPTS?! Like dude, everything related to programming is in english, just use the fucking terms in english for fucks sake. There are some words like "array" that fit into portuguese sentences without needing translation, so why translate it?
Why do you use acronyms in portuguese? People in the Database Systems class will later read a lot the acronym DBMS but won't know what the fuck that is because they teach the acronym SGBD, which is a translation.
It's so cringy and useless, so many terms the students will have to translate back to english when they get out to the real world because everything related to programming is in english.
"oh but what if the person doesn't know english" you don't even have to know english, just associate the concept (which will be explained to you in your language) with an english word. Also if you don't know english you'll have a very hard time, so I'd suggest taking english classes as your electives.
Ok I'm done, I got it out of my system.6 -
Another gem from my Database Fundamentals class, this time it's from the textbook:
So right now we're learning about data modeling with ERDs and the book is explaining a few things about attributes. I got to a part where the book was explaining when you should split an attribute into many (the book mixes up conceptual modelling and logical modelling). The first example the book gave was an address, splitting it up by street name, address number, city, postal code, etc. So far so good. Now we get to the second example: a phone number. The book split the the number 55 11 9784-8900 into four parts:
Country code: 55
Area code: 11
Number prefix: 9784
Number suffix: 8900
At this point I was like "WHAT?". Separating area and country codes from the rest of the number is ok, that's useful, but splitting the number itself in half? Why the fuck would you want to do that? Correct me if I'm wrong but the dash in the middle of the number is just used for "chunking", to make it easier for our brains to read the number. Why would you want to split the number in half? There's literally no reason to do it, at least not in the example the book was showing.
Every time I open this book I keep wondering why the hell my teacher chose it to be our textbook. He's a great teacher, his lectures are awesome, he explains stuff super well, but he chose this book. A book that's filled with shitty literal translations to domain-specific words and acronyms, shitty examples, and convoluted sentences.6