Skip to main content

6. The Master Architecture (Tier 2 & Tier 3 Modules)

Objective: Master the "Storyteller" tenses (Tier 2) to provide context like background processes and uptime. Then, identify and refactor the "Legacy Bloatware" tenses (Tier 3) to keep your system running fast and native.

Part 1: Standard Library Upgrade (The Corporate & Casual API)​

The BlockThe LogicExecution
Figure outTo solve a problem or understand a complex issue."We finally figured out why the server crashed."
Hold upTo delay a process, event, or person."The supply chain issues held up the production."
Bring upTo mention a topic or introduce it into a conversation."Please don't bring up the budget during the meeting."
Burn outTo become completely exhausted from overwork."If we keep working 80-hour weeks, we will burn out."

Part 2: Tier 2 (The Context Modules)​

Do not use these as your default tenses. Only call these modules when you need to specify how an action relates to another action in time.

1. The Background Process (Past Continuous)​

  • Logic: Used to set the scene or describe a process that was running when an "Exception" (a sudden past event) interrupted it.
  • Formula: [Subject] + Was/Were + [V4 (-ing)]
  • Trigger: While, When.
  • Execution: "I was compiling (V4) the code when the power went out."

2. The Pre-History Log (Past Perfect)​

  • Logic: Used only to order two past events. It tells the listener which action happened first. Never use this for a single past event.
  • Formula: [Subject] + Had + [V3]
  • Trigger: Before, By the time, Because (in the past).
  • Execution: "The app crashed because I had deleted (V3) the wrong configuration file." (Event 1: Deleted file. Event 2: App crashed).

3. The Uptime Log (Present Perfect Continuous)​

  • Logic: Used to state how long an active thread has been running continuously up to the present moment.
  • Formula: [Subject] + Have/Has + been + [V4 (-ing)]
  • Trigger: For (duration), Since (starting point).
  • Execution: "The engineers have been trying (V4) to fix the pipeline for three hours."

Part 3: Tier 3 (The Legacy Code / Deprecated Tenses)​

These 4 tenses complete the 12-tense English motherboard, but they are computationally heavy and rarely used in fast, native conversation. You need to be able to read them, but you should actively avoid writing them.

1. Future Continuous​

  • The Bloatware: [Subject] + Will be + [V4] ("I will be flying to London tomorrow.")
  • The Native Override: Use Tier 1 Present Continuous or Future Simple. ("I am flying to London tomorrow.")

2. Future Perfect​

  • The Bloatware: [Subject] + Will have + [V3] ("I will have finished the report by 5 PM.")
  • The Native Override: Use Tier 1 Future Simple with a time limit. ("I will finish the report by 5 PM.")

3. Past Perfect Continuous​

  • The Bloatware: [Subject] + Had been + [V4] ("I had been trying to fix the bug when the system crashed.")
  • The Native Override: Use Tier 2 Past Continuous. ("I was trying to fix the bug when the system crashed.")

4. Future Perfect Continuous​

  • The Bloatware: [Subject] + Will have been + [V4] ("Next year, I will have been working here for a decade.")
  • The Native Override: State it as a simple future fact. ("Next year makes a decade for me here.")

Part 4: Debugging Gauntlet (25 Questions)​

Instructions: Identify the logic required (Background Process, Pre-History, or Uptime). Refactor the "corrupted" sentence into the correct Tier 2 Formula. Integrate the Standard Library API where requested.

1. (Interruption): "I figured out the database logic while I drank my coffee."

2. (Uptime): "The junior developer is trying to fix this bug for three days."

3. (Sequence): "By the time the ambulance arrived, the patient already recovered."

4. (Background): "The CEO brought up the merger while we ate lunch."

5. (Uptime): "I learn Python since January."

6. (Sequence): "The shipment held up because the workers went on strike the day before."

7. (Interruption): "The fire alarm rang while the team wrap up the presentation."

8. (Uptime): "The freelancer works on the front-end architecture for six hours."

9. (Sequence): "I couldn't enter the facility because I left my ID card at home."

10. (Background): "What do you do at 8 PM last night when I called?"

11. (Uptime): "She feels burned out lately because of the tight deadlines."

12. (Sequence): "The flight departed before I reach the boarding gate."

