Legacy Code
What does “it works, don’t touch it” usually refer to?
A. Well-tested code by Henri
B. Well-tested code by Ivar-Endrik
C. Legacy code that no one understands
D. Production documentation
C. Legacy code that no one understands
Q: What tool produces impressive-looking roadmaps disconnected from reality?
A. Grooming
B. Bigbank all-hands
C. Daily stand-up
D. Tech-offsite
D. Tech-offsite
Q: The official fuel of software engineers is:
A. Target end
B. To see Marti happy
C. Salary
D. Cycle time
C. Salary
Q: What is the most reliable way to check if a bug is fixed?
A. Automated tests
B. Code review
C.UAT
D. Ask QA nicely
C.UAT
Q: What’s the safest reply in a 15-person meeting when you have no idea what’s going on?
A. “Good point.”
B. “Let me get back to you.”
C. “Can we take this offline?”
D. Nod and pretend you're on mute
D. Nod and pretend you're on mute
Q: What is typically considered too dangerous to refactor?
A.Promise to pay
B. Mainframe integration
C. SAR
D. Jenkinsfile
B. Mainframe integration
Q: When a Product Owner says “the MVP is ready,” what do they often mean?
A. The code is perfect
B. It barely works, but we can show it
C. Nobody wants to be gatekeeper/on call
D. QA approved it
B. It barely works, but we can show it
Q: Doing everything last-minute is known as:
A. Initiative
B. Procrastination-driven development
C. Busineks in Latvia
D. LEAN
B. Procrastination-driven development
Q: What does “100% test coverage” usually mean?
A. The code is perfect
B. There are lots of tests that test nothing
C. Lets fire QA-s
D. Every case is tested
B. There are lots of tests that test nothing
Q: What does “taking ownership” usually mean in corpo life?
A. Being responsible
B. Getting credit
C. Cleaning up someone else’s mess
D. Getting promoted
C. Cleaning up someone else’s mess
Q: What do we call code full of if-else statements with no structure?
A. Rigorous logic
B. Spaghetti code
C. Camunda flow
D. Targo
B. Spaghetti code
Q: Doing Waterfall while calling it Agile is also known as:
A. Lean
B. Scrum
C. Agilefall
D. Bigbank
C. Agilefall
Q: A “refactor” that ends up doubling the codebase is also known as:
A. Technical debt payment
B. Clean code
C. Overengineering
D. Being Scott
C. Overengineering
Q: What happens when the test environment is “almost like production”?
A. Accurate results
B. Smooth deployments
C. We have access to LHV somehow
D. It works until it doesn’t
D. It works until it doesn’t
Q: What’s a common side effect of back-to-back meetings all day?
A. Increased collaboration
B. Better decisions
C. No actual work gets done
D. Deep strategic alignment
C. No actual work gets done
Q: What’s the developer's reaction when asked to “just add a small feature” to a legacy COBOL system?
A. “Sure, no problem!”
B. “Is COBOL even Turing-complete?”
C. Nervous laughter followed by sick leave
D. “Let me rewrite it in Kotlin first”
C. Nervous laughter followed by sick leave
Q: When a developer says “this is simple,” what do they really mean?
A. They’ve done it before with Indian youtube tutorial
B. It’s 100% done
C. They have no clue how complex it is because they weren't paying attention during grooming and Marti is asking for a readback
D. It’s a 5-minute fix and 3 day revert
C. They have no clue how complex it is because they weren't paying attention during grooming and Marti is asking for a readback
Q: Approving an 800-line pull request with “LGTM” usually means:
A. “Looks Good To Me”
B. “Let’s Go To Mars”
C. “Didn’t read it, ship it”
D. “Leadership Got This Managed”
C. “Didn’t read it, ship it”
Q: When QA reports a bug with steps to reproduce, the developer says:
A. “Thanks!”
B. “Fixed already”
C. “Can’t reproduce on my machine”
D. “Not a bug, it’s a feature”
C. “Can’t reproduce on my machine”
Q: What does it mean when someone says “We value transparency”?
A. You’ll find out from a Slack leak anyway
B. Honest feedback flows freely
C. Everything’s documented
D. We forgot to CC you
A. You’ll find out from a Slack leak anyway
Q: What’s most likely to happen when you refactor legacy code with 0% test coverage?
A. Everything works as expected
B. QA-s losing hair
C. You break production and learn humility
D. You discover a microservice hidden inside
C. You break production and learn humility
Q: What does it usually mean when the project manager says, “we’re on track”?
A. The sprint is going well
B. QA is done
C. They haven’t checked with the dev team
D. A miracle occurred
C. They haven’t checked with the dev team
Q: “Paying down technical debt” usually means:
A. Refactoring
B. Paying engineers more
C. Deleting code
D. Cleaning up someone else’s mess
D. Cleaning up someone else’s mess
Q: Why do developers write unit tests?
A. To ensure quality
B. To sleep at night
C. Because their manager forces them
D. So they can say “I tested it” in code review
D. So they can say “I tested it” in code review
Q: How do you complete trainings?
A. Take notes
B. Ask questions
C. Watch all the videos and give feedback later
D. Mark it as done and yolo the test
D. Mark it as done and yolo the test