Aug 3, 2020 00:54
3 yrs ago
30 viewers *
English term
cardinal sin
GBK
English to French
Tech/Engineering
Games / Video Games / Gaming / Casino
Definition from
What Games Are:
A cardinal sin is a fuzzy term to describe a grievous mistake in game design which sinks a game completely.
Example sentences:
While we're sure many people will consider the game's shortness a cardinal sin, we'd still recommend you give it a try if you're a fan of '80s and '90s gaming, appreciate lush 2D artwork and desire an experience which firmly lodges itself in your consciousness – even if it doesn't last all that long. (NintendoLife)
And, while this is dangerously close to a gaming cardinal sin, it's also something that is understandable. When you can play through a beautiful experience, why would you slog through something that makes your eyes hurt after and hour and has bugs that could ruin your save? (WhatCulture)
Wasting space is not always a cardinal sin. It really depends on the menu being displayed. However, maps and quests, encyclopedias, books, statistics, and inventories generally need the full screen to be useful. (Sapphire Nation)
Proposed translations
(French)
| 4 +4 | péché capital |
Samuel Clarisse
|
Change log
Aug 1, 2020 00:20: changed "Kudoz queue" from "In queue" to "Public"
Aug 3, 2020 00:54: changed "Stage" from "Preparation" to "Submission"
Aug 6, 2020 01:58: changed "Stage" from "Submission" to "Selection"
Aug 6, 2020 05:54: changed "Stage" from "Selection" to "Completion"
Proposed translations
+4
6 hrs
Samuel Clarisse
France
France
France
Always keeping in mind the audience
Native in: French (Variants: Standard-France, Swiss, Canadian, Belgian, Luxembourgish) 
Works in: English to French, Spanish to French
Related KudoZ points
:
209
Selected
péché capital
Definition from
Quora:
Quels sont les 7 péchés capitaux de la programmation ?<br /><br />Mes changements sont minimes. Pas besoin de re-tester." Si vous avez ajouté, ôté ou modifié du code, rappelez-vous de TOUT re-tester en profondeur. Rappelez vous aussi que vos tests ne sont pas réussis tant que les personnes qui "héritent" de votre code (intégrateurs, testeurs, clients, ...) n'ont pas, eux aussi, complétés leurs tests avec succès.
Example sentences:
Les standards sont un moyen efficace pour permettre à plusieurs de travailler efficacement. Qu'il s'agisse de nommer vos composantes (variables, constantes, procédures, méthodes, fonctions, ...) ou d'utiliser certains outils (librairies, IDE, contrôles de versions,...) respectez ces normes. Je comprends que certaines fonctions portent en elles du code inutile que telle ou telle librairie (publique ou interne) peut avoir mais faites tout ce qui est raisonnable pour réutiliser ce code. Votre code que vous pourriez récrire prendrait plus de temps et serait probablement à déboguer contrairement à la librairie proposée (Quora)
4 KudoZ points awarded for this answer.
Something went wrong...