Complete Developer Podcast

“Some people may find that they have a dominant style of learning, with far less use of the other styles. Others may find that they use different styles in different circumstances. There is no right mix. Nor are your styles fixed.” ~ advanology.com 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. The episode begins with where the metaphor of learning styles originated and an overview of the different models. Then the guys delve into the most common model (VARK) discussing the best ways to learn for each style and covering some of the distractions to be avoided. Next they discuss the different settings for learning and how setting adds complexity to the concept of learning. A brief talk on learning mindsets and the ideal style and setting for each follows. Finally the episode ends with a discussion on how individual programmers can use this metaphor to their advantage. Episode Breakdown * 18:40 What Are Learning Styles? Originally for Teachers and Presenters The concept of learning styles comes from the differences in learning modalities. Individuals have a prefered modality and by addressing that modality teachers and presenters should be better able to communicate with students. Several Different Models There are several different models for understanding learning styles. Of the various models Felder and Soloman’s Index of Learning Styles and Howard Gardner’s Multiple Intelligences are the most widely recognized. The model that BJ learned in school is the VAK or VARK model. That stands for Visual, Auditory, Reading/Writing, and Kinesthetic. “Learning styles theory says that an auditory learner will learn things better when they are presented aurally. But there are many types of knowledge which are hard to grasp aurally – for example the shape of a country or how to ride a bike. Just about everyone will learn the shape of a country by seeing that shape, that is visually. Just about everyone learns how to ride a bike by doing it, that is kinaesthetically. It is the type of information that drives how we should present it – not the learning style of the learner.” ~ Olivia Mitchell * 23:45 Styles of Learning Each of these represents a different modality of learning. Individuals generally have a prefered modality or multiple prefered modalities. However depending on the situation or material some modalities are better suited for learning than others. Visual Visual learners learn by visualizing information and the relationships between different sets of data. They prefer charts and graphs or infographics and can become distracted by too much visual stimuli in their environment. Auditory Auditory learners prefer hearing and reciting information. They learn best through lectures, podcasts, or discussion groups. Environments with a lot of noise can be distracting. Tactile Kinesthetic learners take in information by movement. Activities like labs and roleplaying benefit this style. They prefer to be hands on and experimental but have more difficulty with less practical and more conceptual learning. Read/Write This is more than just a visual-tactile combination, they learn by reading and writing. They prefer to interact with text, test their understanding, and fill out handouts or take detailed notes. They will take notes when no written material is presented. * 35:47 Settings for Learning Social Social learners prefer to interact with the presenter...

As we approach the end of the year BJ and Will discuss strategies for setting goals to take back control of your life. Actively setting and reviewing goals helps to maintain focus and motivation. It gives significance to our long term improvements. The guys take a top-down approach to setting goals with analogies to programming structure. They start with lifetime goals and work down to daily to do lists to achieve those goals. The majority of the episode is spent discussing the well known S.M.A.R.T. criteria for goal setting and how it applies to programmers at work and in personal life. The episode closes with some tips on prioritizing and maintaining goals in the long term. Links * IEEE Authors * Forbes Article * Top Achievement * Mind Tools * 30, 60, 90 Day Plan * SMART Goals PDF * Your Goals Must Matter * BareTail Offline Referrences Doran, G.T. (1981). There's a S.M.A.R.T. way to write management's goals and objectives. Management Review, 7(11), 35-36.

