Developing Up

By Mike Miles

About this podcast   English    United States

A podcast focused on the non-technical side of being a developer, because your career is about more than the code you write.
April 10, 2018
Technical leadership is not a specific role, it is a mindset. In this episode we talk with Adam Bergstein (@n3rdstein), V.P. of Engineering at Hook42 (@hook42inc) about what it takes to be a technical leader. In our discussion we tak about behaviours and traits that technical leaders embody and exhibit. Adam shares his personal journey of becoming a technical leader. Explaining how developers of any level, from junior to senior, can become leaders themselves. You have the opportunity to embody these traits to grow your development career. Key Takeaways Technical Leadership is a state of mind, not a specific role. Leadership is not about being the smartest person in the room. Lead by example and empower others. Three Leadership traits Focuses on quality of their work. Constantly learns about business needs and team needs. Not afraid to fail and helps others when they fail. Links from this Episode nerdstein.net Understanding Technical Leadership The Pragmatic Programmer* Previous Episodes Mentioned Leading By Example Dealing with Setbacks Continous Learning Have an idea for a future episode? Tweet Us: @devuppodcast Email Us: [email protected] *We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.
March 13, 2018
Development is full of complexities and challenges. Because of this, it can be difficult to maintain confidence in your development abilities. In this episode we talk with Aubrey Sambor (@starshaped), a front-end developer for chewy.com about Imposter Syndrome. Something that effects almost all developers at some point in their careers. Aubrey shares her personal experiences dealing with Imposter Syndrome and how she works through it. We discuss the five different types of Imposter Syndrome developers may experience. Fore each we outline their causes, effects and methods for overcoming. Key Takeaways Almost all developers experience Imposter Syndrome, you are not alone. You are not in your position due to luck, but because of your hard work. When you experience Imposter Syndrome dont go at it alone, turn to others for help. Five Types of Imposter Syndrome The perfectionist: Continuelly Setting and failing at over abmitious goals. The Super-person: Pushing to work harder and harder to the point overload. Natural Genuinus: If something is not hard, then it is not a sign of success. Rugged Individualist: Assuming that asking for help is a sign of weakness. The Expert: Success is gained through luck and not experience. Links from this Episode Aubrey on Twitter 5 Different Types of Imposter Syndrome The Secret Thoughts of Successful Women* by Valerie Young Mikes on the road "recording booth" Have an idea for a future episode? Tweet Us: @devuppodcast Email Us: [email protected] *We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.
Feb. 13, 2018
Many different types of people interact with the projects that we develop. To be successful then we need to be able to approach our work from their different perspectives. In todays episode we talk with Carie Fisher(@cariefisher) from Hook42 who is a front-end web developer and advocate for accessibility. We discuss why applying different perspectives make our development work and careers better. Carie shares her thoughts and experiences with accessibility, Inclusive Design and Development. We also discuss ways you can apply different perspectives to your development work. Key Takeaways Approach your work from the mind set of "Will it work for them", instead of "it works for me". Use personas to guide developing your work for other types of people. Open your code to reviews and input from other developers. Don't try to do everything at once, make one small improvement at a time. Keep trying. Links from this Episode Recording pillow fort Carie Fisher on Medium How to Boost Your Website’s Accessibility + SEO Previous Episodes Mentioned The Art of the Code Review Have an idea for a future episode? Tweet Us: @devuppodcast Email Us: [email protected]
Jan. 9, 2018
Development is about building solutions to solve problems. But when developing solutions, do you need to build everything yourself? In this episode we talk with Jonathan Solórzano-Hamilton (@jhsolor, @peachpie), Assistant Director of IT Operations and Architecture for ORIS at UCLA. We discuss why as a developer it is part of your job to know when not to build something yourself. During our conversation we outline when to use existing software and the benefits of doing so. We also outline guidelines to follow when looking for pre-existing solutions. Jonathan also provides a recap of his personal experience of what can happen when a development team tries to build everything in house. Key Takeaways Building everything yourself comes with risks and technical debt for you and your team. Focus your efforts on building whats important for your project, for everything else try and use expsing packages. It's part of your job to inform/sell your clients/company how to best build solutions. When looking for existing software Search for packages on reputable sources Look at community usage, is the package being used? check package activity, is it still supported? Review the license is it compatible with your project? Links from this Episode We fired our top talent. Best decision we ever made The Making of Tesla Completing the Netflix Cloud Migration Pervious Episodes Mentioned Using D.U.M.B goals and S.M.A.R.T goals to grow your development career. Taking Risks Have an idea for a future episode? Tweet Us: @devuppodcast Email Us: [email protected]
Dec. 12, 2017
The only way to grow and progress in your development career is to be constantly learning. In this episode we talk with Thomas Feeley (@thomasdfeeley), who has spent his development career learning new skills to keep up with the ever changing development landscape. During our conversation we discuss why it's important for developers to be constantly learning and how it supports career growth. We discuss methods for determining what to learn and how to grow and tools to use to support that growth. Key Takeaways Continuous learning allows you to grow your development career in ways that you are passionate about, not just in ways your project dictate. Introspective learning: Asking "Why" questions to learn when to use that tool, framework or understand a requirement. Expansive learning: Asking "What" and "how" questions, to learn where you need to build-up your knowledge of the tasks surrounding your development. Links from this Episode We fired our top talent. Best decision we ever made The Saga Continues by Wu-Tang Automating Your Workflow with Gulp.js by Zell Liew tomfeeley.com Have an idea for a future episode? Tweet Us: (@devuppodcast) Email Us: [email protected]
Nov. 14, 2017
Development is not just an activity, it is a state of mind. In this episode we sit down with Colby Cook of Genuine (@wearegenuine) and talk about what it means to have a developer mindset. In our conversation we discuss what development has in common with construction, why approaching development as a series of steps is important and what you need to know about yourself as a developer. Key Takeaways Remember to approach development as a series of steps that build ontop of each other. Be mindful of what problems you are trying to solve, only build to solve those problems. Keep in mind who you are, what you know and what you don't know. Use your team to balance stengths and weaknesses. Links from this Episode Genuine View of Chicago Previous Episodes Mentioned -Taking Risks Have an idea for a future episode? Tweet Us: (@devuppodcast) Email Us: [email protected]
Oct. 10, 2017
An important part of your development career is understanding when and how to take risks. In the first episode of season two we sit down with Jim Fisk (@jimafisk) and Stephanie Luz (@SayStephanieNow) of Jantcu (@jantcutech) and talk about taking risks as a developer. In our conversation we discuss why taking risks is important, the two types of risks you'll face and how to balance risk with reward in development. Key Takeaways Risk can be a catalyst for career growth. Without taking risks you’ll stagnate as a developer. Overt risks are easy to quantify and measure. Covert risks are harder to quantify and take a long time to measure. Questions to ask when taking a risk What is the worst potential loss? What is the best potential gain? Does the gain outweigh the loss? (to you) Links from this Episode Jantcu JAMStack Previous Episodes Mentioned Asking for Help Have an idea for a future episode? Tweet Us: (@devuppodcast) Email Us: [email protected]
Aug. 8, 2017
In the final episode of season one we discuss the one constant in your development career, change. We focus the conversation on three main areas of change; in your projects, in your role & responsibilities and in your life. Highlighting ideas from previous episodes we talk about how to approach changes in these areas with a constructive, positive mindset. We end the episode with a few announcements about changes coming to the podcast, as well as, a few bloopers. Special Note A big thank you to Jake Rainis (@jakerainis)for his hard work and partnership in making this first season a success. We will miss him as a host, and wish him the best! Be sure to follow Jake at jakerainis.com Why managing change is important Not being able to handle changes, turns them into roadblocks Taking control of changes, turns them into positive learning experiences. Not being fearful of change provides for new opportunities and growth. Managing Project Changes Be confident in saying, Yes, No or I Don't Know. Deliver thought out estimates and defend them. Develop a plan to accomplish the changes. Managing Role & Responsibility changes Get comfortable with being in uncomfortable situations Treat mistakes as learning opportunities. No matter your role, lead by example. Managing life changes Establish long term and short term goals Maintain a healthy work/life balance Keep your day fresh and find daily positive opportunities. Links from this Episode The Clean Coder* by Robert C. Martin Previous Episodes Mentioned Using D.U.M.B goals and S.M.A.R.T goals to grow your development career. Why it is important that you maintain a healthy work/life balance. The three key phrases you need to know to be a great developer. Get comfortable being uncomfortable. Handling Mistakes Gracefully as a Developer Leading by example Developing a Plan Task Estimation Techniques Keeping your Day Fresh Listener Challenges Tweet us how you manage changes positively. *We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.
July 25, 2017
At some point every developers will hit a slump and find their days feeling stale. To keep your development career progressing and exciting it is important that you find ways to keep every day "fresh". In this episode we discuss why it is important to find new development challenges everyday and avoid slipping into a stale daily routine. We offer a few ideas on how to find new daily challenges to inspire you to keep your day "fresh". Why keep your day “fresh” Helps keep you inspired and engaged with your projects/work. Helps you to continue to innovate in your development approach Putting yourself in position of new challenges and unknowns helps you grow. Ideas for how to keep your day “fresh” Set aside time to learn a new language or technology Identify repetitive tasks and either delegate or automate them Surround yourself by new and positive people Get a change of scenery by moving your desk, or yourself. Listener Challenges Share with us what “keeping your day fresh” means to you. Think about past experiences,what excited you about development how can you capture that day to day? Seek out new opportunities and challenges, do not wait for them to come to you! Get up take a break, walk around, you need a breath of fresh air! Links from this Episode Taking People with you* By David Novak Fluid Stance Board* Previous Episodes Mentioned How you identify, treat and prevent the three types of developer burn out. Avoiding Development Stress Task Estimation Techniques Using D.U.M.B goals and S.M.A.R.T goals to grow your development career. How to give and receive feedback Establishing Office Connections To get more done as a developer you need a personal task management system. *We are a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for us to earn fees by linking to Amazon.com and affiliated sites.
July 11, 2017
The path of development is full of wrong turns, pitfalls and mistakes. You cannot control when a setback will occur on your project, on your team or in your career. What you can control is how you react to the situation. In this episode we discuss what to do when development setbacks occur and how to approach them with a positive mindset. We outline a four step approach towards tackling setbacks and turning them into grown opportunities. Four Steps for Dealing with Setbacks Acknowledge: Accept that a mistake has happened, do not ignore it. Understand: Evaluate why the setback occurred. What lead up to it? Plan: Establish a plan of attack to fix the problem and prevent it from happening again. Execute: take action on your plan and monitor your progress. Key Takeaways Setbacks are going to happen in your projects, teams, career you cannot control when setbacks occur, but you can control your reaction to them. When faced with a setback: Acknowledge, Understand, Plan and Execute. Don’t dwell on your past mistakes, always focus on what is next. Listener Challenges Share with us how you have dealt with development setbacks. Reflect on how a past setback has helped your development career grow. Links from this Episode Hit by a Bus Scenario Previous Episodes Mentioned Establishing Office Connections
Disclaimer: The podcast and artwork embedded on this page are from Mike Miles, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.