Coding Dojo: Adding Tests to Legacy Code (2014)
2 likes1,085 views
Peter Kofler led a coding dojo on adding tests to legacy code. The dojo focused on understanding legacy code, breaking dependencies, extracting pure functions and classes, and refactoring code to be testable. Participants worked on adding tests to the "Ugly Trivia" legacy codebase, an implementation of the game Trivial Pursuit, by extracting pure functions and classes and writing tests for the extracted code.
1 of 16
Downloaded 12 times
Ad
Recommended
Designing Test Cases for the Gilded Rose Kata (2013)
Designing Test Cases for the Gilded Rose Kata (2013)Peter Kofler This document outlines Peter Kofler's presentation on designing test cases for the Gilded Rose Kata. The presentation introduces Kofler and the coding dojo mindset of learning in a safe collaborative space. It describes the dojo structure and focuses on test-driven development skills like designing test cases. Attendees are instructed to get the Gilded Rose code from a GitHub repository, read the requirements, choose a testing framework, create tests to cover all cases, and experiment with different test styles.
Software Craftsmanship Journeyman Tour (2013)
Software Craftsmanship Journeyman Tour (2013)Peter Kofler Peter Kofler is a software developer and "code cop" who is passionate about code quality. He has a Ph.D in applied mathematics and 14 years of industry experience. Kofler is embarking on a "Journeyman Tour" to pair program with developers, teach skills like test-driven development and clean code, and learn new techniques and technologies from others. During the tour, he will pair with developers for a few days, teaching and learning from each other, and blog about his experiences to help others improve their craft. Kofler invites attendees to learn from his teachings on software craftsmanship.
The Brutal Refactoring Game (2013)
The Brutal Refactoring Game (2013)Peter Kofler This document describes The Brutal Refactoring Game workshop conducted by Peter Kofler. The workshop aims to improve code quality through pair programming and refactoring code to remove code smells. It will involve participants coding a Tic-Tac-Toe game in pairs, with Kofler acting as a "benevolent dictator" stopping work whenever a code smell is detected until it is refactored away. The session concludes with a discussion of lessons learned.
Clean Readable Specifications (ETC 2016)
Clean Readable Specifications (ETC 2016)Peter Kofler Peter Kofler, a professional software developer and mentor, focuses on mentoring development teams to create clean, readable, and expressive executable specifications. He emphasizes the importance of quality in programming through practices such as pair programming, coding dojos, and continuous improvement. The document also discusses an inventory system for managing items with specific rules for quality degradation, highlighting special cases like aged brie and backstage passes.
Refactoring the Tennis Kata (2013)
Refactoring the Tennis Kata (2013)Peter Kofler This document outlines Peter Kofler's presentation on refactoring the Tennis Kata coding exercise. The presentation covers the coding dojo mindset of collaboratively learning by slowing down and focusing on quality. It describes the dojo structure, Test Driven Development skills like designing clean code and refactoring safely. It also provides requirements for the Tennis Kata refactoring exercise - to focus on cleanup and refactoring in small steps while running tests often.
Refactoring the Tennis Kata v2 (2016)
Refactoring the Tennis Kata v2 (2016)Peter Kofler The document outlines the principles and practices of conducting a coding dojo focused on refactoring a tennis scoring program. Peter Kofler emphasizes the importance of creating a collaborative and safe learning environment, identifying code smells, and employing merciless refactoring techniques. The document also advises using automated refactoring tools and encourages participants to focus on quality and continuous improvement throughout the process.
Brutal Coding Constraints (ITAKE 2017)
Brutal Coding Constraints (ITAKE 2017)Peter Kofler This document discusses brutal coding constraints that can be used during coding dojos or retreats to improve coding skills. It proposes constraints like removing conditionals, loops, and mutable data to solve problems like implementing tic-tac-toe. Participants are asked to implement a two-player and AI version of tic-tac-toe under these constraints. The goal is to learn through challenges and collaboratively reflect on the experience.
Coding Dojo: Functional Calisthenics (2016)
Coding Dojo: Functional Calisthenics (2016)Peter Kofler Peter Kofler presented at a coding dojo on functional calisthenics. He is a software developer and code mentor who helps teams improve code quality through pair programming, workshops, and coding dojos. The dojo assignment was to implement a social networking application like Twitter using a functional programming language while following constraints like no mutable state, expressions over statements, and maximum abstraction. The goal was to learn through challenges rather than focus on completion.
Idiomatic R for Rosetta Code (2013)
Idiomatic R for Rosetta Code (2013)Peter Kofler The document discusses Rosetta Code, an online collection of programming tasks solved in many different languages, and encourages attendees to contribute R solutions to unsolved tasks or improve existing solutions. It also reviews some existing R code on Rosetta Code to discuss idiomatic R style and seeks help with solving the task of finding Pythagorean triples with a given diameter in a functional way.
Designing Test Cases for the Gilded Rose Kata v3 (2016)
Designing Test Cases for the Gilded Rose Kata v3 (2016)Peter Kofler The document outlines a coding dojo facilitated by Peter Kofler, emphasizing the importance of creating clean, readable, and expressive unit tests for the Gilded Rose kata. It describes the structure of the dojo, the existing inventory system, and the special item rules within the kata, while highlighting objectives like designing 'perfect' unit tests and focusing on quality over speed. Participants are encouraged to engage with requirements, derive necessary test cases, and reflect on their learning experiences.
Coding Dojo - Refactoring Tennis Kata
Coding Dojo - Refactoring Tennis KataAlin Pandichi This document outlines an exercise for practicing refactoring code through pair programming. Developers pair up to refactor a tennis scoring program, taking turns coding on one shared computer every 7 minutes. The goals are to learn refactoring techniques, improve code design through applying principles like removing duplication and revealing intention, and perform small, tested changes to restructure the code without altering its functionality.
TDD as if You Meant It (2013)
TDD as if You Meant It (2013)Peter Kofler The document summarizes Peter Kofler's presentation on Test Driven Development (TDD) at Agile Testing Days 2013. It discusses the mindset of TDD coding dojos, the structure of Kofler's dojo sessions, skills practiced in TDD like designing test cases and refactoring, rules for "TDD as if you meant it," and an assignment to implement tic-tac-toe using TDD. The goal is to focus on doing TDD perfectly rather than just getting the implementation done.
Coding Dojo Object Calisthenics (2016)
Coding Dojo Object Calisthenics (2016)Peter Kofler Peter Kofler is a software developer and code mentor who helps development teams improve code quality through mentoring techniques like pair programming and coding dojos. The document summarizes Object-Oriented Programming concepts like abstraction, encapsulation, polymorphism, and inheritance. It also describes "Object Calisthenics" rules for writing high-quality object-oriented code, such as wrapping primitives, short methods, and avoiding getters/setters. The agenda involves a discussion of OOP concepts and a coding exercise on implementing LCD number display following the Object Calisthenics rules.
Coding Dojo: Data Munging (2016)
Coding Dojo: Data Munging (2016)Peter Kofler Peter Kofler presents a coding dojo focused on data munging, emphasizing quality, collaboration, and continuous improvement through pair programming and test-driven development. Participants engage in various programming assignments to analyze weather and soccer data while adhering to constraints like avoiding control structures. The dojo fosters a learning environment, encouraging reflection on experiences and surprises during the sessions.
Deliberate Practice (Agile Slovenia 2015)
Deliberate Practice (Agile Slovenia 2015)Peter Kofler The document discusses deliberate practice as a way for software professionals to continuously improve. It proposes that traditional training methods are not enough and advocates for code katas, coding dojos, and code retreats where developers can practice specific skills in a low-pressure environment. These practices are presented as a way to overcome weaknesses in software engineering education and on-the-job training by providing structured, repetitive practice opportunities to develop expertise.
Mob Programming (2016)
Mob Programming (2016)Peter Kofler This document discusses mob programming, an agile development technique where the entire team works together on the same task using one computer. It describes mob roles like driver, navigator, and facilitator. The driver focuses on typing code while listening to the navigator, who formulates ideas for the team. Roles rotate every few minutes. Guidelines are provided for mitigating emotions and ensuring visibility when mobbing with many developers. Mob programming aims to improve collaboration, knowledge sharing, and code quality.
JUnit Boot Camp (GeeCON 2016)
JUnit Boot Camp (GeeCON 2016)Peter Kofler This document outlines an agenda for a unit testing boot camp with JUnit. The agenda includes introductions, an overview of JUnit, a coding exercise to practice writing unit tests with JUnit assertions, a lunch break, learning about best practices for writing clean unit tests, another coding exercise, and a retrospective. The document provides background on the instructor and describes how attendees can get the most out of the boot camp by slowing down, getting out of their comfort zone, and pairing with others.
Coding Dojo: Asynchronous Clock-In (2016)
Coding Dojo: Asynchronous Clock-In (2016)Peter Kofler Peter Kofler presented an asynchronous coding dojo on building a clock-in application. The goal was to build a client interface that allows punching in and out with optional GPS data, with asynchronous calls to a backend server. Kofler emphasized focusing on doing the coding challenge correctly rather than just getting it done. Participants were instructed to work in pairs, add testing, and start with a simple asynchronous backend mock to practice asynchronous language features like promises.
Code Retreat Graz, Austria 2013
Code Retreat Graz, Austria 2013Peter Kofler Peter Kofler organized a Code Retreat in Graz to teach attendees about code quality. The retreat consisted of coding sessions focused on Conway's Game of Life where participants practiced pairing, experimenting, and improving code quality based on principles like simplicity, readability, and minimizing duplication. The goal was to help developers learn through repetition rather than focusing on completion.
Extract Method Refactoring Workshop (2016)
Extract Method Refactoring Workshop (2016)Peter Kofler This document summarizes a presentation on refactoring and code quality given by Peter Kofler. The presentation covers topics such as code smells, refactoring techniques like extract method, using tools like PHPStorm for refactoring, and practicing refactoring through coding dojos and katas. The goal is to help developers improve code quality, design and productivity through iterative refactoring.
Coding Dojo: Baby Steps Push Challenge (2021)
Coding Dojo: Baby Steps Push Challenge (2021)Peter Kofler The document discusses a push challenge led by Peter Kofler, emphasizing the importance of producing high-quality code through small incremental changes. It highlights various programming practices like test-driven development, refactoring, and collaborative learning in coding dojos. The focus is on continuous improvement and the benefits of making frequent, small commits to enhance productivity and learning within development teams.
Coding Dojo: Naming with Dices (2021)
Coding Dojo: Naming with Dices (2021)Peter Kofler The document presents guidelines and principles for conducting coding dojos, focusing on pair programming, test-driven development (TDD), and a collaborative learning environment. It emphasizes the importance of slowing down to improve code quality and includes a tic-tac-toe programming assignment with specific constraints. The aim is to foster continuous improvement and professionalism among software developers.
Coding Dojo: Bank OCR Outside-In (2015)
Coding Dojo: Bank OCR Outside-In (2015)Peter Kofler Peter Kofler led a coding dojo session on outside-in test-driven development (TDD) for a bank optical character recognition (OCR) assignment. The assignment asked participants to write a program to parse account numbers from an OCR file containing entries with account numbers represented using pipes and underscores. Kofler emphasized learning outside one's work environment, focusing on quality over speed, and improving through collaboration and reflection.
Coding Dojo: Mars Rover (2014)
Coding Dojo: Mars Rover (2014)Peter Kofler The document describes a coding dojo event where participants will work in pairs using test-driven development and pair programming to solve the problem of programming a Mars rover to navigate a grid based on input commands. The rover must wrap around the grid, detect obstacles, and report its position and any obstacles encountered. Participants will work through introductions, coding exercises, and retrospectives while focusing on best practices like improving existing code rather than deleting it.
Using Automated Code Reviews to Achieve Continuous Quality (ASQF Agile Night ...
Using Automated Code Reviews to Achieve Continuous Quality (ASQF Agile Night ...Peter Kofler Peter Kofler discusses the importance of automated code reviews for achieving continuous quality in software development during his presentation at the ASQF Agile Night in Austria, October 2018. He emphasizes the necessity of ensuring both external and internal quality through practices like static code analysis and dependency analysis, highlighting the benefits and challenges of implementing such measures. Kofler advises integrating code analysis into the build pipeline to identify and address code violations promptly.
Outside-in Test Driven Development - the London School of TDD
Outside-in Test Driven Development - the London School of TDDPeter Kofler The document discusses Outside-In Test-Driven Development (TDD) presented by Peter Kofler at the Software Quality Days 2019. It compares classic Inside-Out TDD to the London School approach, focusing on user interactions and mocking dependencies. Key aspects include a coding exercise on bank OCR, various TDD principles, and the importance of continuous learning and practice in developing quality software.
Code Retreat Venice (2016)
Code Retreat Venice (2016)Peter Kofler This document outlines Peter Kofler's philosophy and approach to mentoring development teams and improving code quality. He advocates for practices like pair programming, coding workshops, and coding dojos where developers practice coding katas in teams to improve skills like test-driven development, clean code, and design. The document provides an example agenda for a coderetreat where developers pair up to practice test-driving solutions for Conway's Game of Life using different programming languages and techniques like writing code without using if statements. The goal is for developers to learn through deliberate practice in a safe collaborative environment outside of work.
Deliberate Practice, New Learning Styles (2015)
Deliberate Practice, New Learning Styles (2015)Peter Kofler Peter Kofler discusses the software crisis, highlighting the increasing complexity and legacy issues in software development due to advancements in technology. He advocates for deliberate practice through methods like coding dojos and code katas to enhance the skills of software professionals. Kofler emphasizes the importance of continuous improvement, mentorship, and collaborative learning to produce high-quality software.
Coding Dojo: Fun with Tic-Tac-Toe (2014)
Coding Dojo: Fun with Tic-Tac-Toe (2014)Peter Kofler This document summarizes a coding dojo event focused on tic-tac-toe. The event introduces pair programming and test-driven development techniques. Attendees work in pairs to implement tic-tac-toe under constraints, such as writing the worst code possible initially and then refactoring without talking. The goal is to learn through challenges and reflection on how to write better code.
Coding Dojo: Baby Steps (2014)
Coding Dojo: Baby Steps (2014)Peter Kofler The document discusses an approach to test-driven development called "baby steps" where developers write one test and the minimum code to pass that test within a 2 minute timer. They then refactor within the next timer period before repeating the process. It recommends practicing this approach to build TDD skills when developing a tic-tac-toe game.
More Related Content
What's hot (20)
Idiomatic R for Rosetta Code (2013)
Idiomatic R for Rosetta Code (2013)Peter Kofler The document discusses Rosetta Code, an online collection of programming tasks solved in many different languages, and encourages attendees to contribute R solutions to unsolved tasks or improve existing solutions. It also reviews some existing R code on Rosetta Code to discuss idiomatic R style and seeks help with solving the task of finding Pythagorean triples with a given diameter in a functional way.
Designing Test Cases for the Gilded Rose Kata v3 (2016)
Designing Test Cases for the Gilded Rose Kata v3 (2016)Peter Kofler The document outlines a coding dojo facilitated by Peter Kofler, emphasizing the importance of creating clean, readable, and expressive unit tests for the Gilded Rose kata. It describes the structure of the dojo, the existing inventory system, and the special item rules within the kata, while highlighting objectives like designing 'perfect' unit tests and focusing on quality over speed. Participants are encouraged to engage with requirements, derive necessary test cases, and reflect on their learning experiences.
Coding Dojo - Refactoring Tennis Kata
Coding Dojo - Refactoring Tennis KataAlin Pandichi This document outlines an exercise for practicing refactoring code through pair programming. Developers pair up to refactor a tennis scoring program, taking turns coding on one shared computer every 7 minutes. The goals are to learn refactoring techniques, improve code design through applying principles like removing duplication and revealing intention, and perform small, tested changes to restructure the code without altering its functionality.
TDD as if You Meant It (2013)
TDD as if You Meant It (2013)Peter Kofler The document summarizes Peter Kofler's presentation on Test Driven Development (TDD) at Agile Testing Days 2013. It discusses the mindset of TDD coding dojos, the structure of Kofler's dojo sessions, skills practiced in TDD like designing test cases and refactoring, rules for "TDD as if you meant it," and an assignment to implement tic-tac-toe using TDD. The goal is to focus on doing TDD perfectly rather than just getting the implementation done.
Coding Dojo Object Calisthenics (2016)
Coding Dojo Object Calisthenics (2016)Peter Kofler Peter Kofler is a software developer and code mentor who helps development teams improve code quality through mentoring techniques like pair programming and coding dojos. The document summarizes Object-Oriented Programming concepts like abstraction, encapsulation, polymorphism, and inheritance. It also describes "Object Calisthenics" rules for writing high-quality object-oriented code, such as wrapping primitives, short methods, and avoiding getters/setters. The agenda involves a discussion of OOP concepts and a coding exercise on implementing LCD number display following the Object Calisthenics rules.
Coding Dojo: Data Munging (2016)
Coding Dojo: Data Munging (2016)Peter Kofler Peter Kofler presents a coding dojo focused on data munging, emphasizing quality, collaboration, and continuous improvement through pair programming and test-driven development. Participants engage in various programming assignments to analyze weather and soccer data while adhering to constraints like avoiding control structures. The dojo fosters a learning environment, encouraging reflection on experiences and surprises during the sessions.
Deliberate Practice (Agile Slovenia 2015)
Deliberate Practice (Agile Slovenia 2015)Peter Kofler The document discusses deliberate practice as a way for software professionals to continuously improve. It proposes that traditional training methods are not enough and advocates for code katas, coding dojos, and code retreats where developers can practice specific skills in a low-pressure environment. These practices are presented as a way to overcome weaknesses in software engineering education and on-the-job training by providing structured, repetitive practice opportunities to develop expertise.
Mob Programming (2016)
Mob Programming (2016)Peter Kofler This document discusses mob programming, an agile development technique where the entire team works together on the same task using one computer. It describes mob roles like driver, navigator, and facilitator. The driver focuses on typing code while listening to the navigator, who formulates ideas for the team. Roles rotate every few minutes. Guidelines are provided for mitigating emotions and ensuring visibility when mobbing with many developers. Mob programming aims to improve collaboration, knowledge sharing, and code quality.
JUnit Boot Camp (GeeCON 2016)
JUnit Boot Camp (GeeCON 2016)Peter Kofler This document outlines an agenda for a unit testing boot camp with JUnit. The agenda includes introductions, an overview of JUnit, a coding exercise to practice writing unit tests with JUnit assertions, a lunch break, learning about best practices for writing clean unit tests, another coding exercise, and a retrospective. The document provides background on the instructor and describes how attendees can get the most out of the boot camp by slowing down, getting out of their comfort zone, and pairing with others.
Coding Dojo: Asynchronous Clock-In (2016)
Coding Dojo: Asynchronous Clock-In (2016)Peter Kofler Peter Kofler presented an asynchronous coding dojo on building a clock-in application. The goal was to build a client interface that allows punching in and out with optional GPS data, with asynchronous calls to a backend server. Kofler emphasized focusing on doing the coding challenge correctly rather than just getting it done. Participants were instructed to work in pairs, add testing, and start with a simple asynchronous backend mock to practice asynchronous language features like promises.
Code Retreat Graz, Austria 2013
Code Retreat Graz, Austria 2013Peter Kofler Peter Kofler organized a Code Retreat in Graz to teach attendees about code quality. The retreat consisted of coding sessions focused on Conway's Game of Life where participants practiced pairing, experimenting, and improving code quality based on principles like simplicity, readability, and minimizing duplication. The goal was to help developers learn through repetition rather than focusing on completion.
Extract Method Refactoring Workshop (2016)
Extract Method Refactoring Workshop (2016)Peter Kofler This document summarizes a presentation on refactoring and code quality given by Peter Kofler. The presentation covers topics such as code smells, refactoring techniques like extract method, using tools like PHPStorm for refactoring, and practicing refactoring through coding dojos and katas. The goal is to help developers improve code quality, design and productivity through iterative refactoring.
Coding Dojo: Baby Steps Push Challenge (2021)
Coding Dojo: Baby Steps Push Challenge (2021)Peter Kofler The document discusses a push challenge led by Peter Kofler, emphasizing the importance of producing high-quality code through small incremental changes. It highlights various programming practices like test-driven development, refactoring, and collaborative learning in coding dojos. The focus is on continuous improvement and the benefits of making frequent, small commits to enhance productivity and learning within development teams.
Coding Dojo: Naming with Dices (2021)
Coding Dojo: Naming with Dices (2021)Peter Kofler The document presents guidelines and principles for conducting coding dojos, focusing on pair programming, test-driven development (TDD), and a collaborative learning environment. It emphasizes the importance of slowing down to improve code quality and includes a tic-tac-toe programming assignment with specific constraints. The aim is to foster continuous improvement and professionalism among software developers.
Coding Dojo: Bank OCR Outside-In (2015)
Coding Dojo: Bank OCR Outside-In (2015)Peter Kofler Peter Kofler led a coding dojo session on outside-in test-driven development (TDD) for a bank optical character recognition (OCR) assignment. The assignment asked participants to write a program to parse account numbers from an OCR file containing entries with account numbers represented using pipes and underscores. Kofler emphasized learning outside one's work environment, focusing on quality over speed, and improving through collaboration and reflection.
Coding Dojo: Mars Rover (2014)
Coding Dojo: Mars Rover (2014)Peter Kofler The document describes a coding dojo event where participants will work in pairs using test-driven development and pair programming to solve the problem of programming a Mars rover to navigate a grid based on input commands. The rover must wrap around the grid, detect obstacles, and report its position and any obstacles encountered. Participants will work through introductions, coding exercises, and retrospectives while focusing on best practices like improving existing code rather than deleting it.
Using Automated Code Reviews to Achieve Continuous Quality (ASQF Agile Night ...
Using Automated Code Reviews to Achieve Continuous Quality (ASQF Agile Night ...Peter Kofler Peter Kofler discusses the importance of automated code reviews for achieving continuous quality in software development during his presentation at the ASQF Agile Night in Austria, October 2018. He emphasizes the necessity of ensuring both external and internal quality through practices like static code analysis and dependency analysis, highlighting the benefits and challenges of implementing such measures. Kofler advises integrating code analysis into the build pipeline to identify and address code violations promptly.
Outside-in Test Driven Development - the London School of TDD
Outside-in Test Driven Development - the London School of TDDPeter Kofler The document discusses Outside-In Test-Driven Development (TDD) presented by Peter Kofler at the Software Quality Days 2019. It compares classic Inside-Out TDD to the London School approach, focusing on user interactions and mocking dependencies. Key aspects include a coding exercise on bank OCR, various TDD principles, and the importance of continuous learning and practice in developing quality software.
Code Retreat Venice (2016)
Code Retreat Venice (2016)Peter Kofler This document outlines Peter Kofler's philosophy and approach to mentoring development teams and improving code quality. He advocates for practices like pair programming, coding workshops, and coding dojos where developers practice coding katas in teams to improve skills like test-driven development, clean code, and design. The document provides an example agenda for a coderetreat where developers pair up to practice test-driving solutions for Conway's Game of Life using different programming languages and techniques like writing code without using if statements. The goal is for developers to learn through deliberate practice in a safe collaborative environment outside of work.
Deliberate Practice, New Learning Styles (2015)
Deliberate Practice, New Learning Styles (2015)Peter Kofler Peter Kofler discusses the software crisis, highlighting the increasing complexity and legacy issues in software development due to advancements in technology. He advocates for deliberate practice through methods like coding dojos and code katas to enhance the skills of software professionals. Kofler emphasizes the importance of continuous improvement, mentorship, and collaborative learning to produce high-quality software.
Similar to Coding Dojo: Adding Tests to Legacy Code (2014) (20)
Coding Dojo: Fun with Tic-Tac-Toe (2014)
Coding Dojo: Fun with Tic-Tac-Toe (2014)Peter Kofler This document summarizes a coding dojo event focused on tic-tac-toe. The event introduces pair programming and test-driven development techniques. Attendees work in pairs to implement tic-tac-toe under constraints, such as writing the worst code possible initially and then refactoring without talking. The goal is to learn through challenges and reflection on how to write better code.
Coding Dojo: Baby Steps (2014)
Coding Dojo: Baby Steps (2014)Peter Kofler The document discusses an approach to test-driven development called "baby steps" where developers write one test and the minimum code to pass that test within a 2 minute timer. They then refactor within the next timer period before repeating the process. It recommends practicing this approach to build TDD skills when developing a tic-tac-toe game.
Code Quality Assurance v4 (2013)
Code Quality Assurance v4 (2013)Peter Kofler The document summarizes a presentation by Peter Kofler on code quality assurance. It discusses Kofler's background and tools he uses to ensure code quality, including mindset/books, code kata exercises, test-driven development, code coverage, continuous integration, static analysis, and code review. It provides an example of using test-driven development to implement a prime factors kata coding exercise.
Pragmatic Introduction to Python Unit Testing (PyDays 2018)
Pragmatic Introduction to Python Unit Testing (PyDays 2018)Peter Kofler The document presents a pragmatic introduction to unit testing in Python by Peter Kofler, emphasizing the importance of quality and professionalism in software development. It covers key concepts of unit testing, including the definition of a unit test, the structure of test classes and methods, and best practices for writing effective tests. The presentation also includes practical exercises and a coding dojo mindset to encourage collaborative learning and improvement.
Nikolai Boiko "NodeJS Refactoring: How to kill a Dragon and stay alive"
Nikolai Boiko "NodeJS Refactoring: How to kill a Dragon and stay alive"NodeUkraine This document discusses refactoring NodeJS code. It defines different types of refactoring including architectural changes, long term refactoring, planned refactoring, in-feature refactoring, and immediate refactoring. It emphasizes the importance of writing a detailed refactoring plan with tasks estimated to less than 2 days each. The plan should include feature implementation, required refactoring, and code cleanup sections. It also provides tips for refactoring such as keeping the code in a working state, merging changes daily, and completing refactoring in small iterative steps.
Practical (J)Unit Testing (2009)
Practical (J)Unit Testing (2009)Peter Kofler The document discusses unit testing and JUnit. It provides an overview of JUnit basics like test methods, assertions and fixtures. It also covers more advanced testing topics such as mocking, testing private methods, dealing with singletons, timing issues, and testing Java EE applications. The presentation encourages writing high-quality test code and tuning test performance.
Coding Dojo: Roman Numerals (2014)
Coding Dojo: Roman Numerals (2014)Peter Kofler This document outlines an agenda for a coding dojo event hosted by Peter Kofler on converting numbers to and from Roman numerals. The event will use pair programming and test-driven development. Attendees will practice converting numbers to Roman numerals under constraints like not using loops or maps. They will also convert Roman numerals to numbers while pair programming in a "ping-pong" style.
Escape the legacy code matrix - Vimercate
Escape the legacy code matrix - VimercateMario Russo The document discusses strategies for dealing with legacy code, including understanding how it works through tracing actions, sketching refactorings, achieving full test coverage starting with the shortest code branches, using tests to explore unknown areas of code, extracting code sections to focus on changes, and making changes guided by tests in a refactoring process that stops when changes are easy to apply. It recommends techniques like pair programming, separating new features from existing code, and using shortcuts to avoid repetition.
Clean Code
Clean Codessusera3d06b1 The document discusses concepts and best practices for writing clean code, including:
- The importance of clean code for productivity and maintainability.
- Philosophies like SOLID principles and test-driven development.
- Guidelines for naming variables and functions clearly and meaningfully.
- Rules for writing small, focused functions that do one thing well.
- When comments are acceptable to provide necessary information versus when they indicate the need to improve code clarity.
Coding Dojo: Bank OCR (2014)
Coding Dojo: Bank OCR (2014)Peter Kofler The document summarizes a coding dojo session led by Peter Kofler on parsing bank account numbers from an optical character recognition (OCR) file. The session followed a structured format including introductions, coding periods with retrospectives, and a closing circle. Participants were assigned to write a program to take an OCR file with account numbers represented as pipes and underscores and parse it into actual numbers, with considerations for readability, matching digits, and flexibility. The goal was to focus on doing the assignment perfectly rather than just getting it done.
Deliberate Practice (2014)
Deliberate Practice (2014)Peter Kofler Peter Kofler discusses deliberate practice techniques for software developers to improve their skills. He describes code katas, which are short programming exercises done daily for practice and memorization. Coding dojos are regular meetups where developers work on katas together for learning and fun away from work pressures. Code retreats are full-day intensive sessions focusing on fundamentals through pair programming and switching partners frequently. The goal is to learn through practice and experimentation rather than production work.
Code Quality Assurance with PMD (2004)
Code Quality Assurance with PMD (2004)Peter Kofler This document summarizes Peter Kofler's presentation on using PMD for static code analysis at Herold Business Data from 2004 to 2006. It discusses setting up daily builds, integrating static analysis with PMD, categorizing rule violations, and processes for addressing rule violations. The presentation outlines several serious coding errors and warnings to prioritize fixing. It also describes next steps of running analysis on additional rules and addressing another set of 100 rule violations.
Narrow Down What to Test
Narrow Down What to TestZsolt Fabok This document discusses how to prioritize what parts of an old application to test first. It recommends determining which features are most used, which parts change frequently, which parts change data, and where failures are likely. The author provides examples of using code coverage, version control history, code reviews, and static analysis to evaluate parts of the code. He then demonstrates how to start writing tests for the highest priority class, using assertions to drive test design and increase coverage incrementally.
Testing & should i do it
Testing & should i do itMartin Sykora Testing code is important to avoid bugs but many PhD students do not rigorously test their code. This document discusses why testing is important and provides tips for effective testing strategies. It recommends having a testing plan, using unit tests, and test-driven development. Automated testing helps ensure code works as intended before and after changes. Rigorous testing adds confidence and allows code to be reused with less risk.
100% Code Coverage in Real World Software
100% Code Coverage in Real World SoftwareAndreas Czakaj The document discusses the importance of achieving 100% code coverage in software development, arguing that automated testing protects against regression bugs, ensures future code adaptability, and fosters quicker development. It highlights the need for a test-driven approach to maintain high code quality and outlines strategies for maintaining coverage, including understanding metrics and avoiding design pitfalls. The document concludes that while achieving full coverage may be challenging, it is essential for maintaining high-quality, maintainable software.
Code Smells
Code SmellsMrinal Bhattacaharya Software Craftsmanship emphasizes not just working software but well-crafted software, steadily adding value through change. Code smells are indicators that code may need refactoring to improve design. Common code smells include lost intent where code purpose is unclear, duplicated code, long methods, large classes, and primitive obsession where code is too simplistic. Refactoring helps reduce technical debt by improving code design without changing functionality.
Clean code and code smells
Clean code and code smellsMd. Aftab Uddin Kajal The document discusses principles of clean code and code smells. It provides definitions and examples of clean code from various experts, including short functions that do one thing, meaningful names, comments that are useful but not redundant, and following the law of Demeter. The document also discusses writing classes with good organization and a single responsibility.
Working Effectively with Legacy Code: Lessons in Practice
Working Effectively with Legacy Code: Lessons in PracticeAmar Shah The document discusses key concepts from Michael C. Feathers' book on effectively working with legacy code, emphasizing the challenges of making changes to untested and poorly understood code. It outlines methods for identifying change points, breaking dependencies, and writing tests before refactoring, as well as addressing common dilemmas faced by developers dealing with legacy systems. Overall, the text promotes a structured approach to refactoring and understanding legacy code as a necessary and learnable skill in software development.
Global Day of Code Retreat (2013)
Global Day of Code Retreat (2013)Peter Kofler The document describes a Global Day of Code Retreat event in Vienna in December 2013 hosted by Peter Kofler. The one-day event focuses on improving code quality through collaborative coding exercises and principles of test-driven development. Attendees will participate in sessions practicing pairing programming, refactoring existing code, and discussing techniques for writing high-quality code. The goal is for participants to learn through doing rather than focusing on completing the exercises.
Code Smells and Refactoring - Satyajit Dey & Ashif Iqbal
Code Smells and Refactoring - Satyajit Dey & Ashif IqbalCefalo This document discusses code smells and refactoring. It begins by defining technical debt as implied costs from easy short-term solutions versus better long-term approaches. It then lists common causes of technical debt like business pressure and lack of testing. Different types of technical debt like code debt and design debt are identified. Common code smells like long methods, duplicate code, and primitive obsession are explained along with refactoring treatments like extracting methods and replacing conditionals with polymorphism. The goal of refactoring is to improve code quality by treating code smells.
Ad
More from Peter Kofler (7)
Writing Tests with the Unity Test Framework
Writing Tests with the Unity Test FrameworkPeter Kofler The document discusses the importance of writing automated tests using the Unity Test Framework, highlighting the benefits of Test-Driven Development (TDD) and providing insights into testing practices for both business logic and user interfaces. It emphasizes the need for effective test practices, exploring challenges and strategies for testing in the 3D environment typical in Unity development. The authors encourage starting automated testing in existing projects gradually while focusing on high-risk or frequently modified code.
GDCR15 in Las Palmas, Gran Canaria
GDCR15 in Las Palmas, Gran CanariaPeter Kofler This document outlines an agenda for a coderetreat event focused on practicing software development skills. The event will involve pairing programmers who will practice test-driven development and object-oriented design principles by implementing Conway's Game of Life using various programming language and problem constraints. Presenters will discuss techniques for improving code quality through deliberate practice and emphasize learning through collaboration.
Designing Test Cases for the Gilded Rose Kata v2 (2015)
Designing Test Cases for the Gilded Rose Kata v2 (2015)Peter Kofler This document discusses designing test cases for the Gilded Rose kata. It introduces Peter Kofler, a software developer and code mentor, and describes a coding dojo where participants practice test-driven development and refactoring skills. The goal is to create unit tests that thoroughly cover the requirements of updating item quality and sell-in values in an inventory system, including edge cases for special items like Brie and backstage passes.
Pair Programming (2015)
Pair Programming (2015)Peter Kofler Peter Kofler presented on pair programming. Some key benefits of pair programming include improved code quality, knowledge sharing between partners, and mentoring junior developers. Effective pair programming involves two programmers working together at one workstation, with one acting as the driver writing code while the other navigates, reviewing the work. It is most useful for production code, programming tasks requiring problem solving, and mentoring novices. Managing the human dynamics between partners and practicing techniques like ping-pong pairing are important for success.
Pragmatic Introduction to PHP Unit Testing (2015)
Pragmatic Introduction to PHP Unit Testing (2015)Peter Kofler The document serves as a pragmatic introduction to unit testing with PHP, featuring insights from Peter Kofler, a seasoned software developer. It outlines the importance of unit tests in ensuring code quality, with techniques and strategies for effective testing using PHPUnit. Additionally, it emphasizes collaborative learning through coding dojos and continuous improvement in programming practices.
Coding Dojo for Testers/Testing Dojo: Designing Test Cases with FitNesse (2014)
Coding Dojo for Testers/Testing Dojo: Designing Test Cases with FitNesse (2014)Peter Kofler 1) Peter Kofler gave a presentation on designing test cases for the Gilded Rose Kata using FitNesse.
2) He discussed the Coding Dojo mindset of collaborative learning and test-driven development.
3) The Gilded Rose Kata models an inventory system where items degrade over time according to various rules, including special rules for items like Brie and backstage passes. The goal is to write tests to cover these rules.
Code Refactoring - Live Coding Demo (JavaDay 2014)
Code Refactoring - Live Coding Demo (JavaDay 2014)Peter Kofler Peter Kofler gives a live coding demonstration of refactoring code to add a new requirement to an inventory management system. He first refactors the existing code to make it more readable and maintainable by removing duplication, splitting methods, and simplifying conditions. He then implements the new requirement that conjured items degrade in quality twice as fast by extracting a strategy pattern. The demonstration shows how refactoring first makes it possible to easily add new features to the code while preserving its behavior.
Ad
Recently uploaded (20)
9-1-1 Addressing: End-to-End Automation Using FME
9-1-1 Addressing: End-to-End Automation Using FMESafe Software This session will cover a common use case for local and state/provincial governments who create and/or maintain their 9-1-1 addressing data, particularly address points and road centerlines. In this session, you'll learn how FME has helped Shelby County 9-1-1 (TN) automate the 9-1-1 addressing process; including automatically assigning attributes from disparate sources, on-the-fly QAQC of said data, and reporting. The FME logic that this presentation will cover includes: Table joins using attributes and geometry, Looping in custom transformers, Working with lists and Change detection.
"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...Fwdays What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.
Hyderabad MuleSoft In-Person Meetup (June 21, 2025) Slides
Hyderabad MuleSoft In-Person Meetup (June 21, 2025) SlidesRavi Tamada Hyderabad MuleSoft In-Person Meetup (June 21, 2025) Slides
cnc-processing-centers-centateq-p-110-en.pdf
cnc-processing-centers-centateq-p-110-en.pdfAmirStern2 מרכז עיבודים תעשייתי בעל 3/4/5 צירים, עד 22 החלפות כלים עם כל אפשרויות העיבוד הדרושות. בעל שטח עבודה גדול ומחשב נוח וקל להפעלה בשפה העברית/רוסית/אנגלית/ספרדית/ערבית ועוד..
מסוגל לבצע פעולות עיבוד שונות המתאימות לענפים שונים: קידוח אנכי, אופקי, ניסור, וכרסום אנכי.
" How to survive with 1 billion vectors and not sell a kidney: our low-cost c...
" How to survive with 1 billion vectors and not sell a kidney: our low-cost c...Fwdays Let's talk about our history. How we started the project with a small vector database of less than 2 million records. Later, we received a request for +100 million records, then another +100... And so gradually we reached almost 1 billion. Standard tools were quickly running out of steam - we were running into performance, index size, and very limited resources. After a long series of trials and errors, we built our own low-cost cluster, which today stably processes thousands of queries to more than 1B vectors.
2025_06_18 - OpenMetadata Community Meeting.pdf
2025_06_18 - OpenMetadata Community Meeting.pdfOpenMetadata The community meetup was held Wednesday June 18, 2025 @ 9:00 AM PST.
Catch the next OpenMetadata Community Meetup @ https://www.meetup.com/openmetadata-meetup-group/
In this month's OpenMetadata Community Meetup, "Enforcing Quality & SLAs with OpenMetadata Data Contracts," we covered data contracts, why they matter, and how to implement them in OpenMetadata to increase the quality of your data assets!
Agenda Highlights:
👋 Introducing Data Contracts: An agreement between data producers and consumers
📝 Data Contracts key components: Understanding a contract and its purpose
🧑🎨 Writing your first contract: How to create your own contracts in OpenMetadata
🦾 An OpenMetadata MCP Server update!
➕ And More!
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdf
A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy.pdfPriyanka Aash A Constitutional Quagmire - Ethical Minefields of AI, Cyber, and Privacy
CapCut Pro Crack For PC Latest Version {Fully Unlocked} 2025
CapCut Pro Crack For PC Latest Version {Fully Unlocked} 2025pcprocore 👉𝗡𝗼𝘁𝗲:𝗖𝗼𝗽𝘆 𝗹𝗶𝗻𝗸 & 𝗽𝗮𝘀𝘁𝗲 𝗶𝗻𝘁𝗼 𝗚𝗼𝗼𝗴𝗹𝗲 𝗻𝗲𝘄 𝘁𝗮𝗯> https://pcprocore.com/ 👈◀
CapCut Pro Crack is a powerful tool that has taken the digital world by storm, offering users a fully unlocked experience that unleashes their creativity. With its user-friendly interface and advanced features, it’s no wonder why aspiring videographers are turning to this software for their projects.
Security Tips for Enterprise Azure Solutions
Security Tips for Enterprise Azure SolutionsMichele Leroux Bustamante Delivering solutions to Azure may involve a variety of architecture patterns involving your applications, APIs data and associated Azure resources that comprise the solution. This session will use reference architectures to illustrate the security considerations to protect your Azure resources and data, how to achieve Zero Trust, and why it matters. Topics covered will include specific security recommendations for types Azure resources and related network security practices. The goal is to give you a breadth of understanding as to typical security requirements to meet compliance and security controls in an enterprise solution.
PyCon SG 25 - Firecracker Made Easy with Python.pdf
PyCon SG 25 - Firecracker Made Easy with Python.pdfMuhammad Yuga Nugraha Explore the ease of managing Firecracker microVM with the firecracker-python. In this session, I will introduce the basics of Firecracker microVM and demonstrate how this custom SDK facilitates microVM operations easily. We will delve into the design and development process behind the SDK, providing a behind-the-scenes look at its creation and features. While traditional Firecracker SDKs were primarily available in Go, this module brings a simplicity of Python to the table.
Enhance GitHub Copilot using MCP - Enterprise version.pdf
Enhance GitHub Copilot using MCP - Enterprise version.pdfNilesh Gule Slide deck related to the GitHub Copilot Bootcamp in Melbourne on 17 June 2025
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdf
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdfPriyanka Aash Oh, the Possibilities - Balancing Innovation and Risk with Generative AI
Smarter Aviation Data Management: Lessons from Swedavia Airports and Sweco
Smarter Aviation Data Management: Lessons from Swedavia Airports and SwecoSafe Software Managing airport and airspace data is no small task, especially when you’re expected to deliver it in AIXM format without spending a fortune on specialized tools. But what if there was a smarter, more affordable way?
Join us for a behind-the-scenes look at how Sweco partnered with Swedavia, the Swedish airport operator, to solve this challenge using FME and Esri.
Learn how they built automated workflows to manage periodic updates, merge airspace data, and support data extracts – all while meeting strict government reporting requirements to the Civil Aviation Administration of Sweden.
Even better? Swedavia built custom services and applications that use the FME Flow REST API to trigger jobs and retrieve results – streamlining tasks like securing the quality of new surveyor data, creating permdelta and baseline representations in the AIS schema, and generating AIXM extracts from their AIS data.
To conclude, FME expert Dean Hintz will walk through a GeoBorders reading workflow and highlight recent enhancements to FME’s AIXM (Aeronautical Information Exchange Model) processing and interpretation capabilities.
Discover how airports like Swedavia are harnessing the power of FME to simplify aviation data management, and how you can too.
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdf
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdfcaoyixuan2019 A presentation at Internetware 2025.
Salesforce Summer '25 Release Frenchgathering.pptx.pdf
Salesforce Summer '25 Release Frenchgathering.pptx.pdfyosra Saidani Salesforce Summer '25 Release Frenchgathering.pptx.pdf
Coding Dojo: Adding Tests to Legacy Code (2014)
- 1. Coding Dojo: Adding Tests to the Ugly Trivia Legacy Code Feb. 2014 Peter Kofler, ‘Code Cop’ @codecopkofler www.code-cop.org Copyright Peter Kofler, licensed under CC-BY.
- 2. Peter Kofler • Ph.D. (Appl. Math.) • Professional Software Developer for 14 years • “fanatic about code quality” • I help development teams PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 4. Coding Dojo Mindset ● Safe place outside work ● We are here to learn ● Need to slow down ● Focus on doing it right ● Collaborative Game PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 5. Dojo Structure ● Introduction 15' ● Coding 60' ● Break ● Interim (Retrospective) 15' ● Coding 60' ● Break ● Coding 60' ● Retrospective 30' PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 6. Legacy Code Skills ● Understanding Legacy Code ● Breaking Dependencies ● Bringing Code Under Test ● Refactoring Mercilessly PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 7. Ugly Trivia PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 8. Legacy Codebase “uglytrivia“ ● Get the code https://github.com/jbrains/trivia ● An implementation of Trivial Pursuit ● http://en.wikipedia.org/wiki/Trivial_Pursuit ● players take turns to answer trivia questions ● questions are split into categories ● players collect coins for right answers PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 9. Requirements ● Choose a testing framework ● Create tests, cover all cases ● May need to extract code to do that PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 10. Don't Focus on Getting it Done. F0cus on Doing It Perfectly.
- 11. →Practice
- 12. Extract Pure Functions ● find a piece of code that can be moved into a separate function by using “Extract Method“ ● replace all external dependencies within this function with independent parameters ● add a test for that function ● refactor the tested code as needed PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 13. Extract Class ● isolate functionality that somehow relates and can be separated from other behaviour ● turn isolated methods into pure functions ● extract these pure functions into a separate class ● add tests for that new class PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 14. Closing Circle ● What did you learn today? ● What surprised you today? ● What will you do differently in the future? PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 15. Peter Kofler @codecopkofler www.code-cop.org Idea by J.B.Rainsberger @jbrains https://github.com/jbrains/trivia PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY
- 16. CC Images ● Dojo http://www.flickr.com/photos/49715404@N00/3267627038/ ● Todos http://www.flickr.com/photos/kylesteeddesign/3724074594/ ● Trivia http://www.flickr.com/photos/thehoneybunny/207992667/ ● Wants you http://www.flickr.com/photos/shutter/105497713/ PETER KOFLER, CODE-COP.ORG FANATIC ABOUT CODE QUALITY