This week we talk about the Sunk cost bias, also been called the "Concorde fallacy" when the UK and French governments took their past expenses on the costly supersonic jet as a rationale for continuing the project, as opposed to cutting their losses (source: Wikipedia).As you'll see we encounter it in every part of your life including coding and career.We talk about various concrete examples:- Standing in a line for too long making yourself "stand it out" because you already lost too much time. Julian fixed this the other day by setting a deadline when to cut his losses.- Keep investing in a complicated (sub optimal) programming language while there are better ones (e.g. Python!)- Investing more effort in a software solution with a sub optimal design. The Zen of Python offers a good criteria here: "If the implementation is hard to explain, it's a bad idea". Sometimes you need to heavily refactor, taking one step back to be able to move two steps forward.- It also happens in one's job, by staying into a comfortable yet underappreciated role knowing you can do better elsewhere, yet you hope one day the situation will (magically) improve.- Another good example of the sunk cost fallacy is "having to finish books", the self imposed pressure of having to read books cover to cover even if you don't like them.- And our last example is around investing, the difficulty of cutting one's losses when money has been already invested. Ego and social pressure make this even harder.Book about cognitive biases: Thinking, Fast and Slow by Daniel Kahneman.CTA: take note of what is going on in your life, where your time / money / effort are going, then ask yourself if you are getting the results you want? Is it time to cut losses and move on?And if you see a sunk cost in your Python career, maybe it's time to hop on a strategy session with us or hit us up on Slack.

This week we talk about persistence and its importance for developers.The skill of learning (complex) things fast and persisting through the difficulty that accompanies it is one of the best skills you can develop. After all we don't always get to choose what technology to use. And there is no better feeling of accomplishment after having struggled through a complex problem.Other areas we talk about is pushing back on requirements, the patience you have to have if results are not showing up immediately and a powerful quote of The Slide Edge.Enjoy and if you're enjoying the show, please leave us a rating on your app of choice! It'll help us get the message in front of even more developers :)

A common issue is the fear and uncertainty around employment our veterans face when leaving the military. After years of solid structure, coming into the civilian world and being left to fend for yourself and not know if you'll be able to land a "9-5 job" can be incredibly daunting.This is the situation our guest found himself in when he left the Australian Army.In this very special episode, I speak with one of my best mates, Ranui "Ra" Rice.Ra tells the story of how he left the military and eventually worked his way into the Tech Industry, discovering his passion for front-end development and graphic design.His journey was not linear and Ra shares many tips and lessons he learned over the years. It wasn't easy but his mindset and determination were his greatest asset.There's a lot to digest in this episode so listen to it once, then listen to it again and take notes!Two of my favourite quotes from Ra:"Time is wasted when you don't do anything with it"."Treat yourself the way you'd treat others."If you'd like to say g'day to Ra, look him up on the PyBites Slack - "Ranui Rice".Ranui's Website: Coming Soon- Julian

Every time you go up you're inevitably going to hit more challenging problems which takes a lot of mindset.Today we talk about 3 occasions where we entered new levels, met new devils and how we dealt with it:1. Getting our first coding role:How you have to dive straight in.Step back a bit, setting expectations with the team (see also episode #021).Try to gain a quick win to boost your confidence.2. Working out:To make gains lift heavier which takes mindset (as well as the discipline of going to the gym every single day).However be nice for yourself, adjust to your situation (80% on a bad day is better than nothing).3. PyBites / getting out there:We wrote last week that every developer needs to build up their body of content.We started doing this with our blog and doing the #100DaysOfCode challenge, then building courses / our platform and ultimately becoming coaches.Every step there were new problems and things we needed to learn (and it never stops).Lot of fear, imposter syndrome we had to conquer along the way.For example getting over hearing your own recorded voice, getting on camera, these are now new "normals" which we could not foresee when we started.So the main takeaway: look for new levels, take things head-on, remember that the pain is temporary and you'll look back realizing there was not that much magic. Then repeat.We hope this inspires you to keep challenging yourself continuously, because it's one of the best feelings in life.What we're reading:Bob: Jake VanderPlas' Python Data Science Handbook which you can read online (thanks Jake!)Julian: The Memory Booster Workbook.If you want to be challenged in order to grow as a Python developer, pursuing better career opportunities, come talk to us. We have helped many people achieve those goals and we would love to see you be our next success story.Book a call here: https://pybit.es/apply Thanks for listening and see you in the next episode.

