Learning Linux Basics Course & Labs
Working with Shell II
Behind Schedule
July 2nd, 10 a.m. — 12 Days Before the Demo
During their weekly conference call, team members Bob, Andrew, and Amira converge to discuss project updates. Early on, Andrew expresses his frustration regarding the persistent escalations in Project Sapphire:
Andrew:
"Three back-to-back escalations. There are too many issues with Project Sapphire. I'm tired of it. Luckily, Donald is managing the situation for me—he's doing a fantastic job."
After a brief pause, Andrew shifts focus to Project Mercury:
Andrew:
"Tell me some good news, Bob. How is the progress on Project Mercury? I hope you've been able to make headway on your laptop."
Bob responds, "I just started reviewing the design documents. I'm also working on deploying it locally and assisting with the issues related to Project Sapphire."
Andrew then directs his attention to Amira:
"That's not what I wanted to hear. Donald mentioned that he handed you the design documents last Wednesday and expected you to migrate the template code to your laptop this week."
Responding defensively, Bob states:
"Well, he did not tell me. In fact, he hasn’t mentioned anything at all regarding that."
Andrew follows up with:
"And what template code is he talking about?"
Keeping quiet, Bob listens as Andrew assigns a new task:
"Amira, please set up bi-weekly meetings to sort this out."
Amira then asks for clarification:
"Do you also want me to send a progress report daily?"
At this moment, an illustration appears to visually support the discussion:
Andrew confirms the new reporting requirement:
"Yes, please. And keep me updated on any showstoppers. We must have everything ready and functioning for Phase 1."
Turning back to Bob, Andrew emphasizes prioritization:
"Bob, it's great that you're addressing the escalations, but your primary focus must be on Project Mercury. Follow Mumshad Mannambeth's guidance and ensure the application is running on your laptop by Monday. This gives us one week to test it before pushing to the development servers."
Bob replies:
"Sure, Andrew. I'll make sure it's completed on time."
July 3rd, 11 a.m. — 11 Days Before the Demo
After reviewing numerous emails from Donald regarding Project Mercury, Bob discovers instructions for migrating template Python scripts from a Windows environment to Linux. One of the emails includes the following snippet:
KERNEL supported cpus:
Bob now faces the task of setting up a Django project on Linux. This involves remotely copying multiple files, extracting archives, making configuration adjustments, and updating specific sections of the code.
To support his efforts, Bob reviews key commands for archiving, data extraction, and efficient use of text editors.
Tip
For more information on setting up your Django project on Linux, refer to the official Django Documentation.
Watch Video
Watch video content