Escuchar The Critical Channel

The Problem: A dropout, a CS graduate, and an MBA walk into a bar... While this sounds like a setup for a supremely cringe joke, it gives us three different perspectives on a big question: are Computer Science degrees important for success in the tech industry? What about degrees in general? Can not having one - or having the wrong flavour of degree - limit your opportunities?

The Problem: There are no silver bullets, but there is a cheat code. Today, let's talk about career progression, from the perspective of three engineering managers. What it means to advance when there are different tracks to explore, what it takes to get that next level, and what managers (i.e we) look for when recommending you for a promotion. Links: * On the Proper Care and Feeding of Monkeys [https://hbr.org/1999/11/management-time-whos-got-the-monkey] * Episode 16: It's a Spreadsheet, Bro [http://www.criticalchannel.io/16] — Our episode on authority * Episode 7: Nothing Engineer [http://www.criticalchannel.io/7] — Our episode on job titles. * Progression: Define and measure career growth for your team [https://progression.co/] * Urban Sports Club's public career ladder [https://urbansportsclub.progressionapp.com/teams/urban-sports-engineering/framework] * Julia Evans | Get your work recognized: write a brag document [https://jvns.ca/blog/brag-documents/] * A Work Log Template for Software Engineers [https://blog.pragmaticengineer.com/work-log-template-for-software-engineers/]

The Problem: The pain of receiving a letter (in German). We often feel stressed, or hear others saying they feel stressed. But what is stress, really? And how could it ever possibly be a good thing? This episode we give some tips on dealing with stress, look at what factors may cause it, and talk about how to recognise it in your direct reports and help them deal with it too. Links: * 43 Folders Series: Inbox Zero | 43 Folders [https://www.43folders.com/43-folders-series-inbox-zero] * Getting Things Done® - David Allen's GTD® Methodology [https://gettingthingsdone.com/] * Drive | Daniel H. Pink [https://www.danpink.com/books/drive/] * The Pomodoro Technique — Why It Works & How To Do It [https://todoist.com/productivity-methods/pomodoro-technique] * Frontiers | What is intrinsic motivation? A typology of computational approaches [https://www.frontiersin.org/articles/10.3389/neuro.12.006.2007/full] * Project management triangle - Wikipedia [https://en.wikipedia.org/wiki/Project_management_triangle]

The Problem: Forever wading through the thick, viscous soup of power differentials. Every company claims to want a strong feedback culture. But what does that even mean? What's so desirable about it, and what are you missing that's preventing you from getting there? Links: * Radical Candor [https://www.radicalcandor.com/] * The Culture Map [https://erinmeyer.com/books/the-culture-map/] * Difficult Conversations: How to Discuss What Matters Most [https://www.amazon.com/Difficult-Conversations-Discuss-What-Matters/dp/0670883395] * 97 Things Every Engineering Manager Should Know: Collective Wisdom from the Experts [https://www.amazon.de/-/en/Camille-Fournier/dp/1492050903]

The Problem: What is this product thing, anyway? Some battles are old as time itself. Godzilla vs. Kong. Man vs. Food. Tabs vs. Spaces. And Product vs. Tech, it seems as well. But why do we so often find a rift there? Surely we're working towards the same goals. Surely we must be able to collaborate and get along. This ep, we explore some of the reasons tension can occur between these two disciplines - and why, actually, that's okay! Links: * Inspired: How to create tech products customers love, by Marty Cagan [https://www.amazon.de/-/en/Marty-Cagan-ebook/dp/B077NRB36N] * Product shouldn't be left to product managers [https://candost.blog/mektup/mektup-32/] * Ubiquitous Language [https://martinfowler.com/bliki/UbiquitousLanguage.html#:~:text=Ubiquitous%20Language%20is%20the%20term,language%20between%20developers%20and%20users]