This week we have Drew Kerr on the show, consultant / web developer and like us, big on self development and mindset.We talk about the importance of mindset as a developer and lessons learned from The Last Dance, an amazing documentary about the Chicago Bulls and Michael Jordan:Fail your way forward, often not taught at school (and important to conquer rejections with interviewing).Being present, not to worry about what might go wrong, not to allow failure to even enter your mind.MJ’s “My game is my biggest endorsement” which is closely related to Gary Keller’s The One Thing; it’s easy to get distracted, you should focus on one thing though and do it extraordinarily well.Expect criticism to happen at higher levels, it takes mental strength to block out the negative / distractions and focus on the essentials.Have a relentless work ethic which will have a compound effect over time (“the slide edge”). Adopt the Seinfeld principle, code every day, deliberate practice is key (see also episode #015).This and much more in our new episode.Enjoy and if you like the show please leave us a review.Get in touch with Drew on PyBites Slack or LinkedIn.Books mentioned:Carol Dweck’s MindsetShad Helmstetter’s What to say when you talk to to yourselfCal Newport’s Deep work and Digital minimalismGary Keller’s The one thingJames Clear’s Atomic habitsJeff Olson’s Slide Edge (not sure if we mention it but definitely useful for number 5.)

In this episode I have a chat with long time PyBites Community Member, Rhys Powell, about the skills programmers should have when coming into a coding role or opportunity.As someone who mentors and trains graduates in Python development for success in the industry Rhys has some great insights into what's really needed, what works and what doesn't.One of the takeaways here is that many of the points that lead to success are more around the mindset people bring over the pure technical skill.Some points we raise and discuss in our conversation:What we really need from engineers is a willingness to learn.Problem solving skills are huge. Being able to break down problems is super important.Understanding how you as a person learn."I don't necessarily require a successful outcome, I'd rather know about how you got to your solution."Passion and the enthusiasm to learn and grow weigh more than "just" technical skill.Technical skills can be taught. The enthusiasm cannot.People should ignore the "brand" of the company and think more about what can this company provide me to help me move forward while I'm providing value to them. "Win-Win".The Fear of failure is something that holds a lot of people back.Failure is not a bad thing. Embrace the fact that sometimes you're going to get things "not quite right".We all make decisions with the best of our knowledge at the time and that takes us a step forward.Aim to understand what your customers and clients actually want. Much of the time they don't know what they want.Being able to communicate is incredibly important as a developer.Not documenting is a common pitfall of new developers.Not writing tests is another pitfall. Writing tests makes your life so much easier as a developer.Self-confidence is a big deal. We shouldn't be full of ourselves but we should be confident in our abilities. Imposter Syndrome in the industry is real!You don't need to know the mountain of technology that's out there to come into a dev role. It's your ability to learn the things you need to know when you need to know them that counts.If you want to see more of Rhys, please, please check out his Twitch channel or reach out to him on the PyBites Slack.Twitch: https://twitch.tv/bleachin74PyBites Slack Username: "Rhys"Github: https://github.com/rhyspowellTwitter: https://twitter.com/Bleachin

Today we talk with Paul Nnaoji, software engineer and co-founder of AskAGuru.We talk about how he got into Python and used it to build out his passion project into a startup! AskAGuru solves a real world problem: how to make music sharing more social. Paul used Flask and Vue.js, a decoupled architecture that makes it easier to scale.We also talk about the business and marketing side of things, how to grow an audience and some important leadership and mindset lessons Paul learned along the way.Links:Check out AskAGuru here.Book Paul mentioned: Gilgamesh by Stephen Mitchell.Talk with Paul on PyBites Slack, LinkedIN or IG.

Protect your calendarIn this episode we wanted to address another productivity issue.We talk about the concerning trend of having an open calendar and how detrimental this can be for getting stuff done.We talk about how we balance meetings vs deep work via time boxing. Related essay: http://www.paulgraham.com/makersschedule.htmlMentioned meeting quote: "Meetings are a symptom of bad organization. The fewer meetings the better." - Peter DruckerWe talk about the culture of "now vs when" and how Slack (ironically) gets this down! They seem to have embraced the "when you work, work, when you play, play".We hope that after listening you take control of your calendar and tell us all about it:https://twitter.com/pybiteshttps://pybit.es/communityFinally, at the start of the episode we mention our new, free 6 day training course: The 6 Key Ingredients of a Successful PythonistaYou can get it here:https://www.buildpythonapps.com/Extra Resources:Julian's Reading: Pine Gap: The Inside Story of the NSA in Australia - David RosenbergBob's Reading: Eleven Rings: The Soul of Success - Phil JacksonSerious Python: Black-Belt Advice on Deployment, Scalability, Testing, and More - Julien Danjou

Today we tackle the ugly monster of distraction. We give you some valuable pointers that can reduce the amount of stress that distractions cause:- Work on the 80/20, the stuff that matters and have goals so you know what to aim at.- Time-box your time, including social media.- Airplane mode is your new best friend.- Watch your bio (= willpower).- Social media vicious cycle (story time!)- Go async with online reading, batch articles with Pocket.- Tab galore is bad (unclosed loops!), go minimal, less is more.- An accountability partner increases your focus and therefore reduces distractions.- Disable desktop notifications and uninstall distracting phone apps.- When you work work, when you play play (again, control your phone use).To seriously boost your productivity, gaining valuable hours back every single week, check out our dedicated course: https://pybitesproductivity.com

This week we talk with Patrick Groß, long time PyBites community member and lead developer of Karmabot, the bot that handles karma points and other tasks in the PyBites Slack Community. We talk about how Patrick got into Python and how he really learned it, his switch from a university to a data analytics job and ... his overhaul of our early Karmabot prototype, turning it into the mature open source project it is today (thanks!) You'll learn about the improvements Patrick made to Karmabot, integrating "Hypermodern Python" concepts, and some of the lessons he learned from contributing to open source overall (hint: both tech and soft skills were important!)We hope this episode will inspire you to start (or continue) contributing to open source, it's a beautiful thing.Karmabot project and Hypermodern Python series:https://github.com/PyBites-Open-Source/karmabothttps://cjolowicz.github.io/posts/hypermodern-python-01-setup/To reach out to Patrick:https://twitter.com/patrick_grshttps://pybit.es/community (DM or #karmabot_dev channel ... actually while there let's give him some Karma, just type "@Patrick +++")