Developer Tea

• Dimensional Reframing - Think Along a New Axis

  This episode introduces the concept of dimensional reframing as a tool to gain new perspectives on problems and facilitate decision-making by considering a new dimension.• Learn how adding a new dimension to a problem can overcome limited perception and lead to new insights.• Discover how applying the dimension of time to bug management can help prioritise and address a manageable number of bugs within a specific period.• Explore how considering your energy levels can inform your approach to personal tasks, matching tasks to your available energy.• Understand how frameworks like Getting Things Done (GTD) use the dimension of context to make tasks more actionable.• Learn how the KonMari method employs the dimension of joy to fundamentally change how you decide what items to keep.• Understand that the key to effective dimensional reframing is choosing a dimension that you care about and that helps you make decisions.• Discover that dimensional reframing can be applied to both individual items and lists of items.📮 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.

  --------  

  12:57
• Chesterton's Fence - Why You Should Think Twice Before Rewriting That Project

  This episode explores the concept of Chesterton's fence, a principle that advises against removing or altering something without first understanding its original purpose.• Understand the core message of Chesterton's fence: before getting rid of an existing system, process, or code, take the time to understand why it was put there in the first place.• Learn about the common thought process that leads to wanting to remove things without understanding them ("Why on earth would anyone ever do it this way?").• Discover the parable of Chesterton's fence: the more intelligent reformer questions the removal of a fence until its use is understood.• See an analogy in code review where a senior engineer might question the removal of code or tests without understanding their purpose.• Understand the cognitive bias of illusory superiority and the Dunning-Kruger effect, which can lead to overestimating one's own abilities and underestimating the reasoning behind existing systems.• Recognise the mistake of assuming that predecessors were incompetent and that their work was done in error.• Appreciate the importance of adopting a curious mindset and trying to understand the original reasons behind existing practices.• Understand that Chesterton's fence is not a justification for never changing anything, but a caution against recklessness and the importance of being informed.• Learn that even when deciding to remove something, understanding its purpose can lead to better decisions and improvements in the future (e.g., replacing an old test with a better one).• Realise the value of learning from the experiences and reasoning of those who came before.📮 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.

  --------  

  8:50
• Reframing Areas of Growth to Your Manager

  This episode discusses how to reframe areas of growth identified in performance reviews with your manager, turning potential weaknesses into strategic strengths. It emphasizes focusing on excelling in your existing strengths rather than spreading efforts thinly across all areas of improvement. Understand why it's misguided to immediately convert a list of growth areas into a to-do list and the importance of collaborating with your manager on this. Learn to identify the growth areas you are interested in and determine what has kept you from excelling in them, such as time, opportunity, or self-confidence. Discover why focusing on becoming extraordinarily good in your already strong areas can lead to unique opportunities for you and your company. Explore how to strategically discuss your growth areas with your manager, focusing on a limited set of areas for improvement and suggesting compromises or delegation for others. Challenge the conventional wisdom of balancing skills and instead consider how to become a top performer (top 2%) in your areas of strength. Realise that a team composed of individuals excelling at different things, will probably be more effective than a team of well-rounded individuals.📮 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!

  --------  

  11:50
• Owning and Requesting Forward-Framed Feedback

  This episode provides a tactical question to elicit useful feedback by taking responsibility for seeking it out and framing the request in a way that encourages advice rather than judgment. Understand that your manager giving you feedback is your responsibility, which means you should actively seek it out rather than waiting. Discover how a simple question can shift the dynamic with your manager to get better feedback, focusing on advice for the future rather than dwelling on past behaviours. Learn the tactical question to ask your manager: "What do you think will hold me back from growing?" or a modified version like, "What do you think will hold me back from getting X promotion?". Explore why framing your feedback request as seeking advice is more effective because managers generally enjoy giving advice and it focuses on future improvement. Understand that the intent is not to analyze past behavior but to identify potential roadblocks to future success and growth.📮 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!.

  --------  

  9:12
• Work Modes Using Autonomy and Definition Clarity Quadrant - Manager Frameworks and Tools Series

  This episode introduces a simple quadrant tool to visualise different working modes that a team or individual task might be in, based on levels of autonomy and definition. Understand how the quadrant is built using the X-axis of dependency (high to low) and the Y-axis of definition (high to low) to visualise different work modes. Explore how the bottom left quadrant represents work that is highly exploratory and highly dependent, often requiring collaboration across multiple departments. Learn how a "spike" usually fits into the bottom right quadrant, signifying autonomous exploration. Discover how the top left quadrant is for work that is highly dependent but highly defined, such as a migration project or adopting a new tool. Understand how the top right quadrant represents work that is the most defined and the most autonomous, typically a singular task assigned to an individual. Recognise that many development frameworks focus on optimising work to fit in the top right quadrant to improve flow by reducing dependencies. Consider that the top left quadrant is often the lowest value production due to high dependencies without creative thinking. Realise that exploratory work, if unguided, can be a liability, and it may be useful to involve more people in the exploration or ensure the individual has significant experience. Be aware that processes are often optimised for tasks in the top right quadrant, potentially leading to the avoidance of work in other quadrants.📮 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.

  --------  

  16:06

Más podcasts de Tecnología

Podcasts a la moda de Tecnología

Acerca de Developer Tea