Historically developers have been specialist. In web development you were either front end or back end. You build your portion of an app and didn't worry about the other areas. The idea behind being a T shaped developer is to have a broad base of knowledge and then dive deep into a few areas.

Non-technical characteristics are valuable to being a good developer. A lot of developers seem to think that the job is only about technical skills, however not all problems we face are in the code.

A string is a data type that stores text. There's more complication to strings than you would think, which is the reason for this episode.

Three tier architecture separates the functional process logic from data storage and user interface. These are developed and maintained independently on separate platforms.

Some companies have bad environments for developers and some have developer environments that may work for some people but not others. As an interviewee you need to be paying attention during an interview for signs that the business may not be the right place for you. This also shows alertness in the interview.

This week we celebrate one year of producing Complete Developer Podcast. It is exciting as we hit our goal for the year a month early. In this week's episode the guys talk about the apprenticeship program that Will put together to get BJ up to speed as a developer.

In response to the trends in project management for software development from the 1970's and 1980's several methodologies were developed and became popular in the 1990's. SCRUM is a framework for implementing project management in Agile Software Development.

Code katas help you to build solid practices in a controlled environment. The idea here is to create a situation with a known problem space and use it to safely practice the same thing over and over again until the technique is fluid, solid, and relaxed.

​Time is the resource we are least able to get more of. It's a far more complicated topic than most examinations of it will lead you to believe. This episode focusses on things that are obvious but still burn through your time. Each alone is not much but when combined or allowed to snowball they contribute heavily to poor time management.

Object Oriented Programming has four major principles: Abstraction - using a focused representation of an actual item, Encapsulation - hiding the internals of an object, Inheritance - reusing code from an existing object, and Polymorphism - one name, many forms.