Episoder
-
LinkedIn is a great resource for connecting with people, but it can also cause serious mental health challenges - and even lead to burnout. If you're looking for a job or just trying to find customers, there are some features of LinkedIn that can ruin your personal peace and drive your anxiety through the roof.
In this episode I share some ways I've helped my tech career coaching clients avoid LinkedIn becoming a problem. Most of these center around avoiding comparing yourself to other people. As Gary Vaynerchuk famously recommends, "produce don't consume". If you follow some of the tips in this episode, you'll be able to responsibly use LinkedIn - and not let it use you!
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:16) 5 Ways to Keep Calm on LinkedIn
(1:38) 1. Avoid Accomplishment Signals
(4:08) 2. Use, Don't Consume
(7:45) 3. Don't Engage Rage Bait
(11:02) 4. Don't Attend Unjustified Meetings
(14:19) 5. Keep Your Network RelevantVisit me at thrivingtechnologist.com
-
Are you a programmer, or in any individual contributor tech role really? Considering switching into management? Be VERY careful. Most companies will not prepare you for what it takes to really be an effective manager. If you've ever been upset with a manager or felt like they weren't equipped to do their job, it's probably because they were promoted due to their success as an individual contributor - but weren't taught effective management techniques and strategies.
In this episode, I'd like to help you avoid being looked at as incompetent by other programmers or anyone in any software development role. You already know that programming and other tech jobs require intentional and ongoing study and improvement. Management is no different!
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:56) 5 Skills To Become a Great Manager
(2:06) 1. Holding People Accountable
(4:24) 2. Taking Responsibility for Others
(8:45) 3. Making Yourself More Available
(13:17) 4. Studying and Practicing Management
(15:56) 5. Being an Incentives TranslatorVisit me at thrivingtechnologist.com
-
Mangler du episoder?
-
If your tech career isn't what you want it to be, it could be a mild annoyance - or something urgent. Knowing how ready you are to actually make a change is important before you take any action that could change the course of your life and career.
When I started career coaching, I noticed sometimes tech professionals would come to me frustrated about their career but not really willing to change. After a while I began using motivational interviewing. This is a technique I use to help me figure out how ready someone is to really make a change in their tech career.
If you're thinking of getting a promotion, switching roles from perhaps programming to something like product management, UX, or data science; or looking to just find a better job - you should assess how urgent the change really is. In this episode I offer 5 stages of readiness for change along with symptoms you can experience at each of them. I hope this helps you know if your tech career is actually in a better place than you thought - or if it truly is time to make a change today!
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:06) 5 Stages of Readiness for Tech Career Change
(1:16) 1. Contemplation
(1:56) 2. Mild Irritation
(2:30) 3. Active Exploration
(3:41) 4. Serious Consideration
(4:37) 5. Urgency and DesperationVisit me at thrivingtechnologist.com
-
Today most tech companies engage in agile signaling - without even knowing it. They do nothing to make it easy to adapt to change, but put on a show to pretend they're agile.
Many software developers and other professionals in the industry, even those with long careers, have never been on project with a truly agile software development process. And so it's not uncommon to hear software engineers and project managers talk about how much they "hate agile" behind closed doors.
A select few understand what being agile really means. It means working together in a way where adapting to change is easy. For those unfortunate people, it can feel like gaslighting to work for these companies. Tech workers all over the industry are expressing more disgust with scrum and agile than ever. And when the SAFe, or "Scaled Agile Framework" arrived - it signaled a final nail in the coffin of many companies ever being able to realize the true benefits of being agile.
In this episode I'd like to help you understand two things. First, we we need agile development more than ever today. With the arrival of AI, software projects are getting disrupted faster than ever and need to adapt. And who knows what the future could bring! I'll also help you understand 4 key events in the history of the software industry that caused the definition of the word agile to essentially mean "anything BUT change"!
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:31) 1. Do We Even Need Agile Development?
(1:37) 1.1 Inability To Respond To Market Change
(3:55) 1.2 Over Budget and Late Projects
(5:50) 2. 4 Key Events That Co-Opted Agile
(6:16) 2.1 Burn-Down Charts and Velocity Tracking
(9:21) 2.2 Jeff Sutherland's Book
(12:47) 2.3 Agile Certifications
(15:51) 2.4 SAFe (Scaled Agile Framework)
(21:12) Episode GrooveVisit me at thrivingtechnologist.com
-
Does programming ever get tiring? Are you frustrated by being left out of key decisions by the company? You may begin to wonder if you should become a manager.
In this episode I'd like to share 5 important considerations before switching from being a programmer to management. It's common advice that "all programmers must become managers eventually", and I don't agree with this.
There are many ways to grow in our career, and management is just one path. However, for some people it may be the perfect next step. I hope this episode helps you know what you're walking into before you take the step to become a manager.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:13) 5 Signs It's Time to Switch to Management
(1:32) 1. You're More Concerned with People than Technology
(3:42) 2. You Want More Organizational Insight
(5:37) 3. You Hate The Technical Interview Process
(9:39) 4. You Want To Work Less Overtime
(12:39) 5. You're Tired of Learning New TechnologyVisit me at thrivingtechnologist.com
-
Many programmers are stuck in their career today, but they place the blame on everyone else. Yes, there are some difficult things going on in the tech industry. But one of the biggest reasons programmers stop growing, is they don't get help.
In this episode, I'd like to share the things I've learned after coaching over 100 software professionals that keep us from getting the help we need.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(4:56) 6 Reasons Why Tech Workers Stay Stuck
(5:06) 1. Skepticism of Marketing and Sales
(8:28) 2. False Sense of Uniqueness
(12:43) 3. Knowledge-Inflated Pride
(14:45) 4. Fear of Relational Intimacy
(17:10) 5. Internet Addiction and Distractions
(20:57) 6. Opportunity Cost of InactionVisit me at thrivingtechnologist.com
-
Want to quit working for companies as an employee, make more money, and choose the clients you work with? It might be time to go solo - as a technology consultant. To be successful, you need to be smart about how you start.
In this episode, I share the exact steps I took to become a solo technology consultant offering software architecture and a variety of other professional services. Whether you're a programmer, in QA, DevOps, do Product Management, Data Science, or any other software development technology role - a technology consultant is not a contractor. You are actually starting a business, and so you need to think like one!
I hope this episode helps you avoid some of the pitfalls that software engineers and other tech professionals can fall into when they try to work for themselves.
Learn about Solopreneur Jumpstart, a coaching package to bootstrap your solo consulting business https://thrivingtechnologist.com/services/software-development-coaching/solodev-coaching-package/
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(2:55) 10 Steps to Become a Solo Technology Consultant
(3:00) 1. Design Your Services
(6:38) 2. Discover The Client
(8:51) 3. Price Your Services
(11:16) 4. Build Client Awareness
(13:37) 5. Incorporate
(16:33) 6. Acquire Clients
(19:01) 7. Negotiate Contracts
(23:34) 8. Manage the Engagement
(26:16) 9. Keep Financial Records
(30:27) 10. Finish Strong and Get a Reference
(34:15) Episode GrooveVisit me at thrivingtechnologist.com
-
Programmers have to learn an incredible amount of information to even BEGIN to be effective at their job. So it's only natural that we don't like to find out something we learned - is wrong in a different context. With so much invested, being open to the possibility that there's a better way to do things can be hard.
In this episode, I share some mindset limitations that we can fall into in tech job roles. We can feel so strongly about experiences we've had, that they blind us from being open to other equally valid perspectives. Every one of these is a mistake I've made more than once in my career.
I hope by being aware of these, you don't end up believing lies. Instead, this information can help you make wiser decisions on your software project - so you don't end up looking like a fool.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:43) 5 Mindset Limitations Programmers Believe
(1:53) 1. Binary Thinking
(5:16) 2. Anecdotal Overconfidence
(12:12) 3. Absolutist Stances
(16:05) 4. Recency Bias
(19:03) 5. Vanity MetricsVisit me at thrivingtechnologist.com
-
Ever seen management bring in a technology consultant, and suddenly they're open to ideas you've been telling them all along? When this first happened to me, I figured technology consultants were probably just better at selling snake oil.
But halfway into my career I became a software development technology consultant, and I learned they were masters of one thing I sucked at - communication. Here's the good news: you don't have to become a technology consultant to be a master of communication. It's simply a decision you make to focus on it.
In this episode, I share 9 ways you can communicate like a consultant, that will get people to stop and listen to what you have to say with more authority and urgency on your software projects. Whether you're a software engineer, in QA or DevOps, or a product or product manager - we all respond to persuasive and informed communication the same way.
I hope this helps you get unstuck in your career in technology, and achieve things you never thought were possible on your software development project!
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(3:10) 9 Ways to Communicate Like a Consultant
(3:17) 1. Be Business-Focused
(5:11) 2. Presentation Skills
(8:20) 3. Adapt To Your Audiences
(12:25) 4. Frequent Feedback Loops
(15:26) 5. Negotiation Skills
(18:02) 6. Healthy Resistance to Rushing
(20:34) 7. Project Documentation
(23:38) 8. Client Relationship Management
(26:34) 9. Continuous Learning
(30:20) Episode GrooveVisit me at thrivingtechnologist.com
-
Most programmers have considered self-employment at one time or another, but fear grips them when they think about how to even get started. When I began working for myself 7 years ago, I had no idea how to transition to being self-employed, but I knew I couldn't stand working for corporations any longer.
In this episode, I'll share the most common fears any programmer faces when they think about what it might be like to work for themselves. And for each of these fears, I'll offer some perspective on how I did it, and you can too.
With the uncertainty of the software industry today (and really any tech job), relying on corporations for employment over our entire career may not be wise in the long run. I hope this episode offers some hope that self-employment isn't impossible as a programmer. But there is no escaping that you'll need to face your fears head on - and overcome them!
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:38) 1. 3 Reasons Programmers Fear Self-Employment
(1:44) 1.1 Financial Uncertainty
(2:46) 1.2 Lack of Business Skills
(3:54) 1.3 Comfort With Current Tech Job
(5:46) 2. How To Overcome Self-Employment Fears
(5:54) 2.1 Financial Planning and Savings
(9:02) 2.2 Gradual Skill Development
(11:53) 2.3 Start Small and Build ConfidenceVisit me at thrivingtechnologist.com
-
It's finally sinking in. Your software project is FAKE agile. Is there anything you can really do about it?
The sad reality is that more companies have fake agile software development processes than those that are authentic. You can fight tooth and nail to try and change the system, or you can accept when there's nothing you can do.
Being a truly agile software company is not usually something any individual programmer or manager can change. It has to start from the top. If the company doesn't do agile budgeting and have a culture of adapting to feedback, they are a typical feature factory focused on output over outcomes.
In this episode, I offer some practical ways to let to of your frustration and do the best job you can given the circumstances. If you're the type of software engineer, manager, or any other tech job role that considers themselves a change agent - you may be challenged by this one.
But this episode isn't for everyone. It's for those of us who are experiencing mental health issues, burnout, and anger over our software project being fake agile. I hope it offers some relief.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
RELATED EPISODES
Spot a Fake Agile Team in Under 7 Minutes!
https://youtu.be/H6GdK-dChtYAn Agile Budget Keeps You From Being a Code Monkey
https://youtu.be/pG4wNLopMZAIs Your "Agile" Backlog Really a Waterfall Project?
https://youtu.be/OosYzkP-pLkCan User Stories Make Software Projects Late?
https://youtu.be/NavlPobhj7AAre Programmers Really To Blame For Bad Estimates?
https://youtu.be/m5A1Wg8hYGoChapter markers / timelinks:
(0:00) Introduction
(1:30) How to Cope With FAKE Agile Development
(3:25) 1. Stop Forcing Change
(5:10) 2. Exercise
(7:25) 3. Become a Requirements Lawyer
(10:33) 4. Charge for Changes
(13:12) 5. Protect Your Reputation
(15:12) 6. Define Your Own Success
(21:54) Episode GrooveVisit me at thrivingtechnologist.com
-
If you're bothered by the problems in the tech industry, I am too. But while every day we seem to hear more and more negative news about it - we're actually paying attention to the wrong problems.
There are many things wrong with the software industry, but very few we can control. And one thing we can control, is how much we understand each other.
Programmers complain that managers set unrealistic deadlines. Managers complain that programmers are lazy. And these are just two examples of the many different tech job roles where misunderstanding each other causes us to feel frustrated and hopeless.
In this episode, I'm sharing my vision for how we can help each other get out of complaining about the tech industry - and DO something about it. While none of us is empowered to fix every problem out there, we can at least fix what's right in front of us.
This episode marks a new chapter for the channel. I'm renaming it to Thriving Technologist! Thriving because we don't just need to be healthy in tech - we need to thrive and succeed. Technologist because we need to help not just software developers thrive, but everyone in the tech industry.
Only when we have empathy for each other and stop seeing each other as enemies, can we stop the anger and begin building a better tech industry for us all to work in. So this is an official welcome to all the people who are not programmers over the years to join us in the effort to create a healthier, more sustainable workplace in tech for us all.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Visit me at thrivingtechnologist.com
-
Learning new technologies, frameworks, and processes as a programmer gives you a feeling of accomplishment. But unchecked, learning can become a dangerous addiction that damages your software development career.
In this episode, I share how software engineers can cap their earning potential if they fall into common traps when learning is the absolute wrong thing to do. If you want to have a long career in software and get the rewards, recognition, and success you deserve - knowing when to (and not to) learn is essential.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:22) 1. How Learning Addiction Harms Tech Careers
(1:28) 1.1 Procrastination
(3:03) 1.2 Sunk Costs
(3:57) 1.3 Declining Value
(5:41) 1.4 Social Avoidance
(7:15) 1.5 Work/Life Imbalance
(8:48) 2. How To Know When Learning is a Trap
(8:54) 2.1 Self-Delusion Your Project Requires It
(10:01) 2.2 Self-Delusion You Need It To Get a New Job
(11:20) 2.3 Influencer Hype and Vanity Metrics
(13:03) 2.4 Tech Industry Pushes Fear of Missing Out (FOMO)
(15:10) 2.5 Current Challenge Looks Easier in New TechVisit me at thrivingtechnologist.com
-
Have you ever seen another programmer who wasn't as skilled as you get promoted? Did you tell yourself management was making a mistake?
Earlier in my career I didn't realize I was doing some things that caused managers to lose confidence in me. I would spend all my time writing code and never think about how I came across to other people.
In this episode, I share some harsh truths I've learned about how being a software engineer can cause us to do things we think the company wants - that actually hurt our reputation in the long run.
Companies are actually paying you for confidence as a programmer. And this episode is full of practical strategies for making sure you don't fall into traps that stop you from getting recognized for the great code you write as a programmer - before your career is really getting started!
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:19) 1. What Companies Really Want From Programmers
(2:12) 2. How To Build Employer Confidence as a Programmer
(2:22) 2.1 Minimize Communicating Problems and Doubt
(5:42) 2.2 Repeat Management's Desires
(7:46) 2.3 Anonymize Blame on Dependencies
(10:57) 2.4 Reduce Your Throughput
(14:52) 2.5 Elevate Your Coworkers
(17:05) 2.6 Over-communicate Status
(20:11) 2.7 Highlight Discovered Shortcuts
(22:20) 2.8 Document Verbal Decisions
(26:58) Episode GrooveVisit me at thrivingtechnologist.com
-
Making videos, podcasts, or blogs could be just what your career as a programmer needs. But it could also be a complete waste of time. Many programmers become influencers, but there are two very different reasons for doing so.
In this episode, I share the difference between being a pure influencer, or posting online for content marketing. Content marketing is helping people solve some problem they have with your content to encourage them to consider doing business with you.
If you're considering working for yourself by starting a software product company, becoming a consultant or freelancer, or selling courses on software development or engineering - becoming an influencer through content marketing is the key to making sales and actually having a business.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:27) 1. The 2 Purposes of Online Content
(1:31) 1.1 For Social Status and Influence
(3:49) 1.2 Demonstrating Competence
(6:09) 2. How Content Marketing Helps Your Career
(6:14) 2.1 Getting a Better Job
(7:38) 2.2 Sell Products and Services
(10:03) 3. 5 Myths of Content Marketing
(10:12) 3.1 Your Ideas Must Be Original
(12:31) 3.2 You Have To Post Everywhere
(13:40) 3.3 You Have To Post All The Time
(17:04) 3.4 You Should Post a Variety of Topics
(20:40) 3.5 You Must Post in All Mediums
(23:51) 4. Building a Business Through Content
(24:13) 4.1 Give Away Something Valuable
(26:37) 4.2 Have a Contact Form
(29:40) 4.3 Get Referrals Through Shares
(32:53) Episode GrooveVisit me at thrivingtechnologist.com
-
Six years ago I was suddenly struck with chronic insomnia where I couldn't sleep more than 3 hours a night. This lasted for nearly 3 years, and I struggled through sleep studies, behavioral changes, and all the typical tips you read online about overcoming insomnia.
Working as a programmer in the tech industry can create a lot of anxiety because we work with our mind. And if your mind is stressed out, add on to that the pressure of personal relationships and finances - and you've got a recipe for horrible sleep problems.
What ultimately treated my insomnia and helped me heal was a combination of psychological, behavioral, environmental, and physical changes I made. In this episode I share 25 practical steps you can try if you're personally struggling with getting a good night's sleep. I hope if you've lost hope that healing your insomnia is possible, my story and what I did gives you the courage to give it another try.
Learn about the CBT-i app:
https://www.ptsd.va.gov/appvid/mobile/cbticoach_app_public.aspJoin my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:15) Negative Effects of Insomnia
(2:19) Categories of Insomnia Solutions
(2:29) 1. Psychological Sleep Solutions for Insomnia
(2:35) 1.1 Wrap Up Your Workday
(3:57) 1.2 Keep a Notepad By Your Bed
(5:03) 1.3 Schedule Worry Time
(7:04) 1.4 Do 1 Thing You're Putting Off
(8:41) 1.5 Reduce Social Media Use
(9:21) 2. Behavior Sleep Solutions for Insomnia
(9:27) 2.1 Set a Realistic Sleep and Wake Time
(11:54) 2.2 Don't Look at The Clock
(12:58) 2.3 Only Use Your Bed for Sleep or Sex
(14:10) 2.4 Stay off Devices for an Hour Before Bed
(15:19) 2.5 Quit Drinking or Doing Drugs
(16:35) 3. Environmental Sleep Solutions for Insomnia
(16:40) 3.1 Keep Your Room Dark and Cold
(18:28) 3.2 Use a Fan or White Noise Generator
(19:37) 3.3 Use Tungsten Light Bulbs
(21:32) 3.4 Use a CPAP Machine or Tape
(23:05) 3.5 Side Sleeping with a Tall Pillow
(24:20) 4. Physical Sleep Solutions for Insomnia
(24:24) 4.1 Don't Eat or Drink After Dinner
(25:33) 4.2 Cardio Exercise Every Morning
(28:45) 4.3 Reduce or Eliminate Caffeine
(31:07) 4.4 Drink Water Throughout the Day
(32:29) 4.5 Get Enough MagnesiumVisit me at thrivingtechnologist.com
-
We programmers love to "do it ourselves", and this can help us stay productive and keep ourselves busy. But the dark side of this tendency, is that it can make it harder to get help - when we actually need it.
In this episode, I share some ways I've learned that software engineers are trained by society, the workforce, and the software industry to resist getting help from others. Then I offer some practical questions you can ask yourself to know if you're in a situation where you should really adopt the DIY mindset - or avoid getting trapped into learning something you don't need to.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:22) 1 3 Reasons Why Programmers Don't Get Help
(1:28) 1.1 Individualized Education
(2:02) 1.2 Corporate Reinforcement
(2:41) 1.3 Gossip over Substance
(4:49) 2 5 Reasons DIY Can Be a Bad Idea
(4:57) 2.1 Low Repeatability Activity
(6:41) 2.2 Outside Your Core Skill Set
(7:41) 2.3 You've Failed 3 Times
(9:23) 2.4 You Keep Putting It Off
(10:41) 2.5 Easy Access to An Expert
(12:33) Episode GrooveVisit me at thrivingtechnologist.com
-
Ever try to sell someone on why you're the right person for them to hire in tech? Or maybe you have a software product or offer freelance IT consulting services you need to sell? I'll bet you've run into the situation where the other person you're talking to doesn't seem to "get" why you're the best solution to their tech problems.
In this episode, I share what I've learned through digital marketing about how to really connect with the person you're convincing in tech, so they can understand the value you offer - and buy your idea. This can help you escape the corporate grind and work for yourself as an entrepreneur, consultant, coach - or sell courses. But it can also help you with the everyday challenge of convincing software architects, managers, and anyone you work with to support any idea you have.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(3:02) Episode Outline
(4:25) 1 How Aware Is Your Prospect of The Problem?
(5:10) 1.1 Problem Unaware
(7:27) 1.2 Problem Aware
(9:46) 1.3 Solution Aware
(10:43) 1.4 Ready to Buy
(13:46) 2 How Well Do You Know Your Prospect?
(14:44) 2.1 Basic Demographics
(16:12) 2.2 Industry-Specific Demographics
(18:21) 2.3 Psychographic Profile
(21:29) 3 Are You Selling To The Right Prospect?
(21:37) 3.1 Who's The Ultimate Buyer?
(23:52) 3.2 What's The Prospect's Budget?
(25:47) 3.3 How Urgent Is Solving The Problem?Visit me at thrivingtechnologist.com
-
On the first software project of my career, I thought doing a good job was all that mattered to move ahead. And while I was successful, I was manipulated by many other programmers through political games. After that experience, I was tempted many times in my career to fight dirty. And sometimes, I made the wrong decision.
In this episode, I share the reasons why we're tempted as coders on software projects to throw ethics to the wind when the temptation for money, power, or prestige are strong. And how falling prey to that temptation may get you ahead in the short term, but it hurts you in the end.
I hope you find some encouragement to take the high road when faced with political games on software development teams, and refuse to bend to other people's will who are unethical!
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(2:04) 1. Why Programmers Are Tempted To Fight Dirty
(2:09) 1.1 High Stakes Competition
(3:00) 1.2 Visibility and Recognition
(3:50) 1.3 Fear of Obsolescence
(5:32) 1.4 Cultural and Structural Encouragement
(8:22) 1.5 Misguided Notions of Success
(9:37) 2. Resisting Corruption in Tech
(10:31) 2.1 Long Term Results & Reputation
(12:39) 2.2 The Power of Networking
(14:54) 2.3 Personal Peace and Satisfaction
(17:17) 2.4 The Ripple Effect of Positivity
(18:42) 2.5 Faith In Doing The Right Thing
(20:10) Episode GrooveVisit me at thrivingtechnologist.com
-
After my first decade of coding, I learned so much I thought: "I must be at least somewhat intelligent, right?". But there was something more valuable I lacked - wisdom. Without wisdom, you'll make decisions in your career that look right in the short term - but turn out disastrous over time.
Wisdom is the ability to make decisions when the rules don't apply. There's no book you can read, no guide to follow, and no clear cut answer. It's derived from experience, sound judgment, a broad perspective, and considering the ethical implications of a decision. And if you learn to cultivate wisdom, you can achieve the things that really matter in your career - and life.
In this episode I share why people in tech careers often mistake intelligence for wisdom. Then I'll help you understand why our industry is so prone to making unwise decisions. I'll go on to help you see the dangerous outcomes of short-term thinking. And finally, I'll share some practical things you can do to become a wiser programmer - and technologist in general.
Join my Patreon:
https://thrivingtechnologist.com/patreonLearn about one-on-one career coaching with me:
https://thrivingtechnologist.com/coachingTechRolepedia, a wiki about the top 25 roles in tech:
https://thrivingtechnologist.com/techrolesThe Thriving Technologist career guide:
https://thrivingtechnologist.com/guideYou can also watch this episode on YouTube.
Chapter markers / timelinks:
(0:00) Introduction
(1:23) Defining Intelligence and Wisdom
(2:14) Stories of Intelligence and Wisdom
(5:10) 1. How Tech Jobs Confuse Intelligence and Wisdom
(5:20) 1.1 Equating Problem Solving with Broad Insight
(6:27) 1.2 Prioritizing Speed over Sustainability
(7:51) 1.3 Specializing vs Holistic Understanding
(9:44) 2. How Ignoring Wisdom Hurts Us in Tech
(9:51) 2.1 Ethical Implications
(12:42) 2.2 Short-Term Over Long-Term Thinking
(13:45) 3. How To Be a Wiser Technologist
(13:52) 3.1 Expand Your Breadth of Knowledge
(16:35) 3.2 Get a Mentor
(18:30) 3.3 Reflect and Be Mindful
(22:02) 3.4 Seek the Counsel of Generalists
(25:02) 3.5 Engage with Non-Technical CommunitiesVisit me at thrivingtechnologist.com
- Se mer