13. (Interruption): "While the mechanic figures out the engine issue, the customer waited in the lobby."

14. (Uptime): "It rains heavily for the last two hours."

15. (Sequence): "They didn't brought up the new policy because the manager didn't arrived yet."

16. (Background): "The stock market crashed while investors celebrate the quarterly earnings."

17. (Uptime): "We wait for the client to join the Zoom call for twenty minutes."

18. (Sequence): "The server went offline because someone unplugs the main power cable."

19. (Interruption): "She was dropping her phone while she ran for the bus." (Hint: Swap the background process and the sudden event)

20. (Uptime): "The logistics team holds up the delivery since Monday."

21. (Sequence): "I had passed the certification exam in 2024." (Warning: Single past event with a timestamp. Downgrade to Tier 1 History Log!)

22. (Background): "The software burned out my CPU while I render the 4K video."

23. (Uptime): "How long are you living in this city?"

24. (Sequence): "By the time we figure out the bug, the client canceled the contract."

25. (Integration): "Although I have studied for months, I blank out when the test was starting."

Part 5: Legacy Refactoring (10 Questions)​

Instructions: The following sentences are technically correct but use computationally heavy "Legacy Code" (Tier 3). Refactor them into faster, more natural native equivalents using Tier 1 or Tier 2 logic.

26. (Future Continuous): "The engineering team will be deploying the new update at midnight."

27. (Future Perfect): "By the end of the quarter, the sales department will have hit their targets."

28. (Past Perfect Continuous): "He had been trying to figure out the memory leak for hours when he finally collapsed."

29. (Future Perfect Continuous): "By December, we will have been living in this apartment for five years."

30. (Future Continuous): "Please don't call me at 2 PM, I will be having a meeting with the client."

31. (Future Perfect): "I will have resolved all the open tickets by tomorrow morning."

32. (Past Perfect Continuous): "The startup had been losing money for months before they finally burned out."

33. (Future Perfect Continuous): "By the time she graduates, she will have been studying software engineering for four years."

34. (Future Perfect): "The background script will have processed all the user data before the system wakes up." 35. (Past Perfect Continuous): "They had been holding up the production line for hours before the manager intervened."

Click here to view the System Output (Answer Key)

Part 4: Debugging Gauntlet (Tier 2 Context Modules)​

1.

  • Clean Code: "I figured out the database logic while I was drinking my coffee."
  • Logic: "While" triggers the Background Process (was drinking) for the sudden interruption (figured out).

2.

  • Clean Code: "The junior developer has been trying to fix this bug for three days."
  • Logic: "For three days" up to the present triggers the Uptime Log (has been trying).

3.

  • Clean Code: "By the time the ambulance arrived, the patient had already recovered."
  • Logic: Two past events. The patient recovering happened first, requiring the Pre-History Log (had recovered).

4.

  • Clean Code: "The CEO brought up the merger while we were eating lunch."
  • Logic: "Eating lunch" is the Background Process; "brought up" is the sudden event.

5.

  • Clean Code: "I have been learning Python since January."
  • Logic: "Since January" triggers the Uptime Log (have been learning).

6.

  • Clean Code: "The shipment was held up because the workers had gone on strike the day before."
  • Logic: The strike happened before the hold-up, requiring the Pre-History Log (had gone).

7.

  • Clean Code: "The fire alarm rang while the team was wrapping up the presentation."
  • Logic: "Wrapping up" is the Background Process interrupted by the alarm.

8.

  • Clean Code: "The freelancer has been working on the front-end architecture for six hours."
  • Logic: "For six hours" up to now triggers the Uptime Log.

9.

  • Clean Code: "I couldn't enter the facility because I had left my ID card at home."
  • Logic: Leaving the card happened before failing to enter. Pre-History Log (had left).

10.

  • Clean Code: "What were you doing at 8 PM last night when I called?"
  • Logic: Asking about a Background Process running at a specific past interruption.

11.

  • Clean Code: "She has been feeling burned out lately because of the tight deadlines."
  • Logic: "Lately" indicates an ongoing state up to now, triggering the Uptime Log.

12.

  • Clean Code: "The flight had departed before I reached the boarding gate."
  • Logic: The flight left first. Pre-History Log (had departed) comes before the History Log (reached).

