Skip to main content

12. Integration Exam 2.0 (The Macro-Logic Test)

Objective: A full system diagnostic. This exam tests the real-world integration of Information Framing (Passive Voice), Data Type Casting (Gerunds/Infinitives), Control Flow (Conditionals), and Exception Handling.

Instructions​

Refactor the corrupted sentences below. These are complex, multi-layered bugs. A single sentence might contain a Conditional crash, a Type Casting error, and a Passive Voice routing failure all at once. Write your clean, debugged code directly below each prompt.

1. (Corporate): "If the new wireframes will sign off on tomorrow, we start the React build immediately." (Hint: Fix the Level 1 Conditional crash, and ensure the wireframes receive the action passively)

2. (Casual): "Despite of I was tired, I whipped up a high-protein dinner after my workout." (Hint: Fix the Exception router and apply the correct Type Cast)

3. (Corporate): "If the server was backed up yesterday, we wouldn't lose the data." (Hint: This is a past event. Apply the Level 3 Post-Mortem logic with Passive Voice)

4. (Casual): "I remember to buy this MacBook Pro back in 2019 even though it was very expensive." (Hint: Fix the Memory Overload Type Cast for a past event)

5. (Corporate): "We need to push back on the timeline. In spite of, the client wants to launch tomorrow." (Hint: A new sentence requires a Hard Stop Exception Router)

6. (Corporate): "Although the Python script running perfectly, but the database rejected the payload." (Hint: Fix the Double Router Loop and the broken verb tense)

7. (Corporate): "If I was the IT director, the Lenovo ThinkStation will replace immediately." (Hint: Sandbox Override in the IF block, plus a Passive Level 2 RESULT block)

8. (Casual): "I went to the cafe in Brookefield for catching up with my university friends." (Hint: Apply the rule for explaining the Purpose/Why of an action)