In project management, a death march is a project where the members feel it is destined to fail, or requires a stretch of unsustainable overwork. The general feel of the project reflects that of an actual death march because the members of the project are forced to continue the project by their superiors against their better judgment.  ~Wikipedia Will and BJ discuss the troubles and tribulations of the death march. They are typically characterized by heavy turnover, burnout, and timelines that are too aggressive to actually meet. Death marches usually come about though poor management or a disconnect between developers and other departments like sales. Rapid growth may also lead to a death march. Growth of the team or growth of the company if it is a startup. It is best to avoid working for companies or projects that have death march potential. To do this ask upfront what the expectations are regarding hours, overtime, and comp time during the interview. Remember you are choosing the company as much as they are choosing you. Links IoT is Over-hyped Wikipedia Definition Urban Dictionary Portable Apps Special Note Excerpt of The Imperial March (Darth Vader's Theme) by John Williams used in the discussion about the Episode VII was taken from The Music Of Star Wars: 30th Anniversary Collector's Edition .

Coming out of a holiday week the guys full on turkey and dressing discuss the impact that distractions have on developers and productivity as well as ways for both developers and management to minimize the amount to distractions faced by developers in a day. They begin looking at the effect of distractions on other professions and explain what a distraction means to a developer. Next Will and BJ talk about the effects of distractions on developers from the productivity as well as the psychological aspect. They end the episode discussing ways that developers and then management can work to minimize distractions. Links Hipster Ipsum IoT List Joel on Software Wireshark Editor's Note: Apologies for this being published a little later than usual. We ran into some technical difficulties with Audacity.

This being a holiday week the guys chose to air a special episode on substance abuse. This was originally part of the Mental Health episode but BJ went "Full Med Student" on the notes and produced a few shows. As many of us gather with our families this week we can see issues with substance abuse come out more than at other times. Part of this is from not having the responsibility of getting up and going to work and part from the stress that usually comes with travel and large gatherings. In this episode Will and BJ discuss some of the signs and symptoms of substance abuse as well as what to do if you suspect you or someone you know may need help. They begin by defining Substance Abuse as an over-indulgence in or dependence on an addictive substance, especially alcohol or drugs. Next Will reviews physical, behavioral, and psychological warning signs of a substance abuse disorder. They guys then delve into the medical signs and symptoms of substance abuse and how they may appear different within the development community. Next they take a look at specific workplace behaviors and how drug abuse can effect the workplace, coworkers, and job retention. In the end they provide information on where to look for help if you or someone you know may be suffering from a substance abuse disorder. Links Oracle Java Definition Learn Java Online National Council on Alcoholism and Drug Dependence Alcoholics Anonymous Narcotics Anonymous Al-Anon Employee Assistance Programs (EAP) Markdown Pad Daring Fireball

This week the guys discuss ways to find motivation and self motivate in times when developers are down and discouraged. They begin by looking at Frederick Hersberg's study on the two factors that influence employee satisifaction: hygiene and motivation. Which leads them to talking about how different companies motivate their employees from by providing autonomy, mastery and purpose to developers. In the bulk of the episode they discuss different strategies to find your own motivation starting with how developers respond to expectations. Then they look at intrinsic and extrinsic factors involved in motivating ourselves. BJ gives a preview of the goal setting episode and even writes some code in his outline. The guys wrap up the episode talking about how to create and sustain self motivation. Links IoT T.A.R.D.I.S. Nine Things Developers Want More Than Money Autonomy, Mastery, and Purpose How Successful People Motivate Themselves Be Self Motivated As A Software Developer Form Successful Habits Find What Motivates You WinMerge

In this the tenth episode Will and BJ discuss ten reasons a programmer or hobbyist might not want to go into full time development. It is best to know early on in your career or training if this is the life for you. The guys are not out to discourage anyone from going into the field but want those entering to be able to make an informed decision. They address some of the challenges that face developers as well as aspects of the working environment that make a career as a developer unique. The episode concludes with a discussion on the matter of programming as a job or programming as a craft. To be successful a developer needs to be a craftsman. Links Learn C++ Psychology of Computer Programming Six Signs You're Not Meant To Be A Programmer Notepad++

But They Are NEVER Wrong! In Episode 9 Will and BJ discuss a common misconception in the workplace. The idea that the customer is always right. They begin by looking at why this attitude is hurtful to employees, other customers, and management explaining why the customer is not always right. Then the guys delve into why the customer is never wrong and how it is the job of employees to guide the customer. Next they take a look at who is the customer from direct customer access in freelance work to internal customers within the same company. The show ends with a detailed look at each of these customers and how developers can best serve them by realizing that they may not always be right but should never be wrong. Links StartX Fails on Raspbian Customer Service No, The Customer is Not Always Right Entrepreneur Why Developers Always Say No Development vs Production Vampires and Werewolves Managing Developers Why Programmers Think They Know Best f.lux

This week BJ keeps his promise and brings an episode on understanding the roles and relationship of sales to development. The guys begin with a discussion on the importance of sales and what they do for the company. Next BJ takes us through an abbreviated Sales School 101. They then talk about differences in pay structure between development and sales with emphasis on why pay better matches ability with sales. The episode finishes with a discussion on how this effects programmers and how both sales and development teams can interact to better their work environments. Links Azure IoT Suites Developers vs Sales Salespeople and Programmers Seven Steps of the Sales Process Sales Process Steps How to Support Sales Why Programmers Get Paid Less Browsershots  

In this episode the guys discuss beliefs that developers hold (or act as if they hold) that simply are not true. They delve into commonly held yet erroneous beliefs that developers tend to have about work, employers, other departments, and more. While it is not an exhaustive list they cover everything from interacting with others to interacting with databases, to changing specs mid project, and misunderstandings about how business works.  These are the sort of critical mis-communications and non-optimal behaviors that distinguish a less experienced and less professional developer from those that have played the game a while and gotten some life experience. Being aware of these will help improve your employer's (and fellow coworker's) perception of you, as well as steer you away from problems that can cause you grief later. Links Learn CPP C Language History How Stuff Works Learn C The Hard Way Unhedged Call Option Palette for Chrome

In this episode of The Complete Developer Podcast, the guys discuss strategies for getting through boring meetings, which are the bane of software developers everywhere. Packed into this episode are a number of strategies you can use to turn boring, time-wasting meetings into something that helps your career, rather than something that simply wastes your productive time. Links Code Newbies Morpho Source Draw.io Breast Cancer 5K Editor's Note: We had some issues with our recording for this episode. Please bare with us as we are learning to use the recording and editing equipment.

Finishing out our series on Health Concerns for Developers we delve into the realm of financial health. In this episode, we discuss a number of issues that can derail software developers from effectively managing their finances. We start out with a breakdown of some pretty alarming statistics regarding average household debt levels in America and how those are broken down across a number of categories. Next, we discuss some ways that developers can deal with their financial problems. Without getting too technical, we suggest some strategies to being digging out from under debt, including ways to reduce expenses, reduce outstanding debt, and increasing income. Finally, we point a couple of things that may help you get through it all successfully. LINKS 11 IoT Programming Languages Programming Throwdown I Will Teach You to be Rich The State of American Credit Card Debt Nerd Wallet Motley Fool CNBC Time Nimble Text