1) You ___ write clean code. a) mustn’t b) must 2) Developers ____ test their code before pushing it. a) must b) mustn’t 3) You ____ follow the team’s coding standards. a) mustn’t b) must 4) Every commit ___ have a clear message. a) must b) mustn’t 5) You ____ take responsibility for your tasks. a) mustn’t b) must 6) Juniors ____ ask for help if they are stuck. a) must b) mustn’t 7) You ___ review pull requests carefully. a) mustn’t b) must 8) You ___ keep your local repository up to date. a) must b) mustn’t 9) All errors ___ be logged properly. a) mustn’t b) must 10) You ___ push unfinished code to the main branch. a) mustn’t b) must 11) You ___ ignore code review comments. a) must b) mustn’t 12) Developers ___ skip writing tests. a) mustn’t b) must 13) You ___ commit sensitive information. a) must b) mustn’t 14) You ___ work on production directly without approval. a) mustn’t b) must 15) You ___ ignore security warnings. a) must b) mustn’t 16) You ____ deploy updates only after QA approval. a) have to b) don’t have to 17) Developers___ follow the sprint plan. a) don’t have to b) have to 18) You ___ track your tasks in Jira. a) have to b) don’t have to 19) You ____ take notes during meetings. a) don’t have to b) have to 20) Developers ___ communicate clearly with the team. a) have to b) don’t have to 21) You___ run all tests before merging a branch. a) don’t have to b) have to 22) You ___ keep your workstation organized. a) have to b) don’t have to 23) You ___ update documentation when adding features. a) don’t have to b) have to 24) You ____ attend daily stand-ups. a) have to b) don’t have to 25) You ___ fix critical bugs immediately. a) don’t have to b) have to 26) You ___ work overtime every day. a) have to b) don’t have to 27) You ___ handle every bug yourself. a) don’t have to b) have to 28) Juniors ___ know all the frameworks at once. a) have to b) don’t have to 29) You ___ write perfect code on your first attempt. a) don’t have to b) have to 30) You ___ memorize all commands — you can check docs. a) have to b) don’t have to 31) You ___ ask for feedback regularly. a) should b) shouldn’t 32) Developers ___ write comments in tricky parts of the code. a) shouldn’t b) should 33) You ___ pair-program with teammates when possible. a) should b) shouldn’t 34) You ____ check logs carefully when a bug occurs. a) should b) shouldn’t 35) You ____ test your code in different browsers. a) should b) shouldn’t 36) Juniors ___ learn Git commands every day. a) shouldn’t b) should 37) You ____ practice coding small tasks every week. a) should b) shouldn’t 38) Developers ___ ignore minor warnings. a) shouldn’t b) should 39) You ____ leave broken code in the repo. a) should b) shouldn’t 40) You ____ skip writing documentation. a) shouldn’t b) should 41) You ____ stay updated on new technologies. a) should b) shouldn’t 42) You ____ review your own code before submitting it. a) should b) shouldn't 43) You ___ communicate blockers early. a) shouldn't b) should 44) You ___ copy code without understanding it. a) shouldn't b) should 45) Developers ___ work in isolation all the time. a) shouldn't b) should 46) You ___ ask your mentor for guidance. a) can b) can't 47) Juniors ___ experiment with small features. a) can b) can't 48) Developers ___ suggest improvements to the workflow. a) can't b) can 49) You ___ push code to production without approval. a) can't b) can 50) You ____ ignore errors reported by QA. a) can’t b) can

Modals for a developer

per en/la
Imprimir
Incrustar

Tauler de classificació

Estil visual

Opcions

Canvia de fonament

Restaurar desada automàtica: ?