v0.1 New Car-eer Smell

Welcome to the first edition of patchNotes. I'm Ian, a former accountant turned software engineer. For years I battled burnout before realizing I needed to make a change. When I finally made the leap, I struggled to find guidance that truly resonated with me.

That's why I started patchNotes: a weekly(ish) newsletter for career changers, especially those breaking into tech. Here, you'll find honest career advice, practical tips, and a little motivation to keep you moving forward. Career pivots aren't easy, but they're made possible through small, consistent actions. Let's get started!

👀 Decoding Career Pivots

Career transitions come in a few broad types. It helps to know what you're up against. Which one are you tackling?

• Industry Transition: Move to a new industry but within the same function.
  Example: Accounting in Manufacturing → Accounting in Fintech.
  (low difficulty)
  
  Every career transition has its challenges, but breaking it into smaller, strategic moves can make the leap seem less daunting. By transitioning industries, we can reduce the change to a more manageable chunk where our transferrable skills are easier to communicate to potential employers.
• Functional Transition: Change your role but stay in the same industry.
  Example: Accounting in Manufacturing → Software Engineering in Manufacturing.
  (medium difficulty)
  
  The functional transition is tricky, but if you have been at your employer for a while, you can use your relationships and influence to create opportunities that might never be available to an outside candidate. I've seen organizations bend backward to create roles for the right person. A few large employers even have programs just for this kind of reskilling. You will never get what you don't ask for, so why not ask?
• Double Jump: Switch both industry and function.
  Example: Accounting in Manufacturing → Software Engineer in AgTech.
  (high difficulty)
  The path I chose (unknowingly) was the dreaded double jump. It's tough but absolutely doable. Creativity, patience, and a little luck are key. My best advice? Build business-like side projects, contribute to open source, or find freelance clients to prove you can do the work. Always be networking - your next opportunity is just one connection away.

🦾 Self Check: Frame Up Your Pivot

Every successful pivot requires a mix of mindset, strategy, and action. It's helpful to spend just a moment to frame your approach. Now that you have a basic framework for understanding your pivot, here are three prompts I want you to consider:

1. Smaller jumps or one giant leap?
No pivot needs to be a giant leap. Consider transitioning to a related industry or shifting functions within your current employer. Think of your career transition more as a series of strategic moves to move you toward your larger goal. Each step builds on the last and reduces your perceived risk. Always do what works for you.

2. What if it was just... easy?
I was pretty good at dreaming up all the ways my career pivot could go wrong, but they almost never happen. I want you to consider another potential scenario: what if everything went right? What does success look and feel like to you? What steps would you take to make it happen? Visualizing success can make it easier for you to plot a roadmap and stay motivated for the long term.

3. What if you had to do it today?
Imagine circumstances changed, and you had to pivot today. No time for overthinking. What's the very first step you would take? Who would you reach out to for advice and support? Crisis mode can help eliminate noise and reveal clear actionable steps. Write them down, then start executing on what's within your control.

🐛 Bug Fixes: Overcoming Fear Traps

Fear is a natural unavoidable part of doing hard things. Don't let it derail you. Most fears are bigger and scarier in our heads than they are in the real world. Let's reframe a few common ones together.

Fear: AI will replace all tech jobs.
Reality: Tech isn't going anywhere. AI is an amazing tool for software engineers. Learn how to leverage it. Don't fear it; make it an ally.

Fear: I'm not smart enough to work in tech.
Reality: You are. I guarantee it. Everyone feels lost in the beginning. Focus on consistent practice. Stay curious.

Fear: I'll never get a job in big tech.
Reality: Most tech workers don't work for big tech companies. Startups, medium-sized companies, and non-tech companies all need tech talent too. Look beyond FAANG.

Fear: I have no idea where to start and its paralyzing.
Reality: Start anywhere. Where you start is less important than starting. Action over-optimization. Choose one learning resource (check Quick Bytes) and trust the process.

Fear: What if I fail?
Reality: Failure is rarely fatal. Harness the feedback from failure. Each misstep is a lesson. Just learn from it and move on.

"Feel the fear and do it anyway!" - Susan Jeffers

⚡️Quick Bytes

Don't delay; start learning today:

• CS50: Harvard's free introduction to computer science course available on edx. Perfect for complete beginners. This is one of those "I can't believe this is free" resources.
• Free Code Camp: Learn the basics at your own pace. FCC grows daily, has an awesome YouTube catalog and is a must bookmark for any new developer.
• The Odin Project: Dive deep into their well-curated web development curriculum. I've personally used TOP resources to learn webdev skills!

📝 Final Notes

Thanks for reading the first edition of patchNotes. No matter how small, every single step counts. Focus on progress, embrace mistakes, and keep learning. If you enjoyed this, share it with a friend who's thinking about their next move. You've got this!

Cheers,

Ian

P.S. Forward patchNotes to a friend! or if this edition was really bad maybe an enemy!? 🤔