9. (Corporate): "If the broken code didn't push to production, the app wouldn't crash." (Hint: Level 3 Post-Mortem + The code didn't push itself)

10. (Corporate): "I look forward to factor in your feedback, despite of the tight deadline." (Hint: Fix the Type Cast and the Exception router)

11. (Casual): "Although she avoids to cook on weekdays, the paneer turned out perfectly." (Hint: Fix the Type Cast for the verb "avoid")

12. (Corporate): "If the budget approves tomorrow, we buy the new software." (Hint: Level 1 Conditional + Passive Trigger)

13. (Corporate): "The meeting wrapped up early in spite of the CEO had a lot of questions." (Hint: Ensure the Data Payload matches the router type)

14. (Corporate): "I suggest to stick to the plan even though the client pushing back." (Hint: Fix the Type Cast for "suggest", and fix the broken continuous verb)

15. (Corporate): "If the issue escalated sooner, the lead developer would fix it." (Hint: Shift to a Level 3 Post-Mortem. The issue did not escalate itself, and the fixing is already in the past)

16. (Casual): "I use pink salt for making the food taste better despite it is expensive." (Hint: Fix the Purpose Type Cast and the Exception Router)

17. (Corporate): "If we have more time right now, the UI redesign would not hold off." (Hint: Level 2 Sandbox reality + Passive RESULT block)

18. (Corporate): "They decided rolling back the update although no data was lost." (Hint: Fix the Type Cast for the verb "decide")

19. (Corporate): "Before to deploy the code, we need the senior dev to weigh in on." (Hint: Apply the Preposition rule, and don't leave the API variable empty at the end)

20. (Casual - Full Refactor): "Despite of I am a freelancer, I enjoy to work with large teams. If I will be hired by Capgemini next month, I have to learn React quickly." (Hint: Fix the Exception Router, the Type Cast, and the Double Future Conditional)

Click here to view the System Output (Answer Key)

1.

  • The Bug: will sign off on, start
  • The Logic: Double Future Crash in the IF block. Because the wireframes receive the action, it must be cast as a Present Simple Passive. The RESULT block requires the future modal.
  • Clean Code: "If the new wireframes are signed off on tomorrow, we will start the React build immediately."

2.

  • The Bug: Despite of I was tired
  • The Logic: "Despite" cannot take "of" and it cannot route a full clause (Subject + Verb). You must either change the router to a Type 1 (Even though) or cast the clause into a Gerund (being).
  • Clean Code: "Even though I was tired, I whipped up a high-protein dinner after my workout." (Or: "Despite being tired, I whipped up...")

3.

  • The Bug: was backed up, wouldn't lose
  • The Logic: Level 3 Post-Mortem (Past reality). The IF block needs Past Perfect Passive (had been + V3). The RESULT block needs would have + V3.
  • Clean Code: "If the server had been backed up yesterday, we would not have lost the data."

4.

  • The Bug: to buy
  • The Logic: Memory Overload. Because buying the 2019 MacBook is a past, completed event, the memory function requires a Gerund.
  • Clean Code: "I remember buying this MacBook Pro back in 2019 even though it was very expensive."

5.

  • The Bug: In spite of,
  • The Logic: A brand new sentence requires a Type 3 Hard Stop router, not a Type 2 Data Object router.
  • Clean Code: "We need to push back on the timeline. However, the client wants to launch tomorrow."

6.

  • The Bug: running, Although... but
  • The Logic: Double Router loop (drop the "but"). The verb "running" is missing its BE gate to make it a valid past continuous action.
  • Clean Code: "Although the Python script was running perfectly, the database rejected the payload."

7.

  • The Bug: was, will replace
  • The Logic: Level 2 Sandbox reality. Apply the Sandbox Override (were) in the IF block. The RESULT block needs a Passive would be + V3 because the ThinkStation cannot replace itself.
  • Clean Code: "If I were the IT director, the Lenovo ThinkStation would be replaced immediately."

8.

  • The Bug: for catching up
  • The Logic: When explaining the Purpose/Why of an action, you must use the Infinitive pointer (to + V1).
  • Clean Code: "I went to the cafe in Brookefield to catch up with my university friends."

9.

  • The Bug: didn't push, wouldn't crash
  • The Logic: Level 3 Post-Mortem + Passive Voice. The code cannot push itself.
  • Clean Code: "If the broken code had not been pushed to production, the app would not have crashed."

10.

  • The Bug: to factor, despite of
  • The Logic: "Look forward to" always requires a Gerund because "to" acts as a Preposition. Drop the "of" after despite.
  • Clean Code: "I look forward to factoring in your feedback, despite the tight deadline."

11.

  • The Bug: to cook
  • The Logic: The verb "avoid" hardcodes a Gerund output.
  • Clean Code: "Although she avoids cooking on weekdays, the paneer turned out perfectly."

12.

  • The Bug: approves, buy
  • The Logic: Level 1 Conditional. The IF block needs Present Simple Passive (the budget doesn't approve itself). The RESULT block needs the future modal.
  • Clean Code: "If the budget is approved tomorrow, we will buy the new software."

13.

  • The Bug: in spite of the CEO had
  • The Logic: Type 2 routers cannot take a full clause. Shift to a Type 1 router (Even though).
  • Clean Code: "The meeting wrapped up early even though the CEO had a lot of questions."

14.

  • The Bug: to stick, client pushing
  • The Logic: "Suggest" hardcodes a Gerund. "Pushing" is missing its BE gate to make it a valid active verb.
  • Clean Code: "I suggest sticking to the plan even though the client is pushing back."

15.

  • The Bug: escalated, would fix
  • The Logic: Level 3 Post-Mortem. The issue did not escalate itself, so it needs Past Perfect Passive. The fix is also in the past.
  • Clean Code: "If the issue had been escalated sooner, the lead developer would have fixed it."

16.

  • The Bug: for making, despite it is
  • The Logic: Explaining purpose requires the Infinitive (to make). "Despite" cannot route a full clause (it is); shift to even though.
  • Clean Code: "I use pink salt to make the food taste better even though it is expensive."

17.

  • The Bug: have, would not hold off
  • The Logic: Level 2 Sandbox (fake reality). The IF block needs Past Simple (had). The RESULT block needs Passive Voice because a redesign cannot hold itself off.
  • Clean Code: "If we had more time right now, the UI redesign would not be held off."

18.

  • The Bug: rolling back
  • The Logic: The verb "decide" hardcodes an Infinitive output because it looks forward to a future task.
  • Clean Code: "They decided to roll back the update although no data was lost."

19.

  • The Bug: Before to deploy, weigh in on
  • The Logic: "Before" acts as a Preposition, requiring a Gerund. "Weigh in on" is a transitive block that cannot be left empty at the end of the sentence.
  • Clean Code: "Before deploying the code, we need the senior dev to weigh in on it."

20.

  • The Bug: Despite of I am, enjoy to work, will be hired, have to
  • The Logic: Full system crash! Fix the Type 2 router. Fix the Gerund output for "enjoy". Fix the Double Future crash in the Passive IF block. Add the future modal to the RESULT block.
  • Clean Code: "Even though I am a freelancer, I enjoy working with large teams. If I am hired by Capgemini next month, I will have to learn React quickly."