Powered by RND
PodcastsNegóciosDeveloper Tea

Developer Tea

Jonathan Cutrell
Developer Tea
Último episódio

Episódios Disponíveis

5 de 1267
  • Backup Plans and Risk Reward Curves
    This episode focuses on the critical importance of having a backup plan, not just for technical redundancies but especially for situations involving human error, which are highly prevalent in one's career. The core argument hinges on understanding risk and reward curves, highlighting the disproportionate impact of failures compared to incremental successes.Understanding Risk and Reward Curves:Successes are often incremental. Delivering a project on time typically leads to opportunities for more projects, good performance reviews, and modest pay increases (e.g., 5-7%). These are positive, but linear or slightly bumpy gains.Failures, especially uncaught ones, have a much longer negative tail. The potential for loss from a significant mistake or a disastrous project significantly outweighs the potential for gain from a success.A bad performance review, for example, can affect future reviews, decrease promotion likelihood, and follow you for a much longer period than a good one.Uncaught failures can place individuals in a pool for budget cuts or layoffs, leading to catastrophic curves where negative effects compound much faster, resembling a logarithmic function. One or two significant negative events could wipe out all accumulated incremental gains.The Criticality of Backup Plans:Backup plans are essential to avoid these catastrophic negative curves and major "wipeout scenarios".This preparedness applies to project failures, personal career contingencies (e.g., getting laid off), and even events beyond direct control.It's crucial to prepare for theoretically possible catastrophic events, not just those that have historically occurred. Even "Black Swan" events or things you're not prepared for can cause major issues.Thinking like this (e.g., similar to life insurance, which you only need once if at all) encourages hedging efforts with basic backup plans, such as redundancy.Benefits of Preparedness:The more you prepare for contingencies, the more likely you can deal with the majority of failures, preventing the catastrophic curve.Having backup plans can create a "flywheel effect", where your ability to respond to negative events actually increases the speed of stacking up further positive outcomes.Being proactive in your career (e.g., interviewing even when you're happy in your current role) builds resiliency.Actionable Advice:Focus on what could go wrong: Try to figure out how things could fail and what catastrophic events are possible, even if they haven't happened yet.Identify vulnerabilities: Locate areas where a catastrophe could lead to a steep drop-off in your career trajectory.Implement a basic backup plan: The recommendation is to put just one in place this week for something that could catastrophically impact your career. This provides a sense of relief and ensures readiness if needed. Taking this first step is likely to encourage creating more backup plans for professional situations.📮 Ask a QuestionIf you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.📮 Join the DiscordIf you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community by visiting https://developertea.com/discord today!🧡 Leave a ReviewIf you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you.
    --------  
    13:50
  • Second Order Consequences and Forcing Functions
    Todays episode delves into understanding and leveraging second and third-order consequences – the ripple effects that occur after an initial action – and introduces forcing functions, which are an inverted way of thinking about these consequences, designed to drive desired outcomes by first determining "what must be true" for them to occur. The episode also connects these concepts to the importance of effective goal setting, explaining how well-defined goals provide clarity, focus, and a strategic framework for decision-making and career advancement.Grasp Second and Third-Order Consequences: Learn to identify the downstream effects of initial actions. For instance, setting a target for test coverage (first action) might lead to people adding tests that don't genuinely test anything but merely inflate the metric (second-order consequence), potentially resulting in disillusionment with testing or continued incidents despite high coverage (third-order consequence). Conversely, giving someone ownership or autonomy (first action) can lead to them proactively filling out details and owning ambiguity (second-order consequence), which may result in higher quality work, freeing up managerial time, and setting the individual up for promotion (third-order consequence).Utilise Forcing Functions for Desired Outcomes: Understand forcing functions as an inverted approach to consequences, where you begin with a desired outcome and then identify the upstream requirements or desirable effects that must be true for that outcome to be achieved. This method helps to focus efforts on one to three key areas for improvement, rather than trying to enhance everything simultaneously.Implement Effective Forcing Functions: Discover how various elements can act as deliberate or accidental forcing functions:A prioritised backlog acts as a forcing function for essential discussions, decision-making, gathering sufficient information for prioritisation, and ensuring knowledgeable individuals are involved in the process.Presentations, demos, or all-hands meetings serve as powerful social forcing functions, as the desire to avoid the discomfort of not having progress to show incentivises action and preparation.Sprint planning is a forcing function that necessitates a clear understanding of priorities and team capacity for the upcoming sprint.Quality metrics or Service Level Agreements (SLAs), such as a P95 response time, act as forcing functions by requiring other system components to be correctly aligned to meet the target.The choice of technology or tech stack can be a significant forcing function for hiring, unintentionally selecting for specific types of engineers (e.g., Java for enterprise experience, TypeScript for full-stack, functional languages for functional programming experience).Workplace restrictions, like requiring night availability, can be accidental forcing functions, potentially selecting against individuals with community involvement, family commitments, or social lives.Successful hiring and recruiting is a strong forcing function for many positive aspects of a company, indicating technical success, high retention, competitive salaries, and a high standard for talent across the organisation.Harness Goals for Clarity and Focus: Recognise that a well-positioned goal is paramount for finding clarity, perspective, and purpose in your career. Goals provide a framework to make decisions about what to do, ensuring your time is spent on what matters to you rather than just on tasks handed to you, thereby enabling personal career growth.Set Relevant and Directionally Correct Goals: Emphasise the relevance of your goals; even if they are specific, measurable, actionable, and time-bound (SMART), they are ineffective if they are not relevant to your desired career path. Aim for goals that are directionally correct, moving you generally towards a long-term outcome (e.g., leading a project if your long-term aspiration is to lead teams), rather than being paralysed by the pursuit of a "perfect" goal.Leverage Manager Feedback for Goal Setting: If you are unsure how to set goals, consider what your boss would look for in your performance in six months. Proactively engage your manager by initiating conversations about career growth and goal setting, framing it as an opportunity for mutual success and seeking their input on what constitutes a "home run" for your role.Set Sustainable and Challenging Goals: Avoid goals that are too abstract (lacking clear actions) or that significantly over- or underestimate your capacity, as both can lead to disengagement. Instead, strive for challenging but sustainable goals that require focus and making difficult choices (e.g., saying "no" to other things) but do not lead to burnout.Be Mindful of Your Choices: Deliberately choose your forcing functions and become aware of those you are accidentally opting into. Consistently consider the downstream effects (second and third-order consequences) of your actions today, and set goals that imply a desired future state rather than dictating the exact methods. Consistency in this mindful approach to goal setting and understanding consequences is key to long-term career success.📮 Ask a QuestionIf you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.📮 Join the DiscordIf you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community by visiting https://developertea.com/discord today!🧡 Leave a ReviewIf you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you.
    --------  
    23:45
  • Don't Try to Solve Hyperobject Problems Once
    This episode delves into the philosophical concept of hyperobjects – problems so vast and complex they lack clear boundaries and cannot be "solved" once and for all. It explores why attempting to permanently fix issues like technical debt, user experience, or performance management is often ineffective. Instead, it offers a new perspective: how to interact with and manage these intractable problems by focusing on specific outcomes and accepting their ongoing nature.Understand hyperobjects as problems that extend beyond clear boundaries and time, such as technical debt or performance management, which cannot be truly "solved".Discover why a "one-time fix" approach is an anti-pattern for hyperobjects, as their dynamic nature means solutions must also be continuous.Learn to shift your mindset from "solving" to "interacting" with these large, persistent problems, focusing on managing their effects rather than trying to contain them.Explore the importance of focusing on specific, achievable outcomes and taking "snapshots" of the problem's current state, acknowledging that the hyperobject itself will continue to evolve.Recognise that language and conceptualisation play a crucial role in framing and addressing these intractable challenges within your work and organisation.📮 Ask a QuestionIf you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com..📮 Join the DiscordIf you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community by visiting https://developertea.com/discord today! It's totally free, and always will be, for people who listen to this show.🧡 Leave a ReviewIf you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you.
    --------  
    15:46
  • Behavior Change 101: Trigger, Incentive, and Ability
    This episode delves into a powerful model for encouraging behaviour change, applicable to both managing others and self-improvement, by focusing on three critical factors: Trigger, Incentive, and Ability. It challenges common, ineffective management approaches and provides insights into fostering new habits and desired actions by making the 'right' thing the 'easy' thing.Uncover why naive management approaches, such as mandating rules or blaming individuals, are ineffective at solving underlying behavioural problems or creating new, lasting habits.Learn about the Trigger, Incentive, and Ability model, a set of principles that can be applied to encourage specific actions in others or to facilitate self-betterment and incorporate new behaviours into your own life.Understand that Incentives are the critical factor in deciding what actions to pursue, driven by the question, "what's in it for me?". It's crucial for incentives to be clear and understood; an unclear incentive is effectively no incentive at all. Beneficial incentives tend to be more effective from a scientific standpoint.Discover the importance of a clear Trigger, which is the cross point or moment at which a decision to act is made. Assuming triggers will be self-generated is often a flawed management practice, especially when encouraging new behaviours.Explore how Ability goes beyond just skill, encompassing clarity on how to do something and the reduction of friction and variability in the desired behaviour. The goal is to reduce cognitive overload and make the desired action the easiest option, thereby facilitating habit formation.Realise the interconnection between Ability and Incentive, as a lack of clarity in how to perform a task (Ability) can make the incentive unclear because the reward for completion becomes uncertain.Learn that the investment in encouraging behaviour change should focus on creating a better trigger, a better (and clearer) incentive, and higher ability (lower friction, higher skill) to ensure people engage in the desired behaviour.📮 Ask a QuestionIf you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.📮 Join the DiscordIf you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community by visiting https://developertea.com/discord today!🧡 Leave a ReviewIf you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you.
    --------  
    20:16
  • Goal of the Goal - Using Goals As A Prioritization Clarifying Tool
    This episode delves into the crucial role of well-positioned goals in a developer's career. It asserts that goals provide clarity, perspective, and purpose, particularly focusing on clarity as a primary benefit. The discussion challenges common struggles with goal setting, including the often-overlooked importance of relevance (the 'R' in SMART goals), suggesting that an irrelevant goal, no matter how specific or measurable, is ultimately ineffective. The core message highlights that the purpose of a goal is to serve as a clarifying and prioritising tool, enabling you to make decisions about what to do and focus your efforts, rather than simply doing work that is handed to you. You will learn to start small and focus on desired outcomes or what you want to be true, accepting that a goal only needs to be "directionally correct" rather than perfect. The episode also provides a practical heuristic: to set goals by considering how your boss will evaluate your performance in the future. It emphasises the importance of setting goals that are challenging but sustainable, avoiding common pitfalls like overly abstract, too easy, or demoralisingly difficult goals, to prevent disengagement and burnout. Ultimately, consistent goal setting and reflection are presented as key drivers for long-term career success.Understand the fundamental importance of goals in providing clarity, perspective, and purpose in your career, especially for driven developers.Recognise that relevance is the most critical factor in goal setting; a goal's specificity or measurability is meaningless if it is not the right goal for you.Grasp that the primary function of a goal is to help you make decisions about what to do, acting as a clarifying, prioritising, and focusing tool for your efforts.Challenge the mindset that your goal as a software engineer is merely to complete assigned work; without personal goals, your career changes and skill development will be difficult.Learn to start small when setting goals and focus on desired outcomes or what you genuinely want to be true in your career.Embrace the concept of a "directionally correct" goal, understanding that a goal does not need to be perfect to guide you effectively towards a larger, long-term outcome.Utilise reflection after meeting a goal to assess whether it moved you closer to your long-term objectives, providing valuable steering for future goals.Employ a practical heuristic for goal setting: imagine how your boss would evaluate your performance in six months or a year, and set goals around those anticipated factors.Be proactive in discussing career growth and goal setting with your manager, framing it as an opportunity for them to direct your efforts towards organisational wins.Identify and avoid common pitfalls in goal setting, such as goals that are too abstract (not tractable), too easy (causing disengagement), or too difficult (leading to demoralisation).Strive for goals that offer a challenging but sustainable chance of success (e.g., around a 60% probability), requiring focus and the ability to say no, without leading to burnout.Understand that consistency in setting and pursuing goals is what ultimately defines long-term success, rather than the perfection of any single goal.📮 Ask a QuestionIf you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com.📮 Join the DiscordIf you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community by visiting https://developertea.com/discord today!🧡 Leave a ReviewIf you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you.For further reading (external sources):SMART Goals: The episode mentions the SMART framework (Specific, Measurable, Attainable, Relevant, Time-bound) as a good set of checks for goals. You can find more information about SMART goals on their Wikipedia page. (Please note: This link provides information from outside of the provided sources and you may want to independently verify that information.)The discussion on goal success probability (e.g., 60% chance of success) alludes to studies on optimal challenge levels for engagement and achievement. You may find further research on goal-setting theory and motivational psychology to explore these concepts in more detail. (Please note: This information is not explicitly from the provided sources and you may want to independently verify it.)
    --------  
    26:13

Mais podcasts de Negócios

Sobre Developer Tea

Developer Tea exists to help driven developers connect to their ultimate purpose and excel at their work so that they can positively impact the people they influence. With over 17 million downloads to date, Developer Tea is a short podcast hosted by Jonathan Cutrell, engineering leader with over 15 years of industry experience. We hope you'll take the topics from this podcast and continue the conversation, either online or in person with your peers. Email: [email protected]
Sítio Web de podcast

Ouve Developer Tea, MoneyFlix e muitos outros podcasts de todo o mundo com a aplicação radio.pt

Obtenha a aplicação gratuita radio.pt

  • Guardar rádios e podcasts favoritos
  • Transmissão via Wi-Fi ou Bluetooth
  • Carplay & Android Audo compatìvel
  • E ainda mais funções
Aplicações
Social
v7.23.3 | © 2007-2025 radio.de GmbH
Generated: 8/30/2025 - 5:47:12 PM