Complete Developer Podcast

You need to keep learning to continue to grow. Old technologies, frameworks, and languages will change and grow to meet new needs and add new features. New technologies are constantly being built and put out for people to use. You don't have to be up-to-date on the bleeding edge tech but should keep up with the feature set in what you are using.

Dani Heileman is a marketing strategist, designer and front end developer who's working as the Marketing Director for Music City Code.

A lot of us would like to do more with our lives, but find ourselves getting blocked by our own laziness, lack of motivation, or simply not being sure which thing to do first. While these skills apply to your career as a software developer, they are also broadly applicable across your entire life.

Getting started can be a little intimidating, so it's important to go over the basic requirements to get started learning how to code through experience.

The idea of code smells is they are patterns or anti-patterns that are easy to identify and show the code needs to be reviewed in that area when refactoring your code. Research by Tufano et al. found that there is empirical evidence for the consequences of "technical debt" but only anecdotal evidence as to how, when, or why this occurs.

The idea of code smells is they are patterns or anti-patterns that are easy to identify and show the code needs to be reviewed in that area when refactoring your code. Depending on who you ask or where you look there are lots of different code smells from general smells, to paradigm specific, to even language and framework specific smells. Code smells can be categorized different ways. Here they are grouped by what they do or the problems they cause.

This week Will and BJ continue their A Developer's Journey series where the guys talk with different developers about their journey into and within software development. The episodes in this series come out periodically and each one focuses on a different developer's journey.

Dr. Tuckman states that team growth and dynamics are influenced by the setting in which the group is working, the area where the group behavior falls at any point, and the where the group is in the sequence. He originally wrote about four phases of group development: Forming, Storming, Norming, and Performing. In 1977 he added a fifth stage called Adjourning. Dr. Tuckman states that they are all necessary for a team to grow and work together.

This week Will and BJ discuss salary negotiation with author Josh Doody. In the episode they talk about some of the common questions developers have about negotiating as well as covering some mistakes that we all make when negotiating for a higher salary.

In this special episode Will and BJ invited old time strongman Iron Tamer David Whitley to discuss how to overcome mental barriers that keep you from doing difficult things. The episode covers how David overcomes mental barriers when performing feats of strength and how that applies to overcoming difficulties as a programmer.

In general, it occurs when the inevitable plateau in learning happens. Generally it's a crippling feeling like you are being a fraud and in imminent danger of being found out. Beyond anything else you must understand, you need to realize that it's part of the journey.

Jason Belcher is an aspiring software developer and has also done a lot to help improve the audio quality on this podcast. Will and BJ first met him down in Atlanta at Code Newbies and they've kept in touch nearly every day since then. Jason provided the intro music for IoTease which he remixed from a guitar track of his father. He became interested in coding through music and mixing audio tracks.

Boolean algebra is a set of rules to describe a problem whose outcome will either be true or false. They were formulated by an English mathematician named George Boole. He's the namesake for the rules and for the boolean type in statically typed languages.

Participating in your community benefits both you and the community. There are many different levels of participation from just showing up to planning and even leading and organizing events. Finally there are many ways in which to get involved. Leading a group isn't for everyone. However anyone can participate and enjoy the rewards of getting out and helping themselves and others.

Programming errors are one thing, but there are other types of errors that can be just as damaging to end user experiences. These errors are easy to miss in a software development shop, precisely because of the biases that are present on the typical development team.