1. Technical
1.1. Should I concentrate on fundamentals? (Data Structures & Algorithms)
1.1.1. Video
1.1.1.1. Youtube
1.1.1.1.1. https://youtube.com/shorts/h06p1sdgtfQ?feature=share
1.1.1.2. TikTok
1.1.1.2.1. https://www.tiktok.com/@glich.stream/video/7121346689872547078
1.1.2. Summary
1.1.2.1. As a junior, senior, or self-taught software engineer, should I focus on the fundamentals? By fundamentals, I mean data structures and algorithms. The short answer is yes.
1.1.2.2. Are you going to be using data structures and algorithms in your day-to-day job? Probably not, but studying data structures and algorithms gives you a new perspective on software development.
1.1.2.3. They give you new ideas, insights, tips, tricks, and techniques with which you can solve problems, or at the very least understand how problems are being solved in the libraries and tools you use every day.
1.1.2.4. So, beyond the technical interview (which, in my opinion, is broken), studying data structures and algorithms brings a ton of value to your career as a software engineer.
1.2. How to grow technically and evolve quickly as a Junior Software Engineer?
1.2.1. Video
1.2.1.1. Youtube
1.2.1.1.1. https://youtube.com/shorts/2G7Ku2xwJ6o?feature=share
1.2.1.2. TikTok
1.2.1.2.1. https://www.tiktok.com/@glich.stream/video/7127962929969777925
1.3. How to grow technically and evolve as a Senior Software Engineer?
1.3.1. Video
1.3.1.1. TikTok
1.3.1.1.1. https://www.tiktok.com/@glich.stream/video/7124675073788660998
1.4. How do you ramp up when there is no time dedicated for on boarding?
1.4.1. Video
1.4.1.1. TikTok
1.4.1.1.1. https://www.tiktok.com/@glich.stream/video/7128344471833513222
1.5. Better effort estimates
1.5.1. Video
1.5.1.1. Youtube
1.5.1.1.1. https://youtube.com/shorts/B3Sp4za7B6k?feature=share
1.5.1.2. TikTok
1.5.1.2.1. https://www.tiktok.com/@glich.stream/video/7147364635912490245
1.6. What every software architect must know
1.6.1. Video
1.6.1.1. Youtube
1.6.1.1.1. https://youtube.com/shorts/2xM3PjaOTNE?feature=share
1.6.1.2. TikTok
1.6.1.2.1. https://www.tiktok.com/@glich.stream/video/7148463174914821382
1.7. Technical scale is not a startups biggest concern!
1.7.1. Video
1.7.1.1. Youtube
1.7.1.1.1. https://youtube.com/shorts/MiLFKYO2Shc?feature=share
1.7.1.2. TikTok
1.7.1.2.1. https://www.tiktok.com/@glich.stream/video/7150579494405950726
1.8. Learning a new programming language
1.8.1. Video
1.8.1.1. TikTok
1.8.1.1.1. https://www.tiktok.com/@glich.stream/video/7168553775211351301
1.9. What is technical debt?
1.9.1. Video
1.9.1.1. Youtube
1.9.1.1.1. https://youtube.com/shorts/JHDXhnMSu84?feature=share
1.9.1.2. TikTok
1.9.1.2.1. https://www.tiktok.com/@glich.stream/video/7163346777230331142
1.10. How many tech stacks you should know?
1.10.1. Video
1.10.1.1. Youtube
1.10.1.1.1. https://youtube.com/shorts/KVeKYNW5xvU?feature=share
1.10.1.2. TikTok
1.10.1.2.1. https://www.tiktok.com/@glich.stream/video/7164085180464909573
1.11. Jack of all trades master of none
1.11.1. Video
1.11.1.1. TikTok
1.11.1.1.1. https://www.tiktok.com/@glich.stream/video/7170042851345190150
1.12. Less code == Less Maintenance
1.12.1. Video
1.12.1.1. Youtube
1.12.1.1.1. https://youtube.com/shorts/BP6enddv5FY?feature=share
1.12.1.2. TikTok
1.12.1.2.1. https://www.tiktok.com/@glich.stream/video/7188899208080985349
1.13. The PR review etiquette
1.13.1. Video
1.13.1.1. Youtube
1.13.1.1.1. https://youtube.com/shorts/uvEyRtZtl60?feature=share
1.13.1.2. TikTok
1.13.1.2.1. https://www.tiktok.com/@glich.stream/video/7188932322517994758
1.13.2. Summary
1.13.2.1. Code reviews don't have to be complicated or obscure. Here's what you should be looking for:
1.13.2.2. 1. The pull request description should adequately document the context of the change.
1.13.2.3. 2. The functionality should be beneficial for the code's users, both end-users (e.g. customers in a SaaS) and developers. Ask yourself: does the code do what the author claims it does, and have the edge cases been identified and addressed? Are there any security issues with the implementation?
1.13.2.4. 3. The code should be well-designed. Consider whether the changes introduced make sense, and whether they integrate well with the rest of the codebase. Are there any bad patterns?
1.13.2.5. 4. The code should not be more complex than necessary. Can you quickly understand the changes (assuming you are familiar with the codebase and have all the context), or do you need further explanation from the author?
1.13.2.6. 5. The change should not be overengineered. Is the author implementing things they might need in the future but don't know they need now?
1.13.2.7. 6. Appropriate unit tests should be included.
1.13.2.8. 7. Comments should be clear and useful. Good comments should mostly explain why, not what.
1.13.2.9. 8. The code should conform to your team's style guide. Anything else is a nitpick that should be optional to address.
1.14. E1 - The FUTURE of Software Engineering
1.14.1. Untitled
1.14.2. Video
1.14.2.1. https://youtu.be/axJ_rfzU_7I
1.14.3. Audio
1.14.3.1. https://anchor.fm/glich/episodes/E1---The-FUTURE-of-Software-Engineering-e1gu5q2/a-a7nmmqr
1.14.4. Summary
1.14.4.1. This is a conversation with Johannes Nicolai a former Principal Solutions Engineer at GitHub
1.14.4.2. Johannes Nicolai believes that in the next five years open source projects and enterprises will be able to build projects with just a click of a button. This will lead to an era of joyful experimentation and making software development easier.
1.14.4.3. Johannes explains that being a solution engineer at GitHub means every day is different and involves working closely with customers and the community. He decided to join GitHub after reading about their incredible concepts such as DevOps, ChatOps, and culture as code.
1.14.4.4. Bassem asks Johannes how he defines the threshold for overdoing it when it comes to using automation. Johannes responds that it's up to the individual to decide when it becomes too much. He also adds that it can be difficult to change the way a team works, as it requires courage and fighting against the IT department to get the tools of choice.
1.14.4.5. Bassem then moves the conversation onto the topic of the day, the future of software engineering. Johannes outlines his approach to the topic, involving acceptance, awareness, and narrowing the scope. He also explains that the best way to predict the future is to create it, and with GitHub and other open source communities, it's possible to have some influence in this direction.
1.14.4.6. In terms of predictions for the next five to ten years, Johannes believes that the technology already exists, but it is unevenly distributed. He mentions his favorite author William Gibson who said the future is already here, it's just unevenly distributed.
1.14.4.7. Johans believes that GitHub will be a key part of software engineering in the future. He explains that it will make it easier to find, fix and optimize code, as well as to provide insights into the code. It will also provide developers with the ability to easily share their work and collaborate with others.
1.14.4.8. At the same time, Johannes believes that developers will have to be more aware of security. He believes that security will become more important as the technology evolves, and that developers will need to be cognizant of the risks associated with the technology.
1.14.4.9. Finally, Johannes believes that the development process will become more automated. He believes that this will make the process more efficient and allow developers to focus on more creative aspects of the project. He also believes that this will lead to more diversity in the open source world.
1.14.4.10. In conclusion, Johannes believes that software engineering will look very different in the future. He believes that GitHub will be a key part of the process and that developers will need to be more aware of security. He also believes that the development process will become more automated, leading to a new era of joyful experimentation.
1.15. E5 - DevOps explained by CoP Director @ GitHub
1.15.1. Untitled
1.15.2. Video
1.15.2.1. https://youtu.be/a4G-Ff1Fp_4
1.15.3. Audio
1.15.3.1. https://anchor.fm/glich/episodes/E5---Demystifying-DevOps-e1hqc8m/a-a7r5ml1
1.16. E10 - Topics every software engineer MUST KNOW
1.16.1. Untitled
1.16.2. Video
1.16.2.1. https://youtube.com/live/gOkx1CyLFvY?feature=share
1.16.3. Audio
1.16.3.1. https://anchor.fm/glich/episodes/E10---What-technical-books-will-not-teach-you-live-streamed-e1jmgd5/a-a82v95l
1.17. E15 - Why is Engineering in Big Tech MUCH more effective?!
1.17.1. Untitled
1.17.2. Video
1.17.2.1. https://youtu.be/fpq-HBHHWd4
1.17.3. Audio
1.17.3.1. https://anchor.fm/glich/episodes/E15---What-does-Software-Engineering-in-Big-Tech-look-like-e1ljca0/a-a89qhjl
1.18. E16 - Why Is Everyone Talking About Data Engineering?
1.18.1. Untitled
1.18.2. Video
1.18.2.1. https://youtu.be/AkJp9xrbu4w
1.18.3. Audio
1.18.3.1. https://anchor.fm/glich/episodes/E16---Why-Is-Everyone-Talking-About-Data-Engineering-e1m73nu/a-a8bq0ni
1.19. E17 - Within The SPECIAL PROJECTS Team @ GitHub
1.19.1. Untitled
1.19.2. Video
1.19.2.1. https://youtu.be/jGbTLSwTBbQ
1.19.3. Audio
1.19.3.1. https://anchor.fm/glich/episodes/E17---Engineering-in-the-Special-Projects-team--GitHub-e1md5la/a-a8cdad4
1.20. E22 - What is Technical Debt & how can we deal with it?
1.20.1. Untitled
1.20.2. Video
1.20.2.1. https://youtu.be/ZOm_Saa_Uv8
1.20.3. Audio
1.20.3.1. https://anchor.fm/glich/episodes/E22---What-is-Technical-Debt--How-Can-We-Deal-With-It-e1r8v5e/a-a8u55lr
1.21. E23 - Software Testing is NOT what you’re familiar with!
1.21.1. Untitled
1.21.2. Video
1.21.2.1. https://youtu.be/HxQbu2ucgic
1.21.3. Audio
1.21.3.1. https://anchor.fm/glich/episodes/E23---Examining-the-nuances-of-Software-Testing-e1sfqf3/a-a92qskq
2. https://glich.stream
3. Soft Skills
3.1. Interviewing for the first time
3.1.1. Video
3.1.1.1. Youtube
3.1.1.1.1. https://youtube.com/shorts/u3vYcgIyvuU?feature=share
3.1.1.2. TikTok
3.1.1.2.1. https://www.tiktok.com/@glich.stream/video/7164324898054114566
3.2. Traits & Skills of the most valuable engineers I've worked with so far
3.2.1. Video
3.2.1.1. Youtube
3.2.1.1.1. https://youtube.com/shorts/kd7meCnZqqo?feature=share
3.2.1.2. TikTok
3.2.1.2.1. https://www.tiktok.com/@glich.stream/video/7135421190667111686
3.3. How much business domain knowledge should you have as a developer?
3.3.1. Video
3.3.1.1. Youtube
3.3.1.1.1. https://youtube.com/shorts/XRWy8LrWLGM?feature=share
3.3.1.2. TikTok
3.3.1.2.1. https://www.tiktok.com/@glich.stream/video/7158369693240200454
3.4. E13 - Imposter phenomenon: how I cope with it!
3.4.1. Untitled
3.4.2. Video
3.4.2.1. https://youtu.be/wUwUhydi808
3.4.3. Audio
3.4.3.1. https://anchor.fm/glich/episodes/E13---Imposter-phenomenon-how-I-cope-with-it--live-streamed-e1lecqd/a-a898076
3.5. Strategies for Working From Home as a Software Engineer!
3.5.1. Video
3.5.1.1. Youtube
3.5.1.1.1. https://youtu.be/SBCZbJRp7Pk
3.5.2. Summary
3.5.2.1. 1. Working remotely requires changes at both the individual and organizational level.
3.5.2.2. 2. Having a structured routine and fixed working hours is essential for increased productivity and avoiding burnout. This includes having a fixed sleeping schedule and working spot. This helps to create a ritual that signals the start and end of the working day, as well as helping to compartmentalize work and life. You should also match your cognitive load with your mental stamina, and incorporate physical activity into your day.
3.5.2.3. 3. To make the most of working remotely, it is important to understand your circle of influence and the power you have to introduce changes. Organizations and teams must also realize that remote working is a business decision and a fundamental cultural change. This means that everything should be done async by default and meetings should be booked in advance with an agenda and limited to 30 minutes.
3.5.2.4. 4. In a remote working environment, everything should be written down and documented, fostering a culture of note-taking and transparency. This allows everyone to have access to the work being done, even if they are not part of the direct team.
4. Engineering Management
4.1. Agile is the new waterfall
4.1.1. Video
4.1.1.1. Youtube
4.1.1.1.1. https://youtube.com/shorts/e6hVw2wAPFQ?feature=share
4.1.1.2. TikTok
4.1.1.2.1. https://www.tiktok.com/@glich.stream/video/7152465492807142661
4.1.2. Summary
4.1.2.1. Agile is the new Waterfall. There is a form of Agile that is practiced in many companies that is complete nonsense. Although some people may be offended, allow me to explain.
4.1.2.2. If you're doing 2-week sprints, spending 8+ hours per engineer on sprint planning, backlog grooming, retrospectives, and sprint demos, and you bring your entire organisation together for "Program Increment" planning, I'm sorry to tell you, you're practicing Waterfall, but have somehow convinced yourself it's Agile.
4.1.2.3. Agile is about allowing each feature team to come up with the best mechanism for them to work effectively. It's about putting trust in the talent you hired, believing they are "capable" of organizing themselves to help you achieve your targets. It's about being structured, but also flexible enough to pick up ad-hoc work of a high priority.
4.1.2.4. If you're thinking: "Oh, but my organisation will be in chaos if our people have this level of autonomy!" Are you sure you hired the right people? If you treat your people like children, they will behave as such. Let's not hide behind terms like "Scaled Agile" and "Modern Software Development" and call it what it is: "Contemporary Waterfall".
4.2. E2 - What skills does an engineering manager need?! Engineering Manager @ Red Hat shares his experience
4.2.1. Untitled
4.2.2. Video
4.2.2.1. https://youtu.be/ut1_QcXfRYA
4.2.3. Audio
4.2.3.1. https://anchor.fm/glich/episodes/E2---What-does-it-take-to-be-an-Engineering-Manager-e1gusct/a-a7npff0
5. Team Dynamics
5.1. Training new hires and junior software engineers
5.1.1. Video
5.1.1.1. Youtube
5.1.1.1.1. https://www.youtube.com/shorts/p_yEje2cJI8
5.1.1.2. TikTok
5.1.1.2.1. https://www.tiktok.com/@glich.stream/video/7133948318383639814
5.2. How can I deal with an engineer is too pedantic?
5.2.1. Video
5.2.1.1. Youtube
5.2.1.1.1. https://www.youtube.com/shorts/N-hZFUSlLeg
5.2.1.2. TikTok
5.2.1.2.1. https://www.tiktok.com/@glich.stream/video/7129813795911847174
5.3. Toxic work environments - Part 1
5.3.1. Video
5.3.1.1. TikTok
5.3.1.1.1. https://www.tiktok.com/@glich.stream/video/7164715338074983685
5.4. Toxic work environments - Part 2
5.4.1. Video
5.4.1.1. Youtube
5.4.1.1.1. https://youtube.com/shorts/sJ8k46oHX1Y?feature=share
5.4.1.2. TikTok
5.4.1.2.1. https://www.tiktok.com/@glich.stream/video/7172267135736089861
5.5. E8 - What it is like to work in a non toxic engineering culture?
5.5.1. Untitled
5.5.2. Video
5.5.2.1. https://youtube.com/live/emVSdWf_J-o?feature=share
5.5.3. Audio
5.5.3.1. https://anchor.fm/glich/episodes/E8---Working-in-a-toxic-engineering-culture--live-streamed-e1jhduq/a-a82atlh
5.6. E25 - Neurodivergence and the tech industry
5.6.1. Untitled
5.6.2. Video
5.6.2.1. https://youtu.be/Y5E-wg_QyoM
5.6.3. Audio
5.6.3.1. https://anchor.fm/glich/episodes/E25---Neurodivergence-and-the-tech-industry-e1tilou
6. Mobility & Opportunities
6.1. Moving to Europe or the USA as a software engineer
6.1.1. Video
6.1.1.1. TikTok
6.1.1.1.1. https://www.tiktok.com/@glich.stream/video/7151765686447017222
6.2. Being a highly skilled migrant is not a burden!
6.2.1. Video
6.2.1.1. TikTok
6.2.1.1.1. https://www.tiktok.com/@glich.stream/video/7152549929695661317
6.3. E9 - Which is better to work at? Startup, Scale-up, Big Tech?
6.3.1. Untitled
6.3.2. Video
6.3.2.1. https://youtube.com/live/15XsC9xVnaE?feature=share
6.3.3. Audio
6.3.3.1. https://anchor.fm/glich/episodes/E9---Make-better-career-choices--live-streamed-e1jmf67/a-a82v3pv
6.4. E12 - Generalist or a specialist software engineer? Which is better?
6.4.1. Untitled
6.4.2. Video
6.4.2.1. https://youtube.com/live/_WR7VqpgVp0?feature=share
6.4.3. Audio
6.4.3.1. https://anchor.fm/glich/episodes/E12---Generalist-or-a-specialist-software-engineer--live-streamed-e1lecjk/a-a897v77
6.5. E20 - Discover your options to get paid as a Software Engineer!
6.5.1. Untitled
6.5.2. Video
6.5.2.1. https://youtu.be/SmJBqjZtqHo
6.5.3. Audio
6.5.3.1. https://anchor.fm/glich/episodes/E20---Engineering-compensation-in-startups--scale-ups-and-publicly-traded-companies-e1ooc9l/a-a8kkcda
6.6. E21 - Engineering in the Arab World vs Europe & USA
6.6.1. Untitled
6.6.2. Video
6.6.2.1. https://youtu.be/b5dD8ADpLs4
6.6.3. Audio
6.6.3.1. https://anchor.fm/glich/episodes/E21---Engineering-in-the-Arab-World-vs-Europe--USA-e1pl21f/a-a8o16dp
6.7. E24 - Contracting as a Software Engineer
6.7.1. Untitled
6.7.2. Video
6.7.2.1. https://youtu.be/6Ml50Z9VtTg
6.7.3. Audio
6.7.3.1. https://anchor.fm/glich/episodes/E24---Contracting-as-a-software-engineer-e1tdg5k/a-a95u0jk
7. System Design & Architecture
7.1. Architecture Decision Record (ADR)
7.1.1. Video
7.1.1.1. Youtube
7.1.1.1.1. https://youtube.com/shorts/Vsar6-0kTO0?feature=share
7.1.1.2. TikTok
7.1.1.2.1. https://www.tiktok.com/@glich.stream/video/7157636413503065350
7.2. Engineering Design Reviews
7.2.1. Video
7.2.1.1. Youtube
7.2.1.1.1. https://youtube.com/shorts/Vtb4eT74rLo?feature=share
7.2.1.2. TikTok
7.2.1.2.1. https://www.tiktok.com/@glich.stream/video/7160407262522117382
7.3. The importance of spikes
7.3.1. Video
7.3.1.1. TikTok
7.3.1.1.1. https://www.tiktok.com/@glich.stream/video/7159212735421566214
7.4. The Art of System Design: Practical guide & Lessons from the field
7.4.1. Video
7.4.1.1. Youtube
7.4.1.1.1. https://youtu.be/3IWpU72eixw
7.5. E14 - What's the role of a Software Architect? Are they REALLY needed?!
7.5.1. Untitled
7.5.2. Video
7.5.2.1. https://youtu.be/-r_-rzlpcJI
7.5.3. Audio
7.5.3.1. https://anchor.fm/glich/episodes/E14---Whats-the-role-of-a-Software-Architect--Are-they-REALLY-needed-e1led8h/a-a8981m4
8. Career
8.1. Titles in tech are meaningless
8.1.1. Video
8.1.1.1. Youtube
8.1.1.1.1. https://youtube.com/shorts/0VZQM5idTBA?feature=share
8.1.1.2. TikTok
8.1.1.2.1. https://www.tiktok.com/@glich.stream/video/7165431746966621446
8.2. Promotions don't come as a result of hard work!
8.2.1. Video
8.2.1.1. Youtube
8.2.1.1.1. https://youtube.com/shorts/cgG1AozH3Kg?feature=share
8.2.1.2. TikTok
8.2.1.2.1. https://www.tiktok.com/@glich.stream/video/7165063862339783942
8.3. Moving into consultancy as an experienced developer
8.3.1. Video
8.3.1.1. Youtube
8.3.1.1.1. https://youtube.com/shorts/8gSliPqQjAc?feature=share
8.3.1.2. TikTok
8.3.1.2.1. https://www.tiktok.com/@glich.stream/video/7122821326431079686
8.4. Is it easier to be hired into a position or promoted into it?
8.4.1. Video
8.4.1.1. Youtube
8.4.1.1.1. Part 1
8.4.1.1.2. Part 2
8.4.1.2. TikTok
8.4.1.2.1. https://www.tiktok.com/@glich.stream/video/7126577886911319302
8.5. Are coding bootcamps a scam?
8.5.1. Video
8.5.1.1. TikTok
8.5.1.1.1. https://www.tiktok.com/@glich.stream/video/7156471923466177797
8.6. If you want to keep enjoying programming, don't make it your job
8.6.1. Video
8.6.1.1. Youtube
8.6.1.1.1. https://youtube.com/shorts/RMmDPuluIj0?feature=share
8.6.1.2. TikTok
8.6.1.2.1. https://www.tiktok.com/@glich.stream/video/7160772640523767045
8.7. Your tech stack IS NOT your identity!
8.7.1. Video
8.7.1.1. TikTok
8.7.1.1.1. https://www.tiktok.com/@glich.stream/video/7163902811619544326
8.8. E3 - Product management career path in enterprises and hypergrowth startups
8.8.1. Untitled
8.8.2. Video
8.8.2.1. https://youtu.be/HAHNECvkB5w
8.8.3. Audio
8.8.3.1. https://anchor.fm/glich/episodes/E3---Product-management-and-engineering-in-hyper-growth-startups-e1h8v2n/a-a7ounvc
8.9. E4 - On mental health and gender equality in tech
8.9.1. Untitled
8.9.2. Video
8.9.2.1. https://youtu.be/X70zoWutuQg
8.9.3. Audio
8.9.3.1. https://anchor.fm/glich/episodes/E4---On-mental-health-and-gender-equality-in-tech-e1h8rr9/a-a7oumd8
8.10. E6 - The Key is a Diverse, Equitable and Inclusive Engineering Culture!
8.10.1. Untitled
8.10.2. Video
8.10.2.1. https://youtu.be/9sQIjXILpNM
8.10.3. Audio
8.10.3.1. https://anchor.fm/glich/episodes/E6---Diverse--Equitable-and-Inclusive-Engineering-Cultures-e1ie95g/a-a7tol63
8.11. E7 - How far can you go as a self-taught software developer?
8.11.1. Untitled
8.11.2. Video
8.11.2.1. https://youtube.com/live/gRUgXJtXIL0?feature=share
8.11.3. Audio
8.11.3.1. https://anchor.fm/glich/episodes/E7---How-far-can-you-go-as-a-self-taught-software-developer--live-streamed-e1j5oqa/a-a80qpta
8.12. E11 - Preparing for tech interviews
8.12.1. Untitled
8.12.2. Video
8.12.2.1. https://youtube.com/live/IzldGQY4RQE?feature=share
8.12.3. Audio
8.12.3.1. https://anchor.fm/glich/episodes/E11---Preparing-for-tech-interviews-live-streamed-e1leam8/a-a897u10
8.13. E18 - The Skills Needed For A Successful Data Analytics Career
8.13.1. Untitled
8.13.2. Video
8.13.2.1. https://youtu.be/uk_1Go_kDvA
8.13.3. Audio
8.13.3.1. https://anchor.fm/glich/episodes/E18---The-Skills-Needed-For-A-Successful-Data-Analytics-Career-e1mfidf/a-a8cl8q7
8.14. E19 - From Software Engineer to CTO
8.14.1. Untitled
8.14.2. Video
8.14.2.1. https://youtu.be/YrhwN1uj6X0
8.14.3. Audio
8.14.3.1. https://anchor.fm/glich/episodes/E19---Software-Engineer-to-COO-e1o7aau/a-a8inplh
9. LEGEND
9.1. Untitled
9.1.1. Short
9.1.1.1. 1 - 3 minutes
9.2. Untitled
9.2.1. Deep dive
9.2.1.1. 18 - 50 minutes
9.3. Untitled
9.3.1. Podcast Episode
9.3.1.1. 30 - 60 minutes