Critical Thinking Challenge

Froggy Jumps

Parties jouées 7 %Précision 80 Temps moyen 01:40

Créer une copie

À propos de cette activité

Sharpen reasoning skills

Créé par

Luisa Valderrama

Colombia

Téléchargez la version pour jouer sur papier

Top 10 résultats

#	Jeux	Précision	temps
1	Anonyme 31 Août 2026	% 100	00:31
2	Anonyme 31 Août 2026	% 100	00:39
3	Sahur 31 Août 2026	% 90	02:22
4	Anonyme 31 Août 2026	% 80	00:34
5	Anonyme 31 Août 2026	% 80	02:01
6	Anonyme 31 Août 2026	% 80	02:33
7	Carol Abril 31 Août 2026	% 70	00:57

Voulez-vous apparaître dans le Top 10 de ce jeu? Connectez-vous pour vous identifier.

Créez votre propre jeu gratuite à partir de notre créateur de jeu

Affrontez vos amis pour voir qui obtient le meilleur score dans ce jeu

Créer un défi

		%
	Anonyme	%
		%
		%

Imprimez votre jeu

Critical Thinking Challenge


Froggy Jumps Critical Thinking ChallengeVersion en ligne Sharpen reasoning skills par Luisa Valderrama 1 A classmate says: 'All software tests are useless.' What question should you ask first to analyze this claim? a Accept the claim as fact since it sounds strong. b Ask for evidence showing which tests are useless and in what context. c Suggest writing more tests without questioning the claim. 2 If two developers disagree on an algorithm, what is a constructive next step? a Compare performance, correctness, and edge cases with test cases. b Choose one opinion and stop the discussion. c Ignore the disagreement and proceed with one implementation. 3 Which habit best improves critical thinking in programming? a Relying on opinions of senior developers only b Regularly questioning assumptions and seeking evidence. c Avoiding new tools to stay with familiar methods 4 You read a bug report that says: 'Crashes only on Friday.' What should you do first? a Ask for reproducible steps and dates to reproduce. b Close the bug as non-reproducible c Blame the user for inconsistent testing 5 A feature request contradicts a current constraint. What is a good approach? a Implement the feature to please the requester b Dismiss the constraint as outdated c Clarify constraints and evaluate trade-offs before deciding. 6 Which action helps avoid cognitive biases in debugging? a Formulate hypotheses and test each one with evidence. b Rely only on past fixes without testing c Jump to conclusions based on initial impressions 7 You hear: 'We always do it this way.' What should you explore? a Assume the method is wrong without evidence b Ignore the statement and proceed c Understand why the method exists and if it still applies. 8 If a metric shows improvement but user satisfaction drops, what do you do? a Ignore the metric and ship anyway b Trust only the metric and stop gathering feedback c Investigate the discrepancy and gather qualitative feedback. 9 Which practice strengthens logical thinking in code reviews? a Make sweeping judgments on style b Ask clarifying questions and require concrete examples. c Accept all changes without review 10 When you cannot prove a bug, what is a wise step? a Wait indefinitely for perfect proof b State uncertainty, propose experiments, and iterate. c Claim certainty to move forward quickly

Vous pouvez intégrer le jeu dans un LMS compatible avec LTI 1.1 ou LTI 1.3 comme Canvas, Moodle ou Blackboard. Les scores seront ainsi automatiquement enregistrés dans le carnet de notes de la plateforme.

Critical Thinking Challenge

Froggy Jumps

À propos de cette activité

Créé par

Téléchargez la version pour jouer sur papier

Top Jeux

Froggy Jumps

The Integumentary System

Froggy Jumps

Phlebotomy Order of Draw Quiz

Froggy Jumps

pizza

Froggy Jumps

Bill of Rights Game - The Constitutionalist

Froggy Jumps

Ethos, Pathos, and Logos Quiz

Froggy Jumps

Critical Thinking ChallengeVersion en ligne

par Luisa Valderrama

A classmate says: 'All software tests are useless.' What question should you ask first to analyze this claim?

If two developers disagree on an algorithm, what is a constructive next step?

Which habit best improves critical thinking in programming?

You read a bug report that says: 'Crashes only on Friday.' What should you do first?

A feature request contradicts a current constraint. What is a good approach?

Which action helps avoid cognitive biases in debugging?

You hear: 'We always do it this way.' What should you explore?

If a metric shows improvement but user satisfaction drops, what do you do?

Which practice strengthens logical thinking in code reviews?

When you cannot prove a bug, what is a wise step?