Podcast Episodes

Creational Design Patterns A constructor is a function that is used to build an object and it is part of that objects definition. Calling a constructor causes cohesion between the code and the object being instantiated. Making changes in the objects can cause problems when calling the constructor. Strongly typed languages tend to catch these errors at compile time however dynamic languages such as JavaScript may not catch the errors until runtime or later. The creational design patterns are ways to break this cohesion

The Value in Not Working Down time can mean time spent not coding at work for various reasons. For this episode though the guys use down time to refer to total down time, not at work and not working at home. Time away from the computer screen.

How Cognitive Biases Affect Developers https://media.blubrry.com/completedeveloperpodcast/p/content.blubrry.com/completedeveloperpodcast/CDP-Episode0035-How_Cognitive_Biases_Affect_Developers.mp3Podcast: Play in new window | Download (53.2MB) | EmbedSubscribe: Apple Podcasts | Android | Email | Google Podcasts | Spotify | RSS | More “Critical thinking is an essential skill in our age of constant information (and misinformation), but our own subconscious biases don’t help matters much when it comes to sorting out truth ...

An Introduction to Design Patterns Design patterns are a way of thinking about abstract concepts in Object-Oriented Programming. In the original book 23 patterns were listed divided into three sets of patterns: Creational, Structural, and Behavioral. Will and BJ discuss both the benefits and some of the critiques of using design patterns when designing and developing code.

Learning Styles Learning styles are a guide to help programmers understand how they learn and how to optimize their ability to learn new materials and keep up on trends in the industry. Will has found that he is primarily a kinesthetic learner whereas BJ is primarily a visual learner. However both enjoy listening to podcasts when driving because the content of the shows and the situation of driving lends itself to auditory learning.

Writing Effective Documentation Many open-source docs are lacking in content. When looking for details on the API all the documentation contains is how to install. Whereas others like Microsoft's MSDN are verbose and troublesome to navigate. This week the guys discuss the different types of documentation and what should go into writing each. One of the best areas for a junior developer to gain experience is writing documentation as according to Will many senior developers are lacking in the skill.

Lessons From The Trickster Tricksters are found in the mythology and stories of almost every culture. From Coyote to Prometheus to Loki, today is April 1st or April Fools Day a day we as a culture celebrate tricksters and pranksters. In cultural stories, or myths tricksters play tricks to teach or create changes that leads to growth. In Norse mythology which has been in the movies lately Thor would not have his hammer without Loki, nor Asgard it's walls. This episode will be a little different from most as the guys discuss nine lessons a trickster would teach programmers.

Web Development Skills to Get the Job Finishing the two part episode on skills web developers need to know the guys tackle the skills needed to land a job along with advanced skills to set yourself apart. The episode closes with a list of honorable mentions that do not directly apply to web development but are interpersonal skills useful to a career in development.

Skills Every Web Developer Needs https://media.blubrry.com/completedeveloperpodcast/p/content.blubrry.com/completedeveloperpodcast/CDP-Episode0029-Skills_Every_Web_Developer_Needs.mp3Podcast: Play in new window | Download (51.8MB) | EmbedSubscribe: Apple Podcasts | Android | Email | Google Podcasts | Spotify | RSS | More The question was asked on Quora: What are the five essential skills every web developer should have? There were 91 different answers to this question, though most could be broken ...

How to Identify Technical Debt The term technical debt can be misleading and confusing. It is generally referred to as a metaphor referencing the consequences of system design or software architecture in a codebase. Technical debt can be difficult to identify directly so developers need to use clues that can be broken down into social cues, code cues, and testing/deployment cues.