Merge pull request #375 from turingschool/tar_lesson3

Tar lesson3

module4/pd/lessons/operations_and_reliability.md

@@ -0,0 +1,131 @@
+---
+layout: page
+title: Operations and Reliability  
+module: 4
+---
+
+### Warm Up:
+
+In small groups, discuss the following:
+
+- Reflect on job titles you’ve had in the past. What does growth look like within those roles?
+- If the opportunity presented itself would you return to your previous place of work as a different title?
+- How do companies make sure new features don’t break their systems? Who they gonna call?  👻
+
+## IT Generalist to Manager of Technology
+
+IT Generalist couldn't be a more vague title. Information Technology General has more of a ring to it but if you break IT Generalist down it's actually pretty cool if you ask me (the universal _me_). It's a person who is competent in several different fields within tech, and suprise, suprise, that's you (the universal _you_)! After finding himself on the job market for 6 months, Turing Alum Joe Fogiato 2211 was reached out to by a previous employer. He found himself back at MANNA, the company he was at prior to Turing. However, this time as an IT Generalist, he was able to pave his his own path after asking himself: “What else can I do?”, “What does the organization need?”, “What are my career aspirations?”. He is now the Senior Manager of Technology and Continuous Improvement. 
+
+<section class="checks-for-understanding">
+### Note
+As small companies and non-profits begin to grow, or enter the modern era, it’s common for them to need a general “technology person” i.e. a IT Generalist.
+</section>
+
+Since starting at Turing, how many times have family members come to you with “computer questions,” as if you’ve suddenly become a wizard of technology? From “Can you fix the printer?” to “How do I copy and paste on my phone?”—I’ve heard it all. While Joe isn’t fixing printers at work, he is the go-to tech expert at his job, building accessible platforms for clients and writing automated scripts, just to name a couple of his contributions. As a jack of all trades, Joe is constantly learning new things and solving problems with technology every day.
+
+### Key Responsibilities:
+1. **Technology Management & Integration**
+
+    Oversee the cloud-based data warehouse, manage code changes, schema updates, integrations, and resolve technological pain points across departments. Administer day-to-day technology solutions to meet organizational needs.
+
+2. **Strategic Planning & Implementation**
+
+    Identify technology needs, strategize solutions, implement changes, and benchmark against organizational plans. Manage the IT budget and track savings through cost-reduction efforts.
+
+3. **Security & Compliance Oversight**
+
+    Serve as the internal Security Officer, ensuring data and technology security in collaboration with compliance officers and third-party providers. Monitor and mitigate risks, including cyber threats.
+
+4. **Training & Documentation**
+
+    Develop and lead staff training, workshops, and coaching. Create and maintain SOPs (standard operating procedures), training materials, and documentation to support processes, procedures, and security measures.
+
+5. **Hardware, Software & Telecommunications**
+
+    Manage the deployment, maintenance, and inventory of hardware and software. Ensure telecommunications infrastructure meets organizational requirements and aligns with emerging industry trends.
+
+We got a chance to sit down with Joe and speak on what it's like being the go-to technology problem solving person at a non-profit. Check out the full interview below. Please forgive my congestion - I had a cold 🤧
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/o8HGp95SMEI?si=6HsQ3bnqrMzCAW4p" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+
+Click to 20:36 to be all kinds of inspired, but when asked if he could give any piece of advice, or final thoughts, to future job seekers he had this to say:
+
+<section class="call-to-action">
+***“If you come to Turing with a mindset, I just wanna learn how to code because I want this thing and I want this very linear, this is the thing I want. I think that there is more risk to that than keeping it broader saying… I'll use myself as an example, I want a role where I use technology to solve problems for a mission that I care about. There are going to be way more roles and things you can do with that and you'll get to learn a lot more than if you're just like, no, I just want to be a software engineer. I don't want to do anything else. I think regardless of how the landscape shifts and jobs wise, that is always going to be something that exists and something that people want.”***
+</section>
+
+<section class="dropdown">
+### Let's Try it! 
+
+**Technology Problem-Solving**
+
+  **Scenario:**
+  The organization relies on a cloud-based data warehouse for storing and managing client data. Recently, users have reported difficulty accessing certain data fields after a schema update, impacting their ability to complete daily tasks.
+
+  1. What steps would you take to investigate and resolve this issue?
+  2. How would you ensure communication between the affected team and the technical team during this process?
+  3. What documentation or training would you create to prevent this issue from happening again?
+</section>
+
+<section class="call-to-action">
+Alternative job titles with similar responsibilities:
+- Technology and Operations Manager
+- IT Systems Administrator
+- Technology Solutions Specialist
+- Systems Integration Specialist
+</section>
+
+## Site Reliability Engineer (SRE)
+Similarly, Brennan Ayers 1903 found himself searching for a new job and was “willing to take anything." He came across a Site Reliability Engineering (SRE) Role and decided to pivot from development. A Site Reliability Engineer ensures that software systems are reliable, scalable, and efficient. They blend software engineering and operations to automate tasks like deployments, monitor system performance, and quickly resolve incidents. Their main goal is to maintain uptime while improving systems through automation and optimization.
+
+### Key Responsibilities:
+
+1. **System Reliability and Performance**
+    - Ensure systems are highly available and meet defined Service Level Objectives (SLOs).
+    - Monitor performance and troubleshoot outages to maintain uptime.
+2. **Automation and Process Improvement**
+    - Automate repetitive tasks like deployments, scaling, and incident recovery.
+    - Reduce manual work (toil) to improve efficiency and reliability.
+3. **Incident Response and Root Cause Analysis**
+    - Handle and resolve system incidents quickly.
+    - Conduct root cause analyses (RCAs) to prevent similar issues.
+4. **Infrastructure Optimization**
+    - Design and manage scalable, cost-efficient infrastructure.
+    - Optimize system performance and plan for future growth.
+5. **Monitoring, Observability, and Alerting**
+    - Implement tools to track system health and detect anomalies.
+    - Set up alerts and dashboards for better visibility into infrastructure.
+
+We had the chance to chat with Brennan, who transitioned from a traditional engineering role to Site Reliability Engineering (SRE). During our conversation, he shared insights into his journey into tech and his experiences as an SRE. Check out the full interview below!
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/9gh2dUtmSSs?si=Zqq78dZi9egcS10A" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+
+<section class="dropdown">
+### Let's Try it! 
+
+**🚨 Keep the System Running! 🚨**
+
+  **Scenario:**
+  Imagine you're a SRE at a super cool tech company who is responsible for maintaining the reliability of a web application. A critical service your team manages is experiencing slow performance during peak hours - losing money, ah! What steps would you take to identify and address the issue? Think about monitoring tools, automation, and collaboration with other teams.  
+</section>
+
+<section class="call-to-action">
+  Alternative job titles with similar responsibilities:
+  - DevOps Engineer
+  - Infrastructure Engineer
+  - Platform Engineer
+  - Production Engineer
+  - Incident Response Engineer
+  - Cloud Operations Engineer
+</section>
+
+## Wrap up
+
+<section class="checks-for-understanding">
+  In your notebook take some time to reflect on your experiences before Turing, the new skillset you’ve acquired, and how those can be applied to Tech Manager and a SRE.
+
+  - Describe some similarities and differences between a traditional Software Engineering role and someone who is a IT Generalist? SRE?
+  - What are examples in your previous work experience where you leveraged your education/skillset to grow within your role?
+  - Is there alignment between these roles and your previous experience / skillset? Begin to search job postings with these titles. Find 3 - 5 job postings that align with what you’re looking for.
+  - What are some further questions you’d ask Joe or Brennan?
+</section>

module4/pd/lessons/tech_adjacent_roles.md

@@ -34,6 +34,6 @@ Lesson 1: [Support Engineering](./support_engineering)
 
 Lesson 2: [Technical Writing and Quality Assurance](./technical_writing_and_QA)
 
-Lesson 3: Operations and Reliability
+Lesson 3: [Operations and Reliability](./operations_and_reliability)
 
 Lesson4: Education and Community Content