Developing Up

Developing Up
By Mike Miles
About this podcast
A podcast focused on the non-technical side of being a developer, because your career is about more than the code you write.
In this podcast

side

developer

Mike Miles

code

Machine generated. There may be errors. Report errors to us.
Latest episodes
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
June 27, 2017
In development some stress helps to provide a sense of urgency. However too much stress can degrade your ability to produce your best work. In this episode we discuss some common causes of stress in development and why they can become problems. We then talk about a few methods you can use to reduce stress in your development career. Causes of development stress Internal: Imposter Syndrome, Real Developer Syndrome, unwillingness to collaborate. External: Pressure from others, Timelines and deadlines, work/life imbalances. Why too much stress is bad Leads to development burnout Can lead to health issues Prevents you from doing your best work How to prevent development stress Remember you are only “building sandcastles” Take a break and step away from the cause of the stress Ask others for help. Links from this episode Deep Work* by Kal Newport How to Invest your Time like Money* by Elizabeth Grace Saunders Listener challenges Share your methods for reducing development stress. Spend a day without context switching. Focus on a single task. Chunk out your next week into buckets of time. Previous episodes mentioned The Four Attributes of a Great Development Team Procrastination vs. Precrastination How you identify, treat and prevent the three types of developer burn out. *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.
June 13, 2017
When it comes to getting tasks completed there are two types of developers. Those who get things done as soon as possible and those who wait until the last minute. Being one is not better than being the other as long as you are able to deliver your best work. In this episode we are discussing the differences between procrastinators and precrastinators. We talk about the pro’s and con’s of each approach and how they affect your development work. Sharing tips to improve your abilities to get things done, not matter which type of developer you are. Procrastination vs. Precrastination Procrastination: Waiting until the last minute to complete tasks. Precrastination: Completing a task as soon as it is assigned. Pros of Procrastination Creates a sense of urgency that forces you to focus on getting a task completed. Helps you to not stress about a task, until you absolutely have to focus on it. Prevents over-engineering by focusing on completing only the work you need to. Pros of Precrastination Creates a sense of urgency to get a task done as soon as possible. Allows for plenty of time to get a task completed. Provides opportunities to revise you approach to a task. Cons of Procrastination Prevents the opportunity to explore different approaches. Provides risk of running out of time to complete a task. Potentially to compromise the quality of work in order to get it done in time. Cons of Precrastination Increases chances of over-engineering a solution. Potentially increased stress over completing a task when it is on your todo list. May be easier to be distracted from what you focus should be on. Tips for Improving as a Procrastinator or Precrastinator Plan out the timeline you have to get work done. Spread out your workload to give yourself plenty of time to think. Focus on creating sustainable habits of your development approach. Listener Challenges Let us know, are you a Precrastinator or a Procrastinator?