13.

  • Clean Code: "While the mechanic was figuring out the engine issue, the customer waited in the lobby."
  • Logic: "Figuring out" is the Background Process.

14.

  • Clean Code: "It has been raining heavily for the last two hours."
  • Logic: "For the last two hours" up to now triggers the Uptime Log.

15.

  • Clean Code: "They didn't bring up the new policy because the manager hadn't arrived yet."
  • Logic: The DO gate (didn't) forces "bring" to V1. The manager failing to arrive happened first, triggering the Pre-History Log (hadn't arrived).

16.

  • Clean Code: "The stock market crashed while investors were celebrating the quarterly earnings."
  • Logic: "Celebrating" is the Background Process interrupted by the crash.

17.

  • Clean Code: "We have been waiting for the client to join the Zoom call for twenty minutes."
  • Logic: "For twenty minutes" up to now triggers the Uptime Log.

18.

  • Clean Code: "The server went offline because someone had unplugged the main power cable."
  • Logic: Unplugging happened first. Pre-History Log (had unplugged).

19.

  • Clean Code: "She dropped her phone while she was running for the bus."
  • Logic: "Running" is the continuous Background Process. "Dropped" is the sudden interruption.

20.

  • Clean Code: "The logistics team has been holding up the delivery since Monday."
  • Logic: "Since Monday" triggers the Uptime Log.

21.

  • Clean Code: "I passed the certification exam in 2024."
  • Logic: A single event with a timestamp (in 2024) must downgrade to the Tier 1 History Log (V2). No Pre-History needed.

22.

  • Clean Code: "The software burned out my CPU while I was rendering the 4K video."
  • Logic: "Rendering" is the Background Process; "burned out" is the sudden event.

23.

  • Clean Code: "How long have you been living in this city?"
  • Logic: Asking for duration up to the present triggers the Uptime Log.

24.

  • Clean Code: "By the time we figured out the bug, the client had canceled the contract."
  • Logic: The cancellation happened first. Pre-History Log (had canceled).

25.

  • Clean Code: "Although I had studied for months, I blanked out when the test started."
  • Logic: "Had studied" (Pre-History Log) happened before the test "started" (Sudden Past Event).

Part 5: Legacy Refactoring (Tier 3 to Native)​

26. (Future Continuous to Active Thread):

  • Legacy: "The engineering team will be deploying the new update at midnight."
  • Native: "The engineering team is deploying the new update at midnight." (Or: will deploy)

27. (Future Perfect to Future Projection):

  • Legacy: "By the end of the quarter, the sales department will have hit their targets."
  • Native: "The sales department will hit their targets by the end of the quarter."

28. (Past Perfect Continuous to Background Process):

  • Legacy: "He had been trying to figure out the memory leak for hours when he finally collapsed."
  • Native: "He was trying to figure out the memory leak for hours when he finally collapsed."

29. (Future Perfect Continuous to Future Projection):

  • Legacy: "By December, we will have been living in this apartment for five years."
  • Native: "By December, we will hit five years in this apartment." (Or: "December makes five years...")

30. (Future Continuous to Routine/Active Thread):

  • Legacy: "Please don't call me at 2 PM, I will be having a meeting with the client."
  • Native: "Please don't call me at 2 PM, I have a meeting with the client." (Or: am having)

31. (Future Perfect to Future Projection):

  • Legacy: "I will have resolved all the open tickets by tomorrow morning."
  • Native: "I will resolve all the open tickets by tomorrow morning."

32. (Past Perfect Continuous to Background Process):

  • Legacy: "The startup had been losing money for months before they finally burned out."
  • Native: "The startup was losing money for months before they finally burned out."

33. (Future Perfect Continuous to Future Projection):

  • Legacy: "By the time she graduates, she will have been studying software engineering for four years."
  • Native: "When she graduates, it will be four years of studying software engineering."

34. (Future Perfect to Future Projection):

  • Legacy: "The background script will have processed all the user data before the system wakes up."
  • Native: "The background script will process all the user data before the system wakes up."

35. (Past Perfect Continuous to Background Process):

  • Legacy: "They had been holding up the production line for hours before the manager intervened."
  • Native: "They were holding up the production line for hours before the manager intervened."