Within programming there are many problems that can occur throughout a coding process.Various solutions exist to different problems and sometimes a design pattern has beenestablished for a specific problem. Design patterns are established solutions to a commonproblem developers can face while coding. To choose one of the design patterns that fits theproblem can be challenging depending on the developer.This study focused on collecting data on inexperienced developers' experience in choosing adesign pattern. This study has limited itself to four different approaches to choose a designpattern. Selected approaches are: Scan intent section, study how patterns interrelate, Examinecause of redesign and Killer”Killer examples'' for design patterns. The approaches have beenselected from other sources that have described them in detail. These chosen approaches havebeen used to test five inexperienced developers and collect data on their experience withchoosing a design pattern. The results of the chosen approaches have collected data with thehelp of a usability testing method and semi-structured interview. The data have been analyzedwith the help of a thematic analysis. The thematic analysis resulted in five themes: Info notfound, Difficulties in understanding design patterns, Uncertainties when selecting designpatterns, Effective approaches and Familiar with approaches. The Findings from these themesand their codes have revealed multiple issues when selecting a design pattern. Findings alsoestablished what participants thought were effective approaches according to their ownexperience working with these approaches.

Test-driven development is a software development practice that prompts developers to write tests before writing source code. Studies report varied results on the effects that test-driven development has on the development process, and how this practice compares to other development practices, such as more traditional test-last development methodologies. There also seems like there has not been a discussion around the possible problems that a developer could encounter when adopting this technique, something that seems relevant to making accurate assumptions on the usability of the practice. A literature review was conducted, where the subject of test-driven development is examined with a focus on how inexperienced programmers interact with the practice and what effect it has on the product, in terms of external quality, productivity, number of test written and test coverage. The results suggest that there are no significant differences in external quality and productivity between TDD and TLD. The results also suggest that divide and conquer and refactoring are skills that ease the process of adopting the test-driven development practice.