Dev Theory - A Web Development Podcast

Shaun and Isaac share their experience in the industry and how they were able to achieve six figure salaries!

In this episode of the Dev Theory podcast, we delve into various topics related to web development and share some personal anecdotes along the way. The conversation starts with a lighthearted discussion about haircuts, a relatable aspect of our lives. From beard grooming to barber visits, it's a glimpse into everyday experiences. Moving on to the professional realm, we explore experiences with a Proof of Concept (POC) project involving an analytics tool. Additionally, there's a mention of work related to code refactoring and workflow improvements. We also touch on the integration of AI in troubleshooting pipeline failures, highlighting the potential of AI-driven solutions in the field. Transitioning to hobbies, we talk about a shared interest in golf, emphasizing the appeal of this recreational activity. That's a wrap for this episode of Dev Theory – Thanks for tuning in! 🎙️

Join us for a thought-provoking episode of "Layoffs," where we explore the complex journey of facing job loss and the transformative power it can hold. In this episode, we delve into the practical aspects of handling layoffs and the potential they have for paving the way to unforeseen opportunities. We begin by examining the intricacies of severance packages – often overlooked but crucial for a smoother transition. Our discussion includes strategies for navigating negotiations and making the most of this phase of change. Moving forward, we take a closer look at the practical side of job hunting – from refining your resume to mastering interviews. Our insights aim to equip you with the tools to approach your job search with confidence and professionalism. Keywords: layoffs, transitions, opportunities, severance, job hunting, resilience, growth, transformation, career journey.

- There are a couple of points that I was wanting Isaac and me to discuss on today's podcast - How to simply form an opinion - here is the path to creating your own opinion - active reading - listen to as many arguments as u can - argue with people smarter than me - fight against my own emotional bias (self-serving bias vs confirmation bias) - think about as many variables as possible - and also the original problem of not remembering. How can I form an opinion or understand something if I can’t remember - How to learn faster, and remember more in an ever-changing career - eliminate the noise How to remember everything you learn by removing these things: - information streams that cause overload - multitasking - distractions - Once you have only one source of information coming in, you can use these techniques to help you remember and comprehend the information - recall - Feynman (*Fine men*) technique - spaced repetition

Shaun and Isaac catch up on life and talk about manager feedback

We're talking about everything workflow! You'll learn what a typical agile environment workflow looks like. You'll also hear Isaac and Shaun talk about how they work with Jira and how their teams use it. Exciting stuff :) 

Intro - Welcome back to Dev Theory Podcast - A podcast about everything Web Development. - This is Episode 22. I'm Shaun Willis, here with our co-host Isaac Weber. Today we will be answering questions from our listeners and talking about how to work remotely for the companies in the US. ## Table of Contents - Boro Dev Agency, LLC - responding to our listeners    - the entrepreneur has great feature ideas fleshed out, but difficulty implementing the actual features in a web app. Should he focus his energy on building his technical chops or finding someone to build it for him.    - someone from dubai get a remote job in the US. W7 - you need to fill out a W7 and receive an I10 which is identification so taxes can be accounted for. ### Outro - (Shaun) - Thanks again for listening to Dev Theory Podcast. I'm Shaun Willis with our co-host Isaac Weber If you like this show leave us a review and share it with your friends.

Intro - Welcome back to Dev Theory Podcast - A podcast about everything Web Development. - This is Episode 21. I'm Shaun Willis, here with our co-host Isaac Weber. Today we will be talking about Tesla AI Day, Humanoid Robots, and where we see AI headed as it relates to software engineering careers ## Table of Contents - Tesla AI Day - Humanoid Robots - neuralink - AI headed as it relates to software engineering careers. ### Outro - (Shaun) - Thanks again for listening to Dev Theory Podcast. I'm Shaun Willis with our co-host Isaac Weber If you like this show leave us a review and share it with your friends. if you are a tech company interested in sponsoring this podcast, you can email us [email protected]

Table of Contents continue the discussion on Career paths finding startups that just received a new round of funding tend to always ramp up hiring efforts, so someone looking to get into the industry might be a great place to start googling and searching. They tend to hire in bulk and are sometimes willing to take entry-level developers. A Typical Career Path for a Software Engineer Below is a common career path for a software engineer. Bear in mind that each company will have its own specific roadmap and this is just an example. Tech Lead: As a tech lead, you’ll be responsible for the entire software development process. You’ll manage a large team of professionals involved in software design and development. You’ll be required to report development progress to company stakeholders and provide input into the decision-making process. Team Manager: If you have strong leadership skills, you can progress into a managerial-based role. You’ll be responsible for the well-being of the entire team and will oversee their career progression. Technical Architect: As a technical architect, you’re expected to overlook the entire architecture and technical design. You’ll be required to build processes for the team and provide technical leadership. This role will also involve looking into the scaling of support systems. Chief Technology Officer: A CTO is the head of an organization’s technological needs. They oversee R&D and employ technology to improve products and services for their clients. This is often considered the pinnacle of a software engineer's career https://www.thinkful.com/blog/software-engineer-career-path/

Table of Contents 2021 State of the Industry. - 32 Crucial Technology Industry Statistics to Know in 2021 Software Engineer's Career Pathshow to stay relevant in an ever-changing industry A Typical Career Path for a Software Engineer Below is a common career path for a software engineer. Bear in mind that each company will have its own specific roadmap and this is just an example. Junior Software Engineer: At the beginning of your career you’ll have limited experience and start in an entry-level position. As a junior software engineer, you’ll be required to develop software to meet client requirements within a specified time frame. You’ll report to your team leader, who will act as a mentor and guide you. During this period of your career, you have the opportunity to learn new skills and gain essential experience working on real-life software projects. Senior Software Engineer: After a few years, you’ll become a senior software engineer. You’ll learn new programming languages, and master the software development lifecycle. You may have the opportunity to train junior engineers or even manage a small team of your own. You’ll start to be introduced to other business elements such as project budgets and high-level company objectives. Tech Lead: As a tech lead, you’ll be responsible for the entire software development process. You’ll manage a large team of professionals involved in software design and development. You’ll be required to report development progress to company stakeholders and provide input into the decision-making process. Team Manager: If you have strong leadership skills, you can progress into a managerial-based role. You’ll be responsible for the well-being of the entire team and will oversee their career progression. Technical Architect: As a technical architect, you’re expected to overlook the entire architecture and technical design. You’ll be required to build processes for the team and provide technical leadership. This role will also involve looking into the scaling of support systems. Chief Technology Officer: A CTO is the head of an organization’s technological needs. They oversee R&D and employ technology to improve products and services for their clients. This is often considered the pinnacle of a software engineer's career