Code kata
15 likes3,316 views
The document discusses the evolution of programming as a profession, emphasizing the importance of mastering tools and techniques such as Test-Driven Development (TDD). It introduces code katas as methods for practicing programming skills through various styles, aiming for continuous improvement. Additionally, it provides resources and examples for further exploration in coding practices.
1 of 55
Downloaded 98 times
Ad
Recommended
Coding Dojo
Coding DojoCaike Souza
油
Coding Dojo is a group that meets regularly to practice coding techniques through kata exercises in a collaborative, non-competitive environment. Kata involves practicing detailed patterns of movements to improve skills. Dojos use two main formats: prepared kata where one person codes from scratch while others observe, and randori kata where pairs take turns coding while others can provide help. The goal is to practice and improve techniques through deliberate practice rather than solve real-world problems. Proper etiquette is followed, such as not disturbing those coding and asking for help when stuck. People of all skill levels are welcome to join the Orlando dojo meetings.Coding Dojo In 5 minutes
Coding Dojo In 5 minutesWouter Lagerweij
油
The document outlines the concept of a coding dojo, a collaborative environment where programmers train and learn together through pair programming. It describes pair programming roles (driver and observer), techniques such as test-driven development (TDD), and the retrospective process for continuous improvement. Additionally, it includes links to resources and emphasizes the non-competitive, educational focus of a coding dojo.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. 覯讌 startlink.live: ロ譴 (hongjun7) - Teamwork in Programming Contests
覯讌 startlink.live: ロ譴 (hongjun7) - Teamwork in Programming ContestsStartlink
油
This document discusses teamwork in programming contests. It describes a team that achieved success in several competitions from 2016-2017 by working together effectively. The key aspects of teamwork discussed are balancing individual strengths, collaborating during practice, and coordinating strategies during contests. Working as a coordinated team is emphasized as being more effective than working as individuals.TDD and Simple Design Workshop - Session 1 - November 2018
TDD and Simple Design Workshop - Session 1 - November 2018Paulo Clavijo
油
The document contains snippets of code and discussions around test-driven development (TDD) best practices. It discusses principles of TDD like writing tests first, keeping tests independent and self-contained, and refactoring code. It also provides examples of refactoring Java and Kotlin test code, including using custom assertions and organizing tests in arrange-act-assert blocks. Pair programming and software design principles like YAGNI, DRY and SOLID are also briefly mentioned.Talking about craftsmanship with ensaimadas and katas
Talking about craftsmanship with ensaimadas and katasRachel M. Carmena
油
The document discusses concepts related to software craftsmanship including extreme programming, test-driven development, code katas, and pair programming. It summarizes Ward Cunningham's views on extreme humility in software development and emphasizes practices like continuous integration, evolutionary design, and not making decisions prematurely. The document also promotes raising the bar of professional software development through communities of practice and sharing knowledge to help others learn.Talking about craftsmanship with "ensaimadas" and katas (May, 2018)
Talking about craftsmanship with "ensaimadas" and katas (May, 2018)Rachel M. Carmena
油
The document discusses the principles of craftsmanship in software development, emphasizing the importance of humility and collaboration in practices like extreme programming and pair programming. It highlights the significance of continuous improvement through refactoring and the necessity of maintaining high standards in code quality, alongside the adoption of methodologies such as Test-Driven Development (TDD). Additionally, it encourages a learning culture within teams to foster professional growth and effective partnerships.Programming in HTML5 with JavaScript and CSS3
Programming in HTML5 with JavaScript and CSS3Ali Fallahi
油
The document discusses JavaScript programming basics including variables, data types, operators, and strings. It introduces variable declaration and assignment, binary and unary operators, the string and Boolean data types, string concatenation, logical operators, and short-circuiting operators. Examples are provided to demonstrate JavaScript syntax and fundamentals.JavaScript Speech Recognition
JavaScript Speech RecognitionFITC
油
Speech recognition is the process of translating spoken words to text. It involves recording and digitizing audio, segmenting it into phonemes, applying a recognition model to analyze the phonemes against a lexicon and grammar, and returning a confidence-weighted transcript. Speech recognition accuracy is around 92% for English but lower for other languages. Mobile apps can use platform-specific APIs like Google Now on Android while the W3C specification allows cross-browser support. The related Speech Synthesis API can output responses by voice. Together these APIs enable interactive speech applications.Innoveo coding dojo
Innoveo coding dojoTech Head Brothers
油
The document discusses the concept of a coding dojo, which is a collaborative environment for developers to practice programming skills through challenges rather than competition. It explains the idea of 'code kata', a practice exercise designed to improve coding skills through repetition, along with two specific types: TDD kata and Randori kata, which involve different approaches to coding and testing. The goal is to provide a safe and enjoyable space for improvement and learning in programming.Lesson 1
Lesson 1Dr. Rupinder Singh
油
This document provides an overview of the C programming language. It discusses the history of C and how it was created by Dennis Ritchie in 1972. It also outlines the typical steps involved in a program development process, including requirement specification, analysis, design, implementation, verification and testing, and maintenance. The document explains that C is commonly used for systems software, compilers, databases, operating systems, and device drivers due to its efficiency and performance. It provides examples of where C is used and the benefits it provides.Class 4 IPO and Intro to Ruby
Class 4 IPO and Intro to RubyStephen Parsons
油
The document outlines a class focused on programmatic problem-solving using Ruby, covering topics such as installing Ruby, data types, and methods. It includes exercises related to input-process-output (IPO) approaches for problem-solving and introduces basic Ruby programming concepts. The agenda also mentions assignments due and future topics like set theory and Venn diagrams.Comefrom
ComefromSiddharth Shukla
油
The document introduces COMEFROM, a proposed programming construct that is the opposite of GOTO and allows code execution to jump to arbitrary points. It argues that writing structured code can be difficult and proposes COMEFROM as a solution to make code more readable by eliminating the need to explicitly define control flow. Using COMEFROM, code execution could jump to statements labeled with COMEFROM from any point. The concept is presented partly in jest to challenge conventions of programming language design.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.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.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.AgilePT2012 PGMADS
AgilePT2012 PGMADSCatarina Reis
油
The document presents a retrospective of the postgraduate course in Agile Software Development (PGMADS) focusing on agile methods, software testing, and soft skills. It details objectives, product backlog items, methods, and feedback from trainees regarding their experiences during the course. Key achievements included successful soft skills training and positive group dynamics, while challenges faced involved scheduling and assessment workload.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.Test Driven iOS Development (TDD)
Test Driven iOS Development (TDD)Babul Mirdha
油
TDD involves first writing an automated test that fails, then writing just enough code to pass that test, and refactoring the code. The red-green-refactor process ensures code is tested and well-designed. Studies found TDD reduced pre-release defects by 40-90% and increased initial development time by 15-35%, but allowed for faster development long-term by eliminating bugs early. The document demonstrates TDD with a temperature converter in Xcode, starting with failing tests for -40C=-40F and 30C=86F then coding to pass them.Kata String Calculator
Kata String CalculatorSoftware Craftsmanship Alicante
油
This document describes a meetup group called Software Craftsmanship Alicante. It provides information on who they are, what they like (agile and programming), and why they care about building community. It invites software developers who like agile to join them. It also provides contact details like their Meetup, Twitter, Slack, and GitHub pages. One member, Enrique Barbeito Garcia, then discusses test-driven development and demonstrates a string calculator kata.Kanban for Software Development and Kaizen Culture
Kanban for Software Development and Kaizen CultureAcquate
油
The document discusses the application of Kanban in software development, highlighting its history, basic concepts, and practical implementation to enhance workflows. It addresses common sources of waste in the development process, such as overproduction and delays, and emphasizes the importance of continuous improvement through Kaizen. The presentation underscores the significance of visual management tools like Kanban boards to track progress and improve team collaboration.Introduction of Tools for providing rich user experience in debugger
Introduction of Tools for providing rich user experience in debuggerNaoto Ono
油
1. The document discusses two sessions in a talk about tools for providing rich user experiences in debugging.
2. Session 1 focuses on debugging Ruby programs in Chrome DevTools, while Session 2 discusses tools for supporting debugging in VS Code.
3. Key features discussed include the History Inspector for going back to points in a debug session and the Object Inspector for visualizing objects.S坦 Os Imaturos N達O Testam
S坦 Os Imaturos N達O TestamCarlos Brando
油
This document discusses test-driven development (TDD) and behavior-driven development (BDD) processes. It provides examples of using RSpec to write tests for a User class in Ruby, starting with basic tests and refactoring the code and tests. Key points covered include the benefits of writing tests first, the red-green-refactor TDD cycle, describing behaviors with BDD, and using matchers like "have_many" in RSpec tests.Writing Performant Front-end Code
Writing Performant Front-end CodeLyubomir Bozhinov
油
The document is a presentation from a virtual conference discussing best practices for writing performant front-end code, led by Lyubomir Bozhinov. It emphasizes the importance of measuring code performance, optimizing JavaScript execution, and understanding the rendering process to enhance user experience. The talk covers various strategies, including minimizing layout complexity and using modern frameworks effectively to achieve optimal performance.TDD reloaded - JUGTAA 24 Ottobre 2012
TDD reloaded - JUGTAA 24 Ottobre 2012Pietro Di Bello
油
Test-Driven Development (TDD) is a software development technique focused on writing automated unit tests before the actual code, aiming for 'clean code that works.' The TDD process involves writing a failing test (red), making it pass (green), and then refactoring the code to eliminate duplication. The document explains the principles, benefits, and challenges of TDD, as well as providing a coding example and outlining the rules of unit testing.Test Driven Development
Test Driven DevelopmentValerio Maggio
油
The document outlines the principles and practices of Test Driven Development (TDD) in software engineering, emphasizing its role in enhancing the development process through continuous feedback, unit testing, and incremental improvements. It highlights the methodology where tests are written before code to clarify design intentions, reduce bugs, and simplify code. The document also discusses the social implications, benefits, and limitations of TDD, emphasizing the importance of discipline and the challenges associated with its implementation.TDD and Getting Paid
TDD and Getting PaidRowan Merewood
油
The document discusses Test-Driven Development (TDD) and emphasizes its significance and challenges in software engineering, particularly in writing good code. It outlines the steps of TDD, the importance of involving clients in the test creation process, and highlights potential pitfalls like over-promising and introducing tests too abruptly. Additionally, it addresses the need for a solid infrastructure to support testing and the distinction between developers' skill levels and code quality.Code Review
Code Reviewrantav
油
The document discusses code review tools and processes. It describes formal in-person code review meetings, challenges with scheduling and concentrating, and more efficient alternatives like email and web-based code review tools. It also covers motivations for code review like finding defects early and improving coding standards, and tips for effective code reviews like preparing, focusing on understanding rather than criticism, and keeping reviews short.Day1 - TDD (Lecture SS 2015)
Day1 - TDD (Lecture SS 2015)wolframkriesing
油
This document provides an overview of a presentation on test-driven development (TDD) and JavaScript. It discusses concepts like refactoring, unit testing, pair programming, and practicing TDD in small exercises called code katas. The presentation covers JavaScript topics like variable scoping and introduces the basic steps of TDD: writing a failing test first, then just enough code to make it pass before refactoring. It emphasizes that TDD helps produce a simple design and provides quick feedback.Unit Testing like a Pro - The Circle of Purity
Unit Testing like a Pro - The Circle of PurityVictor Rentea
油
The document discusses the principles and practices of professional unit testing, emphasizing the importance of test design, TDD (Test-Driven Development), and mocking. It covers strategies for writing reliable tests, maintaining code quality, and ensuring high test coverage while addressing common pitfalls and best practices. It aims to inform software developers about effective testing techniques to improve code robustness and maintainability.More Related Content
What's hot (10)
JavaScript Speech Recognition
JavaScript Speech RecognitionFITC
油
Speech recognition is the process of translating spoken words to text. It involves recording and digitizing audio, segmenting it into phonemes, applying a recognition model to analyze the phonemes against a lexicon and grammar, and returning a confidence-weighted transcript. Speech recognition accuracy is around 92% for English but lower for other languages. Mobile apps can use platform-specific APIs like Google Now on Android while the W3C specification allows cross-browser support. The related Speech Synthesis API can output responses by voice. Together these APIs enable interactive speech applications.Innoveo coding dojo
Innoveo coding dojoTech Head Brothers
油
The document discusses the concept of a coding dojo, which is a collaborative environment for developers to practice programming skills through challenges rather than competition. It explains the idea of 'code kata', a practice exercise designed to improve coding skills through repetition, along with two specific types: TDD kata and Randori kata, which involve different approaches to coding and testing. The goal is to provide a safe and enjoyable space for improvement and learning in programming.Lesson 1
Lesson 1Dr. Rupinder Singh
油
This document provides an overview of the C programming language. It discusses the history of C and how it was created by Dennis Ritchie in 1972. It also outlines the typical steps involved in a program development process, including requirement specification, analysis, design, implementation, verification and testing, and maintenance. The document explains that C is commonly used for systems software, compilers, databases, operating systems, and device drivers due to its efficiency and performance. It provides examples of where C is used and the benefits it provides.Class 4 IPO and Intro to Ruby
Class 4 IPO and Intro to RubyStephen Parsons
油
The document outlines a class focused on programmatic problem-solving using Ruby, covering topics such as installing Ruby, data types, and methods. It includes exercises related to input-process-output (IPO) approaches for problem-solving and introduces basic Ruby programming concepts. The agenda also mentions assignments due and future topics like set theory and Venn diagrams.Comefrom
ComefromSiddharth Shukla
油
The document introduces COMEFROM, a proposed programming construct that is the opposite of GOTO and allows code execution to jump to arbitrary points. It argues that writing structured code can be difficult and proposes COMEFROM as a solution to make code more readable by eliminating the need to explicitly define control flow. Using COMEFROM, code execution could jump to statements labeled with COMEFROM from any point. The concept is presented partly in jest to challenge conventions of programming language design.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.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.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.AgilePT2012 PGMADS
AgilePT2012 PGMADSCatarina Reis
油
The document presents a retrospective of the postgraduate course in Agile Software Development (PGMADS) focusing on agile methods, software testing, and soft skills. It details objectives, product backlog items, methods, and feedback from trainees regarding their experiences during the course. Key achievements included successful soft skills training and positive group dynamics, while challenges faced involved scheduling and assessment workload.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.Similar to Code kata (20)
Test Driven iOS Development (TDD)
Test Driven iOS Development (TDD)Babul Mirdha
油
TDD involves first writing an automated test that fails, then writing just enough code to pass that test, and refactoring the code. The red-green-refactor process ensures code is tested and well-designed. Studies found TDD reduced pre-release defects by 40-90% and increased initial development time by 15-35%, but allowed for faster development long-term by eliminating bugs early. The document demonstrates TDD with a temperature converter in Xcode, starting with failing tests for -40C=-40F and 30C=86F then coding to pass them.Kata String Calculator
Kata String CalculatorSoftware Craftsmanship Alicante
油
This document describes a meetup group called Software Craftsmanship Alicante. It provides information on who they are, what they like (agile and programming), and why they care about building community. It invites software developers who like agile to join them. It also provides contact details like their Meetup, Twitter, Slack, and GitHub pages. One member, Enrique Barbeito Garcia, then discusses test-driven development and demonstrates a string calculator kata.Kanban for Software Development and Kaizen Culture
Kanban for Software Development and Kaizen CultureAcquate
油
The document discusses the application of Kanban in software development, highlighting its history, basic concepts, and practical implementation to enhance workflows. It addresses common sources of waste in the development process, such as overproduction and delays, and emphasizes the importance of continuous improvement through Kaizen. The presentation underscores the significance of visual management tools like Kanban boards to track progress and improve team collaboration.Introduction of Tools for providing rich user experience in debugger
Introduction of Tools for providing rich user experience in debuggerNaoto Ono
油
1. The document discusses two sessions in a talk about tools for providing rich user experiences in debugging.
2. Session 1 focuses on debugging Ruby programs in Chrome DevTools, while Session 2 discusses tools for supporting debugging in VS Code.
3. Key features discussed include the History Inspector for going back to points in a debug session and the Object Inspector for visualizing objects.S坦 Os Imaturos N達O Testam
S坦 Os Imaturos N達O TestamCarlos Brando
油
This document discusses test-driven development (TDD) and behavior-driven development (BDD) processes. It provides examples of using RSpec to write tests for a User class in Ruby, starting with basic tests and refactoring the code and tests. Key points covered include the benefits of writing tests first, the red-green-refactor TDD cycle, describing behaviors with BDD, and using matchers like "have_many" in RSpec tests.Writing Performant Front-end Code
Writing Performant Front-end CodeLyubomir Bozhinov
油
The document is a presentation from a virtual conference discussing best practices for writing performant front-end code, led by Lyubomir Bozhinov. It emphasizes the importance of measuring code performance, optimizing JavaScript execution, and understanding the rendering process to enhance user experience. The talk covers various strategies, including minimizing layout complexity and using modern frameworks effectively to achieve optimal performance.TDD reloaded - JUGTAA 24 Ottobre 2012
TDD reloaded - JUGTAA 24 Ottobre 2012Pietro Di Bello
油
Test-Driven Development (TDD) is a software development technique focused on writing automated unit tests before the actual code, aiming for 'clean code that works.' The TDD process involves writing a failing test (red), making it pass (green), and then refactoring the code to eliminate duplication. The document explains the principles, benefits, and challenges of TDD, as well as providing a coding example and outlining the rules of unit testing.Test Driven Development
Test Driven DevelopmentValerio Maggio
油
The document outlines the principles and practices of Test Driven Development (TDD) in software engineering, emphasizing its role in enhancing the development process through continuous feedback, unit testing, and incremental improvements. It highlights the methodology where tests are written before code to clarify design intentions, reduce bugs, and simplify code. The document also discusses the social implications, benefits, and limitations of TDD, emphasizing the importance of discipline and the challenges associated with its implementation.TDD and Getting Paid
TDD and Getting PaidRowan Merewood
油
The document discusses Test-Driven Development (TDD) and emphasizes its significance and challenges in software engineering, particularly in writing good code. It outlines the steps of TDD, the importance of involving clients in the test creation process, and highlights potential pitfalls like over-promising and introducing tests too abruptly. Additionally, it addresses the need for a solid infrastructure to support testing and the distinction between developers' skill levels and code quality.Code Review
Code Reviewrantav
油
The document discusses code review tools and processes. It describes formal in-person code review meetings, challenges with scheduling and concentrating, and more efficient alternatives like email and web-based code review tools. It also covers motivations for code review like finding defects early and improving coding standards, and tips for effective code reviews like preparing, focusing on understanding rather than criticism, and keeping reviews short.Day1 - TDD (Lecture SS 2015)
Day1 - TDD (Lecture SS 2015)wolframkriesing
油
This document provides an overview of a presentation on test-driven development (TDD) and JavaScript. It discusses concepts like refactoring, unit testing, pair programming, and practicing TDD in small exercises called code katas. The presentation covers JavaScript topics like variable scoping and introduces the basic steps of TDD: writing a failing test first, then just enough code to make it pass before refactoring. It emphasizes that TDD helps produce a simple design and provides quick feedback.Unit Testing like a Pro - The Circle of Purity
Unit Testing like a Pro - The Circle of PurityVictor Rentea
油
The document discusses the principles and practices of professional unit testing, emphasizing the importance of test design, TDD (Test-Driven Development), and mocking. It covers strategies for writing reliable tests, maintaining code quality, and ensuring high test coverage while addressing common pitfalls and best practices. It aims to inform software developers about effective testing techniques to improve code robustness and maintainability.Developers mDay u Banjoj Luci - Milan Popovi, PHP Srbija Testimony (about...
Developers mDay u Banjoj Luci - Milan Popovi, PHP Srbija Testimony (about...mCloud
油
This document discusses the importance of testing software. It outlines 30 tips for writing tests, including writing tests before code, treating tests like code, minimizing asserts per test, using data providers, and allocating time for testing in estimates. Testing helps catch bugs, improve code quality, and ensure stability. The document emphasizes that automated testing is key and should test everything that could break an app.Xp days ukraine 2012
Xp days ukraine 2012Wiktor 纏onowski
油
The document discusses reversing the traditional tests pyramid when dealing with legacy code. It notes that with legacy code, there may be no true units to unit test. Instead, it advocates starting with end-to-end tests to build confidence to refactor the code into units and add integration and unit tests. However, it warns that end-to-end tests are long to maintain. The goal is to slowly reverse the tests pyramid by refactoring code into units and adding tests at each level to manage technical debt over time. Paying down technical debt is important to maintain the ability to change software.Test Driven Development
Test Driven Developmentjakubkoci
油
This document discusses test-driven development (TDD) and behavior-driven development (BDD). It covers the core principles and rules of TDD, including writing failing tests first and then code to pass the tests. The benefits of TDD are described, such as improved design, documentation, and catching errors earlier. Challenges with TDD are acknowledged, but it is argued that with experience writing clean code and following design best practices, TDD can help developers write higher quality code. Tools for writing tests like Hamcrest and AssertJ are also mentioned.TDD CrashCourse Part2: TDD
TDD CrashCourse Part2: TDDDavid Rodenas
油
El curso de Desarrollo Guiado por Pruebas (TDD) dirigido por David R坦denas analiza los principios y mitos del TDD, enfatizando su valor en la facilitaci坦n del cambio en el software y el papel de la disciplina en la programaci坦n. A trav辿s de ejemplos y reglas pr叩cticas, se discute c坦mo mejorar el dise単o del c坦digo y la necesidad de mantener pruebas efectivas para garantizar la calidad del software. Adem叩s, se aborda el debate sobre la efectividad del TDD, con reflexiones sobre su implementaci坦n y c坦mo evitar malentendidos comunes en su aplicaci坦n.Bdd - L'arte di non farsi i fatti propri
Bdd - L'arte di non farsi i fatti propriCommit University
油
The document discusses Test Driven Development (TDD) and the challenges associated with its implementation, including common mistakes and team pitfalls. It emphasizes the benefits of TDD in improving code quality and reducing defect rates while also introducing Behavior Driven Development (BDD) as a collaborative approach to defining and testing software behaviors. Key concepts include defining business goals and using a shared language among stakeholders to create executable specifications.TDD in Python With Pytest
TDD in Python With PytestEddy Reyes
油
This document provides an overview of Test-Driven Development (TDD) using Python and pytest, emphasizing its methodology and effective practices. It includes a step-by-step guide on implementing a Flask 'Hello World' application using TDD principles and highlights the importance of mocking external dependencies. Additional resources and tools for TDD in Python are also discussed.It's all about behaviour, also in php - phpspec
It's all about behaviour, also in php - phpspecGiulio De Donato
油
The document discusses test-driven development (TDD) and behavior-driven development (BDD). It explains that BDD uses external specifications to describe behavior before coding starts. This solves issues with TDD like where to begin and what to test. BDD uses a double cycle of writing scenarios in Behat and then examples in Phpspec at the internal class level. Phpspec is used to describe behavior through examples before coding classes. The document provides instructions on installing Phpspec and describes how to define a specification and examples.CD in Machine Learning Systems
CD in Machine Learning SystemsThoughtworks
油
The document discusses continuous deployment (CD) in machine learning, emphasizing the importance of rapid deployment of new features, improved quality through smaller changes, and the need for structured testing and monitoring. It highlights the critical role of data management, model performance evaluation, and the implications of employing machine learning systems. Best practices, including feature toggles, test pyramids, and monitoring for errors, are outlined to ensure effective model validation and operationalization in production environments.Ad
More from Giordano Scalzo (14)
The Joy Of Server Side Swift Development
The Joy Of Server Side Swift DevelopmentGiordano Scalzo
油
The document provides a historical overview of programming languages from the 1940s to the 2010s, detailing their development and significance. It introduces the joy of server-side Swift development, showcasing frameworks like Perfect, Vapor, and Kitura while highlighting their features and performance metrics. Additionally, the document includes code snippets and examples for creating a weather application and a Facebook Messenger chatbot using Swift.How to Clone Flappy Bird in Swift
How to Clone Flappy Bird in SwiftGiordano Scalzo
油
This document provides step-by-step instructions for cloning and building a Flappy Bird clone using Swift. It begins with setting up the project structure and basic gameplay elements like the background, ground and bird. It then adds parallax scrolling, bird animation and physics. Pipes and collision detection are implemented along with scoring. The document details many Swift concepts like classes, protocols and physics bodies to recreate the classic mobile game.A swift introduction to Swift
A swift introduction to SwiftGiordano Scalzo
油
The document serves as a comprehensive guide to various Swift programming concepts, covering topics such as closures, functions, classes, and enumerations. It includes code examples demonstrating the usage of conditional statements, optional handling, and tuple returns, among others. Additionally, the document discusses advanced features like protocols, extensions, and generics, along with unit testing strategies.Better Software: introduction to good code
Better Software: introduction to good codeGiordano Scalzo
油
The document discusses good code practices and principles. It begins with an agenda that covers why code quality matters, object oriented principles like SOLID, code smells and heuristics for good code, and concludes with questions. Some key principles discussed include the single responsibility principle, open/closed principle, Liskov substitution principle, and interface segregation principle. Examples are given to illustrate how to apply these principles and improve code quality.Tame Accidental Complexity with Ruby and MongoMapper
Tame Accidental Complexity with Ruby and MongoMapperGiordano Scalzo
油
The document introduces MongoMapper, an ORM for MongoDB that aims to simplify Rails application development by avoiding accidental complexity. It discusses how MongoMapper handles object persistence, embedded documents, validation and callbacks. It also covers querying capabilities via Plucky and available plugins. The goal is to provide a familiar ActiveRecord-like interface while taking advantage of MongoDB's flexible data model.JavaScript Survival Guide
JavaScript Survival GuideGiordano Scalzo
油
The document provides an overview of essential JavaScript concepts for survival including scope, literals and constructors, functions, and testing frameworks. It discusses best practices for declaring variables with var, using constructor functions and prototypes to create objects, encapsulating functions and data with closures, and popular JavaScript testing frameworks like QUnit, JSUnit, and Vows.JavaScript Patterns
JavaScript PatternsGiordano Scalzo
油
The document discusses JavaScript patterns. It begins by introducing the author and their motivation for learning patterns. It then covers essential patterns around scope, literals and constructors, functions, and code reuse. It discusses the single var pattern, constructor functions, private members, and classical versus prototypal inheritance. The document is an educational guide to common JavaScript patterns.Tdd iPhone For Dummies
Tdd iPhone For DummiesGiordano Scalzo
油
The document discusses test-driven development (TDD). It states that TDD relies on short development cycles where the developer first writes an automated test case that defines a new function or improvement. Then the developer produces code to pass that test, and refactors the new code to acceptable standards.Better Software Developers
Better Software DevelopersGiordano Scalzo
油
The document discusses better software development and hiring better developers. It notes that 24% of software projects will be cancelled, 32% will be late or over budget, and 44% will have severe technical difficulties. It discusses the rise of complexity in software projects and different development methodologies like waterfall, UML, design patterns, and agile. It suggests that a process is not enough and skilled people are needed. It describes different types of developers and proposes studying, finding a mentor, and doing code katas to improve skills. It discusses hiring based on the two-factor theory of hygiene and motivation factors. The conclusion is to raise the bar when hiring, forget cheaper developers, and hire the best in order to improve outcomes forAgile Iphone Development
Agile Iphone DevelopmentGiordano Scalzo
油
The document discusses iPhone app development using Objective-C. It covers the basics of getting started, including what is needed to begin like a Mac, Xcode, and an iPhone. It then explains key Objective-C concepts like classes, methods, and memory management using retain counts. The document also discusses unit testing iOS apps using OCUnit and some Xcode tips. It emphasizes testing first and concludes by noting the market demands more apps and there is room for improvement.XpUg Coding Dojo: KataYahtzee in Ocp way
XpUg Coding Dojo: KataYahtzee in Ocp wayGiordano Scalzo
油
The document describes the OCP Kata process for practicing object-oriented design principles. It involves:
1. Writing a failing test case
2. Creating a factory to pass the test with minimal code
3. Writing another failing test and refactoring to pass it
4. Repeating steps 2-3, refactoring each time to keep tests failing until the new case is implemented
An example FizzBuzz kata is provided, starting with a test for single numbers then refactoring to add logic for multiples of 3 (Fizz) through repeated tests and refactoring. The goal is to practice separation of concerns through object oriented patterns.Bdd: Tdd and beyond the infinite
Bdd: Tdd and beyond the infiniteGiordano Scalzo
油
The document discusses behavior driven development (BDD) and test-driven development (TDD). It shows an example of incrementally developing a FizzBuzz program using TDD and JUnit tests. First, a single test is written to verify the output for the number 1. Then tests are added and code is modified to pass each new test, building up the full FizzBuzz logic over multiple test/code iterations. The document also discusses differences between traditional TDD testing and BDD-style testing, where test method names are written as sentences describing expected behavior.10 minutes of me: Giordano Scalzo's Visual Resume
10 minutes of me: Giordano Scalzo's Visual ResumeGiordano Scalzo
油
Giordano Scalzo is a software enthusiast with over 25 years of experience, graduating in electronics engineering in 1996 and working in various roles including software engineer, team leader, and agile project manager. He has a strong belief in software craftsmanship and has co-founded a software company, although faced challenges in the startup market. Currently based in London, he enjoys coding, mentoring, and participating in developer communities while continuously seeking new challenges.Scrum in an hour
Scrum in an hourGiordano Scalzo
油
Scrum is an agile framework for managing complex projects. It emphasizes transparency, inspection, and adaptation. Key aspects of Scrum include short sprints with fixed durations, daily stand-ups, sprint planning and reviews, and retrospectives. The product owner prioritizes features in the backlog and the cross-functional team works to complete them in sprints. Applying Scrum principles like frequent delivery, transparency, and process improvement can help manage uncertainty, deliver value faster, improve quality, and eliminate waste.Ad
Code kata
- 2. Who is a programmer?
- 3. A step towards management...
- 4. ...or point of no return!
- 5. NO!
- 6. Classical Ages of Computer Programming
- 7. Dark Ages of Computer Programming
- 8. Renaissance of Computer Programming
- 10. The Way of the carpenter is to become pro鍖cient in the use of his tools, 鍖rst to lay his plans with a true measure and then perform his work according to plan. -Go Rin No Sho
- 11. SW Craftsman Tools: Languages
- 12. SW Craftsman Tools: Tdd Test-driven development (TDD) is a software development technique that relies on the repetition of a very short development cycle http://en.wikipedia.org/wiki/Test-driven_development
- 13. Tdd first the developer writes a failing automated test case that defines a desired improvement or new function http://en.wikipedia.org/wiki/Test-driven_development
- 14. Tdd then produces code to pass that test http://en.wikipedia.org/wiki/Test-driven_development
- 15. Tdd and finally refactors the new code to acceptable standard http://en.wikipedia.org/wiki/Test-driven_development
- 16. Tdd cycle
- 17. Tdd cycle
- 18. Tdd cycle
- 19. Tdd cycle
- 20. Tdd cycle
- 21. Tdd cycle
- 22. Tdd cycle
- 23. Tdd cycle
- 24. Tdd cycle
- 25. Tdd cycle
- 27. Tdd cycle Easy, isnt it?
- 28. Tdd cycle No, at all! :-(
- 29. SW Craftsman Tools: Split stories Business problem
- 30. SW Craftsman Tools: Split stories Presentation Business logic Persistence
- 31. SW Craftsman Tools: Split stories Ft1 Ft2 Ftn Presentation Business logic Persistence
- 32. SW Craftsman Tools: Editors
- 33. When improve them?
- 34. Work != Practice
- 35. Code kata
- 36. Code kata Kata ( or literally: "form") is a Japanese word describing detailed choreographed patterns of movements practised either solo or in pairs.
- 37. Code kata Practice on small exercise
- 38. Code kata 30 minutes to an hour long
- 39. Code kata styles Prag Dave Thomas Simple Problems Many correct solutions Different each time Learn by experimentation
- 40. Code kata styles Uncle Bob Martin Copy a Master Follow forms precisely Learn by Repetition Aim for perfect performance
- 41. Performance!
- 42. Kata 9: Back to Checkout http://codekata.pragprog.com/2007/01/kata_nine_back_.html Item Unit Special Price Price -------------------------- A 50 3 for 130 B 30 2 for 45 C 20 D 15
- 43. total with no special offers it "is zero when nothing is scanned" it "is 50 when A is scanned" it "is 80 when AB is scanned" it "is 115 when CDBA is scanned"
- 44. total when A is on special offer it "is 130 when AAA is scanned" it "is 180 when AAAA is scanned" it "is 260 when AAAAAA is scanned"
- 45. total when A and B are both in special offer it "is 175 when AAABB is scanned"
- 46. Resources
- 52. Randori
- 53. Code Retreat
- 54. Its your turn!