Workshop fight legacy code write unit test
•
3 likes•588 views
Stanly Lau is an agile coach and software developer based in Singapore who has worked with companies of various sizes in industries such as insurance, mobile safety, education, logistics, and banking. The document discusses legacy code and how to deal with it. Legacy code is defined as code without unit tests that is difficult to change and prone to bugs. It recommends adopting modern engineering practices like test-driven development and refactoring to incrementally add tests and make changes to legacy code.
Report
Share
Report
Share
Download to read offline
Recommended
Is Xp still extreme?
The document discusses the history and principles of Extreme Programming (XP). It traces XP back to its origins on the Chrysler Comprehensive Compensation System project in 1993. The core values of XP like communication, simplicity, feedback and courage are explained. Fundamental XP practices like pair programming, planning game, test-driven development and continuous integration are also outlined. The document then considers how technology advances since XP was first developed have changed how software teams work. It concludes by questioning how "extreme" software teams are willing to be in exposing themselves to achieve success for their customers, teams and society.
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
Stanly Lau is an agile coach and software developer based in Singapore who has worked with companies of various sizes in industries such as insurance, mobile safety, education, logistics, and banking. The document discusses legacy code and provides tips on how to deal with it. Legacy code is defined as code without unit tests that is difficult to change and prone to bugs. It recommends adopting modern engineering practices like test-driven development and refactoring. It also outlines an approach for identifying change points, breaking dependencies, writing tests, and then making changes to legacy code in a safe manner.
Unit testing for project managers
This presentation gives you the evidence as to why unit testing works and a process for how to bring it your team as soon as possible. There's a reason why the growth of unit testing, and automated unit testing in particular, has exploded over the past few years. It not only improves your code, it's faster than releasing code without tests. You'll learn: What, exactly, is a unit test?; The 7 reasons why managers love unit testing; and how to change mindset and processes to start unit testing now.
[XP Day Vietnam 2015] XP is not windows XP
This document discusses eXtreme Programming (XP), an agile software development framework. It provides definitions and explanations of key XP practices, principles, and values. The main points are:
- XP focuses on practices like pair programming, testing, code reviews, and frequent integration that are taken "to the extreme."
- The core values of XP center on individuals, interactions, working software, customer collaboration, and responding to change.
- Key practices include sit together pairing, testing, informative workspaces, user stories, test-driven development, and more.
- Principles guide the framework and include ideas like baby steps, mutual benefit, flow, reflection, and redundancy.
Test Driven Development
This document discusses test-driven development (TDD) and unit testing. It defines TDD as a process that involves writing a failing test first, then implementing code to pass that test, and refactoring if needed. Key benefits of TDD and unit testing include reduced bugs, lower maintenance costs, and improved code design. The document provides guidelines for writing good unit tests and emphasizes that tests should be quick, isolated, and answer what behavior was tested and what the expected and actual results were.
Why pay two developers to do the work of one?
Let's explore some of the myths that you hear around XP development, and talk about why your developers should be using XP to create quality, well-crafted software.
Paul Ellarby - Why do scrum?
The document discusses several key principles of agile development including building the right thing instead of wasting time on specifications that may change, delivering value incrementally, responding to change, and building quality into the product through practices like unit testing, test-driven development, pairing, refactoring, and continuous integration. It emphasizes that customers' understanding of what they want evolves over time and that many things change along the way, so an agile approach helps teams adapt.
Agileee 2012
The document discusses reversing the "tests pyramid" approach to address technical debt in legacy code. It notes that unit testing is difficult for code without separation of concerns, but refactoring without tests is risky. It proposes starting with high-level tests to gain confidence for refactoring into units and writing unit tests incrementally. However, end-to-end tests are long to maintain, and if needed, the architecture may be flawed. Reversing the tests pyramid and refactoring code in this way takes time but pays back technical debt and allows for sustainable changes. Beware of refactoring just for its own sake - focus on removing duplication and improving changeability.
Recommended
Is Xp still extreme?
The document discusses the history and principles of Extreme Programming (XP). It traces XP back to its origins on the Chrysler Comprehensive Compensation System project in 1993. The core values of XP like communication, simplicity, feedback and courage are explained. Fundamental XP practices like pair programming, planning game, test-driven development and continuous integration are also outlined. The document then considers how technology advances since XP was first developed have changed how software teams work. It concludes by questioning how "extreme" software teams are willing to be in exposing themselves to achieve success for their customers, teams and society.
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
Stanly Lau is an agile coach and software developer based in Singapore who has worked with companies of various sizes in industries such as insurance, mobile safety, education, logistics, and banking. The document discusses legacy code and provides tips on how to deal with it. Legacy code is defined as code without unit tests that is difficult to change and prone to bugs. It recommends adopting modern engineering practices like test-driven development and refactoring. It also outlines an approach for identifying change points, breaking dependencies, writing tests, and then making changes to legacy code in a safe manner.
Unit testing for project managers
This presentation gives you the evidence as to why unit testing works and a process for how to bring it your team as soon as possible. There's a reason why the growth of unit testing, and automated unit testing in particular, has exploded over the past few years. It not only improves your code, it's faster than releasing code without tests. You'll learn: What, exactly, is a unit test?; The 7 reasons why managers love unit testing; and how to change mindset and processes to start unit testing now.
[XP Day Vietnam 2015] XP is not windows XP
This document discusses eXtreme Programming (XP), an agile software development framework. It provides definitions and explanations of key XP practices, principles, and values. The main points are:
- XP focuses on practices like pair programming, testing, code reviews, and frequent integration that are taken "to the extreme."
- The core values of XP center on individuals, interactions, working software, customer collaboration, and responding to change.
- Key practices include sit together pairing, testing, informative workspaces, user stories, test-driven development, and more.
- Principles guide the framework and include ideas like baby steps, mutual benefit, flow, reflection, and redundancy.
Test Driven Development
This document discusses test-driven development (TDD) and unit testing. It defines TDD as a process that involves writing a failing test first, then implementing code to pass that test, and refactoring if needed. Key benefits of TDD and unit testing include reduced bugs, lower maintenance costs, and improved code design. The document provides guidelines for writing good unit tests and emphasizes that tests should be quick, isolated, and answer what behavior was tested and what the expected and actual results were.
Why pay two developers to do the work of one?
Let's explore some of the myths that you hear around XP development, and talk about why your developers should be using XP to create quality, well-crafted software.
Paul Ellarby - Why do scrum?
The document discusses several key principles of agile development including building the right thing instead of wasting time on specifications that may change, delivering value incrementally, responding to change, and building quality into the product through practices like unit testing, test-driven development, pairing, refactoring, and continuous integration. It emphasizes that customers' understanding of what they want evolves over time and that many things change along the way, so an agile approach helps teams adapt.
Agileee 2012
The document discusses reversing the "tests pyramid" approach to address technical debt in legacy code. It notes that unit testing is difficult for code without separation of concerns, but refactoring without tests is risky. It proposes starting with high-level tests to gain confidence for refactoring into units and writing unit tests incrementally. However, end-to-end tests are long to maintain, and if needed, the architecture may be flawed. Reversing the tests pyramid and refactoring code in this way takes time but pays back technical debt and allows for sustainable changes. Beware of refactoring just for its own sake - focus on removing duplication and improving changeability.
Test Driven Development
Test-driven development allows developers to find and fix bugs more quickly by writing automated tests before developing code. This reduces debugging time and improves productivity. Constant testing is crucial for short release cycles and gives developers confidence to refactor and improve code quality throughout development. Automated testing enables developers to test thoroughly without losing focus.
Improve your TDD skills
An amazing opportunity for all the coders to improve their TDD skills in a safe and thrilling environment. Our lab is a 3 hours intensive practice event, focusing on the practice of TDD, essential for software development and design, away from the pressures of ‘getting things done’.
Pair Programming: overview and concepts
Extreme Programming (XP) is an agile software development methodology that embraces change. Two key practices of XP are pair programming and testing. Pair programming involves two programmers working together at one computer, with one typing while the other reviews the work. This allows for continuous review and collaboration. Some techniques for pair programming include ping pong pairing and chess clock pairing to ensure both partners contribute equally. Pair programming improves code quality, problem solving abilities, and knowledge sharing.
The Software Craftsman (2nd edition)
The document discusses the need for "Software Craftsmen" who take pride in their work and continuously hone their skills. A Software Craftsman will choose quality over speed and takes responsibility for their work. The document outlines tips for becoming a Software Craftsman, such as learning techniques like test-driven development, practicing through code katas and dojos, and working on real projects. Software Craftsmen are needed because they avoid producing bad code through deliberate practice and skill development.
Impression from Geecon 2014
The document contains summaries from several presentations at the Geecon 2014 conference. Key topics discussed include the 7 duties of great software professionals, how to get kids started with programming in Java, mutation analysis as an alternative to code coverage, advantages of SQL over NoSQL databases, microservices architecture, and strategies for handling errors and preventing memory leaks in applications. Several Java libraries and tools are also mentioned like JUnit, Mockito, Pitest, Lombok, and SLF4J.
Agile Software Development for Non-Developers
A Crash Course Introduction into the world of Agile Software Development for people with a sparse or non-existent background in Software Development.
I held this presentation as a Brownbag session at ThoughtWorks Hamburg. The TDD part included a live coding session and the part about Continuous Integration and Continuous Delivery was backed with an example of a real Continuous Integration Server that worked on the results from the TDD live coding session.
The Software Craftsman
This document discusses the need for software craftsmen and their characterization. It defines a software craftsman as someone who chooses to "get it right" over just "getting it done", takes responsibility for their work, and is a continuous learner. It recommends ways for developers to become craftsmen, such as practicing techniques like TDD, refactoring, and contributing to the community.
The Heart Of Agile
The document discusses the heart of Agile and emphasizes that individuals and interactions are more valued than processes and tools. It provides examples of situations where valuing individuals and interactions over rigid processes and contracts led to better outcomes. Building an effective Agile team requires collective code ownership, commitment to the team over any individual, and letting go of ego to value collaboration over individual accomplishments.
Coderetreat @ CodersTUG
This document outlines an agenda for a coderetreat event. It includes:
- An introduction that describes the event organizer and purpose of learning through sharing.
- An agenda with sessions on test-driven development, extreme programming, cost of change, simple design principles, and mechanics of TDD.
- Descriptions of pair programming, test-driven development, and the Game of Life cellular automaton that will be used in exercises.
- Logistical details like session structure, pairing rotations, and expectations around deleting code between sessions.
Agile xp crash_course_2010_05_21
This document provides an overview of Agile and eXtreme Programming (XP), including the core values and principles of the Agile Manifesto, roles and practices in XP, and how to adopt and apply XP to projects. It discusses key aspects of XP like short iterations, user stories, frequent releases, test-driven development, refactoring, collective code ownership, and more. The goal is to give the reader a crash course in Agile and XP methodologies.
Test-Driven Design - ¿Porqué?
The document discusses test-driven development (TDD) and how it can be used to reduce unnecessary complexity, also known as inventory, in software design. TDD involves writing automated tests before code to articulate requirements and ensure only needed code is written. It promotes designing simple, clear code without duplication through principles like You Aren't Gonna Need It and refactoring code in small, reversible steps. Following TDD principles is claimed to reduce inventory created by excess complexity and allow designs to evolve incrementally based on test feedback.
Extreme & pair programming Slides ppt
Extreme Programming (XP) is an agile software development methodology that embraces frequent changes. It utilizes practices like pair programming, where two programmers work collaboratively at one computer. Pair programming provides benefits like continuous review to reduce defects, improved problem solving, and faster learning. However, it is criticized for being unrealistic and not business focused. Overall, agile methodologies are increasingly used over traditional "high ceremony" approaches.
The art of not being too good at the Marshmallow test
Martin Henk, Co-Founder, Head of Product Management, Pipedrive: "The art of not being too good at the Marshmallow test"
Working effectively with legacy codes
This document discusses strategies for safely changing legacy code. It introduces concepts like adding features versus fixing bugs, refactoring to improve design while preserving behavior, and optimization. The key strategies are to either carefully plan and understand the code before making changes ("edit and pray"), or to first add tests as a "safety net" before modifying code ("cover and modify"). Adding tests allows getting quick feedback on changes through regression testing and prevents bugs from spreading. Overall tests are emphasized as critical for safely refactoring and changing legacy code.
Pair programming demystified
Learn about problems of mature teams, about myths of pair programming and pair synergetic behaviors. How to implement pair programming in your company and how we did it in DaftCode.
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...MobileMonday Estonia
Taavet Tamm, Senior Dev, Fortumo: "“Startup - it’s not just an IT project” - a random sampling of problems we’ve faced so far."Tips sukses berkarir sebagai developer dan programmer 2021
Tetap kembangkan skill mu di era pandemi. Jadikan hari-harimu lebih produktif dengan asah pengetahuan dan skill di Dicoding Event. Kali ini Dicoding LIVE disponsori oleh IDCamp dengan tema "Tips Sukses Berkarir sebagai Developer dan Programmer 2021"
Developer dan programmer kini menjadi salah satu pekerjaan yang paling diminati. Jadi, tidak heran jika banyak orang yang tertarik mencoba profesi ini untuk berkarir. Sayangnya masih banyak orang berpikir bahwa bekerja menjadi developer dan programmer hanya berhubungan dengan hal-hal yang bersifat technical, padahal tidak. Banyak hal yang harus dipersiapkan dan diketahui saat ingin mulai berkarier di dunia kerja seperti tools apa yang bisa membantu produktivitas, cara berkomunikasi dengan tim, sampai problem solving masalah dalam tim. Kali ini bersama dengan Andri Suranta Ginting (Mobile Engineer, Gojek) akan kita bahas tips dari pengalaman beliau dalam berkarir sebagai developer dan programmer juga menyiapkan hal technical dan non-technical untuk dikuasai di dunia kerja.
A Test Manifesto 2014.03.26
Last year we were challenged to build an agile test team to work in different products and technologies for 8 distributed teams from 3 to 7 people. We had to break with legacy assumptions on how testing should be enacted while keeping company policies. And most of all, we had to make sure everyone is enabled to do the best possible job.
Enabling a team is about motivation, trust and simplifying decision making processes. The test team as a whole has to scale and fit for multiple scenarios and projects. Every team member had a different background and needs so no policies would really apply to all. Or worst, we would be spending time twisting the rules to fit each case.
First, we decided to coordinate as a guild. Second, we issued this Test Manifest as a declaration of purpose and discipline.
Whatmakesoftwareflexible
Whatmakesoftwareflexible - XP Day HaNoi 2015, Extreme Programming, TDD, Refactor
Remembering Bernie Copy (2)
This document is a memorial for a dog named Bernie Hanosh who passed away on August 10, 2011. It expresses love and remembrance from his family with wishes that even in death, Bernie will have all the things he enjoyed in life like walks, food, belly rubs, and naps. The family states they will always miss their beloved pet.
Remembering Bernie Copy
This document is a memorial for a dog named Bernie Hanosh who passed away on August 10, 2011. It expresses love and remembrance from Bernie's family, lists his nickname and birth/death dates, and wishes him happy walks, food, belly rubs, and naps in his afterlife while stating that he will be deeply missed.
Remembering Bernie
This document is a memorial for a dog named Bernie Hanosh who passed away on August 10, 2011. It expresses love and remembrance from Bernie's family, wishes him happy walks and full meals in his afterlife, and says they will always miss him.
More Related Content
What's hot
Test Driven Development
Test-driven development allows developers to find and fix bugs more quickly by writing automated tests before developing code. This reduces debugging time and improves productivity. Constant testing is crucial for short release cycles and gives developers confidence to refactor and improve code quality throughout development. Automated testing enables developers to test thoroughly without losing focus.
Improve your TDD skills
An amazing opportunity for all the coders to improve their TDD skills in a safe and thrilling environment. Our lab is a 3 hours intensive practice event, focusing on the practice of TDD, essential for software development and design, away from the pressures of ‘getting things done’.
Pair Programming: overview and concepts
Extreme Programming (XP) is an agile software development methodology that embraces change. Two key practices of XP are pair programming and testing. Pair programming involves two programmers working together at one computer, with one typing while the other reviews the work. This allows for continuous review and collaboration. Some techniques for pair programming include ping pong pairing and chess clock pairing to ensure both partners contribute equally. Pair programming improves code quality, problem solving abilities, and knowledge sharing.
The Software Craftsman (2nd edition)
The document discusses the need for "Software Craftsmen" who take pride in their work and continuously hone their skills. A Software Craftsman will choose quality over speed and takes responsibility for their work. The document outlines tips for becoming a Software Craftsman, such as learning techniques like test-driven development, practicing through code katas and dojos, and working on real projects. Software Craftsmen are needed because they avoid producing bad code through deliberate practice and skill development.
Impression from Geecon 2014
The document contains summaries from several presentations at the Geecon 2014 conference. Key topics discussed include the 7 duties of great software professionals, how to get kids started with programming in Java, mutation analysis as an alternative to code coverage, advantages of SQL over NoSQL databases, microservices architecture, and strategies for handling errors and preventing memory leaks in applications. Several Java libraries and tools are also mentioned like JUnit, Mockito, Pitest, Lombok, and SLF4J.
Agile Software Development for Non-Developers
A Crash Course Introduction into the world of Agile Software Development for people with a sparse or non-existent background in Software Development.
I held this presentation as a Brownbag session at ThoughtWorks Hamburg. The TDD part included a live coding session and the part about Continuous Integration and Continuous Delivery was backed with an example of a real Continuous Integration Server that worked on the results from the TDD live coding session.
The Software Craftsman
This document discusses the need for software craftsmen and their characterization. It defines a software craftsman as someone who chooses to "get it right" over just "getting it done", takes responsibility for their work, and is a continuous learner. It recommends ways for developers to become craftsmen, such as practicing techniques like TDD, refactoring, and contributing to the community.
The Heart Of Agile
The document discusses the heart of Agile and emphasizes that individuals and interactions are more valued than processes and tools. It provides examples of situations where valuing individuals and interactions over rigid processes and contracts led to better outcomes. Building an effective Agile team requires collective code ownership, commitment to the team over any individual, and letting go of ego to value collaboration over individual accomplishments.
Coderetreat @ CodersTUG
This document outlines an agenda for a coderetreat event. It includes:
- An introduction that describes the event organizer and purpose of learning through sharing.
- An agenda with sessions on test-driven development, extreme programming, cost of change, simple design principles, and mechanics of TDD.
- Descriptions of pair programming, test-driven development, and the Game of Life cellular automaton that will be used in exercises.
- Logistical details like session structure, pairing rotations, and expectations around deleting code between sessions.
Agile xp crash_course_2010_05_21
This document provides an overview of Agile and eXtreme Programming (XP), including the core values and principles of the Agile Manifesto, roles and practices in XP, and how to adopt and apply XP to projects. It discusses key aspects of XP like short iterations, user stories, frequent releases, test-driven development, refactoring, collective code ownership, and more. The goal is to give the reader a crash course in Agile and XP methodologies.
Test-Driven Design - ¿Porqué?
The document discusses test-driven development (TDD) and how it can be used to reduce unnecessary complexity, also known as inventory, in software design. TDD involves writing automated tests before code to articulate requirements and ensure only needed code is written. It promotes designing simple, clear code without duplication through principles like You Aren't Gonna Need It and refactoring code in small, reversible steps. Following TDD principles is claimed to reduce inventory created by excess complexity and allow designs to evolve incrementally based on test feedback.
Extreme & pair programming Slides ppt
Extreme Programming (XP) is an agile software development methodology that embraces frequent changes. It utilizes practices like pair programming, where two programmers work collaboratively at one computer. Pair programming provides benefits like continuous review to reduce defects, improved problem solving, and faster learning. However, it is criticized for being unrealistic and not business focused. Overall, agile methodologies are increasingly used over traditional "high ceremony" approaches.
The art of not being too good at the Marshmallow test
Martin Henk, Co-Founder, Head of Product Management, Pipedrive: "The art of not being too good at the Marshmallow test"
Working effectively with legacy codes
This document discusses strategies for safely changing legacy code. It introduces concepts like adding features versus fixing bugs, refactoring to improve design while preserving behavior, and optimization. The key strategies are to either carefully plan and understand the code before making changes ("edit and pray"), or to first add tests as a "safety net" before modifying code ("cover and modify"). Adding tests allows getting quick feedback on changes through regression testing and prevents bugs from spreading. Overall tests are emphasized as critical for safely refactoring and changing legacy code.
Pair programming demystified
Learn about problems of mature teams, about myths of pair programming and pair synergetic behaviors. How to implement pair programming in your company and how we did it in DaftCode.
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...MobileMonday Estonia
Taavet Tamm, Senior Dev, Fortumo: "“Startup - it’s not just an IT project” - a random sampling of problems we’ve faced so far."Tips sukses berkarir sebagai developer dan programmer 2021
Tetap kembangkan skill mu di era pandemi. Jadikan hari-harimu lebih produktif dengan asah pengetahuan dan skill di Dicoding Event. Kali ini Dicoding LIVE disponsori oleh IDCamp dengan tema "Tips Sukses Berkarir sebagai Developer dan Programmer 2021"
Developer dan programmer kini menjadi salah satu pekerjaan yang paling diminati. Jadi, tidak heran jika banyak orang yang tertarik mencoba profesi ini untuk berkarir. Sayangnya masih banyak orang berpikir bahwa bekerja menjadi developer dan programmer hanya berhubungan dengan hal-hal yang bersifat technical, padahal tidak. Banyak hal yang harus dipersiapkan dan diketahui saat ingin mulai berkarier di dunia kerja seperti tools apa yang bisa membantu produktivitas, cara berkomunikasi dengan tim, sampai problem solving masalah dalam tim. Kali ini bersama dengan Andri Suranta Ginting (Mobile Engineer, Gojek) akan kita bahas tips dari pengalaman beliau dalam berkarir sebagai developer dan programmer juga menyiapkan hal technical dan non-technical untuk dikuasai di dunia kerja.
A Test Manifesto 2014.03.26
Last year we were challenged to build an agile test team to work in different products and technologies for 8 distributed teams from 3 to 7 people. We had to break with legacy assumptions on how testing should be enacted while keeping company policies. And most of all, we had to make sure everyone is enabled to do the best possible job.
Enabling a team is about motivation, trust and simplifying decision making processes. The test team as a whole has to scale and fit for multiple scenarios and projects. Every team member had a different background and needs so no policies would really apply to all. Or worst, we would be spending time twisting the rules to fit each case.
First, we decided to coordinate as a guild. Second, we issued this Test Manifest as a declaration of purpose and discipline.
What's hot (18)
The art of not being too good at the Marshmallow test
The art of not being too good at the Marshmallow test
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...
“Startup - it’s not just an IT project” - a random sampling of problems we’ve...
Tips sukses berkarir sebagai developer dan programmer 2021
Tips sukses berkarir sebagai developer dan programmer 2021
Viewers also liked
Whatmakesoftwareflexible
Whatmakesoftwareflexible - XP Day HaNoi 2015, Extreme Programming, TDD, Refactor
Remembering Bernie Copy (2)
This document is a memorial for a dog named Bernie Hanosh who passed away on August 10, 2011. It expresses love and remembrance from his family with wishes that even in death, Bernie will have all the things he enjoyed in life like walks, food, belly rubs, and naps. The family states they will always miss their beloved pet.
Remembering Bernie Copy
This document is a memorial for a dog named Bernie Hanosh who passed away on August 10, 2011. It expresses love and remembrance from Bernie's family, lists his nickname and birth/death dates, and wishes him happy walks, food, belly rubs, and naps in his afterlife while stating that he will be deeply missed.
Remembering Bernie
This document is a memorial for a dog named Bernie Hanosh who passed away on August 10, 2011. It expresses love and remembrance from Bernie's family, wishes him happy walks and full meals in his afterlife, and says they will always miss him.
LinkedIn features guide
LinkedIn is a business-oriented social networking site mainly used for professional networking with over 65 million registered users worldwide. It allows users to connect with colleagues and professionals, find potential business partners and clients, and learn about companies. LinkedIn can help users expand their professional network, get discovered by recruiters, promote their business, and stay updated with industry news and connections.
Xp not windows xp
This document discusses eXtreme Programming (XP), an agile software development framework. It provides definitions and explanations of key XP practices, principles, and values. The main points are:
- XP focuses on practices like pair programming, testing, code reviews, and frequent integration that are taken "to the extreme."
- The core values of XP center on individuals, interactions, working software, customer collaboration, and responding to change.
- Key practices include sit together pairing, testing, informative workspaces, user stories, test-driven development, and more.
- Principles guide the framework and include concepts like baby steps, mutual benefit, flow, reflection, and redundancy.
Visual studio 2015 ide new features
Visual studio 2015 ide new features. Meetup chia sẻ về những tính năng mới của Visual Studio 2015
HaNoi Net Group Introduction
HaNoi Net Group Introduction - let's share to be shared.
Community for all developers to: join and learn, do and share
Agile .NET Development with BDD and Continuous Integration
Agile .NET Development with BDD and Continuous Integration
Áp dụng CI là một phần không thể thiếu nếu bạn mong muốn nâng cao năng suất và giảm thiểu lỗi lầm khi phát triển cũng như deploy sản phẩm qua việc sử dụng các practices và tools để tự động hóa các khâu
Bài trình bày của anh Trương Anh Quân tại Meetup của Ha Noi .NET Group.
Chi tiết vui lòng xem tại: http://tungnt.net
Continuous Delivery with VS2015 and TFS2015
Continuous Integration - Continuous Delivery (CI-CD) with Visual Studio 2015 and Team Foundation Server 2015
1) CI/CD Introduction: CI/CD Advantages; CI/CD Practices
2) CI/CD with VS2015&TFS2015
3) Continuos Inspection with SonarQube
SignalR with ASP.NET MVC 6
Deep diving SignalR with ASP.NET MVC 6.
Speaker: Mr Sherman Chen - Telerik Senior Architect/Advocate with more than 15 years developing desktop, web and mobile apps
Docker for .net developer
Docker for .net developer, Container, Hyper-V, Docker Tool for VS, Windows Container, Images, Layer, Docker architecture, What is Docker, Docker Engine
Viewers also liked (15)
Agile .NET Development with BDD and Continuous Integration
Agile .NET Development with BDD and Continuous Integration
Similar to Workshop fight legacy code write unit test
How I Learned to Stop Worrying and Love Legacy Code.....
Legacy Code. I never wrote it; everybody else did!
How many times have you waded through an ageing, decaying, tangled forrest of code and wished it would just die?
How many times have you heard someone say that what really needs to happen is a complete rewrite?
I have heard this many times, and, have uttered that fatal sentence myself.
But shouldn’t we love our legacy code?
Doesn’t it represent our investment and the hard work of ourselves and our predecessors?
Throwing it away is dangerous, because, before we do, we’ll need to work out exactly what it does, and we’ll need to tweeze out that critical business logic nestled in a deeply entangled knot of IF statements. It could take us years to do, and we’ll have to maintain two systems whilst we do it, inevitably adding new features to them both. Yes we get to reimplement using the latest, coolest programming language, instead of an old behemoth, but how long will our new cool language be around, and who will maintain that code, when it itself inevitably turns to legacy?
We can throw our arms in the air, complaining and grumbling about how we didn’t write the code, how we would never have written it the way it is, how those that wrote it were lesser programmers, possibly lesser humans themselves, but the code still remains, staring us in the face and hanging around for longer that we could possibly imagine. We can sort it out, we can improve it, we can make it testable, and we can learn to love our legacy code.
Software Quality via Unit Testing
Software quality is critical to consistently and continually delivering new features to our users. This talk covers the importance of software quality and how to deliver it via unit testing, Test Driven Development and clean code in general.
This is the deck from a talk I gave at Desert Code Camp 2013.
How to write good quality code
I was invited to the Coder Factory to give a brief introduction to writing code that is scalable, shareable and usable.
Should you be your own judge?
It is one of the famous excuses for developer not writing unit test.
Presented in KTM JS, here I have discussed on what other benefits dev can achieve from unit test apart from problem findings.
Tdd
This document discusses test driven development (TDD). It begins by explaining the basic TDD process of writing a failing test, getting it to compile, making it pass without changing existing code, and then refactoring. It outlines some benefits of TDD like improved code quality and confidence in changes. It also notes some challenges like additional overhead and keeping test code clean. Overall, it argues that while TDD requires proper implementation, it can help produce higher quality code with fewer bugs.
The View - Lotusscript coding best practices
This document discusses best practices for LotusScript coding. It covers topics like code structure, using short logical functions, defensive programming, variable naming conventions, and ensuring variables only exist as long as needed. The goal is to write code that is maintainable, reusable, and robust. Testing practices like test-driven development and separating development, testing, and production environments are also recommended to improve quality.
How to write bad code using C#
There has been lots of talk on the importance of writing good and manageable code – code whose inherent beauty bring tears to the eyes of the developer that looks at it. This talk is not like that. This talk will focus on the techniques that are used by millions across the world to bring tears to the eyes of the maintaining developer, as well as a graphic stream of profanities.We will investigate some of the most common anti-patterns and half-measures that occur in real live code, and will marvel at the ingenuity and outright creativity necessary to create ugly messes of unmaintainable code that still manages to work for it’s users.
Managing and evolving JavaScript Code
If your project has working features, a living design system, quality assurance and a code style guide, there is nothing that you will learn in this talk. Maybe.
Test-Driven Development Reference Card
This document discusses Test-Driven Development (TDD). It defines TDD as writing unit tests before writing any production code. TDD helps ensure code is consistently refactored for better design. The document outlines the TDD process of writing a test, seeing it fail, writing code to pass the test, then refactoring. It discusses using TDD with legacy code by refactoring code to be testable. Sample unit tests are provided to demonstrate testing default constructor values. Benefits of TDD include better code design, earlier defect detection, and fewer defects in production releases.
Agile & Test Driven Development: The Ampersand Commerce Approach
A presentation to University of Manchester Computer Science graduates about how Ampersand Commerce approaches Agile and Test Driven Development. Also, information about our graduate programme for software engineers
Developer Job in Practice
The document provides guidance for developers on best practices for writing code. It emphasizes following rules like clean code, code reviews, and refactoring. Key points include writing simple and readable code, avoiding duplication, learning from others, and ensuring code meets definitions of done that specify requirements like testing and code quality. Refactoring is advised to reduce technical debt by improving structure without changing functionality. Code reviews are recommended to catch defects through constructive peer review.
How to quickly add a safety net to a legacy codebase
Did you ever inherited a horrible legacy system to maintain and you were scared to introduce bugs touching it? If you did (who never did?) then this post is for you.
You can find the accompanying video and blogpost soon on
Integreation
Slides from a quick and dirty presentation I gave to colleagues on Continuous Integration, Unit / Spec testing, etc.
CREDIT: this is very much in the Zach Holman school of presentation. I borrowed a lot of inspiration (and some colors/fonts) from his designs. Attribution was given.
Test Driven Development - Workshop
Test Driven Development (TDD) is a software development process that relies on the repetition of a very short development cycle: requirements are turned into very specific test cases that are failed, then the software is improved to pass the new tests, and finally any newly introduced code is refactored. The document outlines the TDD lifecycle and process, describes unit testing and how it verifies isolated units of code, and discusses how TDD results in testable, clean code through refactoring. It provides examples of unit testing code for a bank account class.
TDD - Cultivating a Beginner's Mind
The document discusses how test-driven development (TDD) can help software developers avoid design mistakes that stem from relying too heavily on past experience. It notes that experience can make developers vulnerable by leading them to automatically apply familiar patterns without considering if they are the best solution. TDD encourages an incremental "beginner's mind" approach where the simplest code is written to pass each test before refactoring, which helps developers introduce the right abstractions and avoid over-engineering. Refactoring is key to improving designs emerging from TDD. The document advocates practicing TDD and refactoring to cultivate humility and flexibility in design.
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Big Ball of Mud (BBoM) architectures are viewed as the culmination of many design decisions that, over time, result in a system that is hodgepodge of steaming and smelly anti-patterns. It can be arguably claimed that one of the reasons for the growth and popularity of agile practices is partially due to the fact that the state of the art of software architectures was not that good. Being agile, with its focus on extensive testing and frequent integration, has shown that it can make it easier to deal with evolving architectures (possibly muddy) and keeping systems working while making significant improvements and adding functionality. Time has also shown that Agile practices are not sufficient to prevent or eliminate Mud. It is important to recognize what is core to the architecture and the problem at hand when evolving an architecture.
This talk will examine the paradoxes that underlie Big Balls of Mud, what causes them, and why they are so prominent. I’ll explore what agile practices can help us avoid or cope with mud. I’ll also explain why continuous delivery and TDD with refactoring is not enough to help ensure clean architecture and why it is important to understand what is core to the architecture and the problem at hand. Understanding what changes in the system and at what rates can help you prevent becoming mired in mud. By first understanding where a system’s complexities are and where it keeps getting worse, we can then work hard (and more intelligently) at sustaining the architecture. This can become a key value to the agile team. The results will leave attendees with practices and patterns that help clean your code (refactor) as well as keeping the code clean or from getting muddier.
Additionally, I’ll talk about some practices and patterns that help keep the code clean or from getting muddier. Some of these include: Testing, Divide & Conquer, Gentrification, Demolition, Quarantine, Refactoring, Craftmanship and the like.. The original Big Ball of Mud paper described some best practices such as SHEARING LAYERS and SWEEPING IT UNDER THE RUG as a way to help deal with muddy architectures. Additionally there are some other practices such as PAVING OVER THE WAGON TRAIL and WIPING YOUR FEET AT THE DOOR that can make code more habitable.
10 Big Ideas from Industry
Advice on structured software development for academics. Presented to Maths and Physics PhD students and researchers at Queens University Belfast.
eXtreme Programming
How to succeed in software development. Following agile methodology principles helps to achieve much better results. Know more about eXtreme Programming, one of the famous agile software development methodology.
20191116 DevFest 2019 The Legacy Code came to stay (El legacy vino para queda...
20191116 DevFest 2019 The Legacy Code came to stay (El legacy vino para queda...Antonio de la Torre Fernández
Talk given in DevFest Asturias 2019 (GDG Google Developer Group Asturias)
16.11.2019 Gijón (Spain)
The Legacy Code came to stay
(spanish)
El legacy vino para quedarse
RESUMEN
Es una charla que pone en relieve que los servicios que damos los agilistas, no están orientados a sustituir el trabajo de otros, sino que entre todos conseguimos mejorar nuestros productos y nuestra vida diaria en el trabajo.
ABSTRACT
Casi todos sabemos lo que es el Legacy Code, ese proyecto al que todos nos hemos enfrentado alguna vez y que cuesta trabajar con él.
Lo que era algo a evitar o a sustituir, en los últimos años por diversas razones, se ha convertido en algo que debe seguir existiendo durante mucho tiempo, por lo que se busca la manera de seguir manteniendolo con confianza.
Esta necesidad parece técnica, y a lo sumo se entiende que involucra a los equipos que lo mantienen, pero realmente es una estrategia empresarial en la que se busca además de mantener la funcionalidad existente, avanzar el producto y cubrir la necesidad actual, con la ayuda de un equipo al que hay que mantener motivado, practicando además, eso tan difícil que hoy se conoce como La Retención del Talento.
Explicaremos en esta charla los diferentes tipos de retos enmarcados en Código Legado, tantos técnicos como con los equipos a los que nos hemos enfrentado en Codesai y qué estrategias usamos para afrontarlos.
Arch factory - Agile Design: Best Practices
This document provides guidance on agile architecture and design principles. It emphasizes that agile design is about responding quickly to change for customers and teams through transparency, lightweight processes, and continuous learning. Key principles discussed include designing incrementally without large upfront design; getting early and continuous feedback; delaying commitment and complexity; and maximizing evolutionary design through reversibility and packaging. The document also covers topics like testing, distributed teams, and delivering frequently.
Similar to Workshop fight legacy code write unit test (20)
How I Learned to Stop Worrying and Love Legacy Code.....
How I Learned to Stop Worrying and Love Legacy Code.....
Agile & Test Driven Development: The Ampersand Commerce Approach
Agile & Test Driven Development: The Ampersand Commerce Approach
How to quickly add a safety net to a legacy codebase
How to quickly add a safety net to a legacy codebase
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work
20191116 DevFest 2019 The Legacy Code came to stay (El legacy vino para queda...
20191116 DevFest 2019 The Legacy Code came to stay (El legacy vino para queda...
More from Tung Nguyen Thanh
How to become senior .net developer
How to become senior .net developer, .net interview question ,.net framework ,tdd ,unit test ,ci/cd ,ddd ,cqrs-es, clean code, solid
Domain Driven Design Introduction
Domain Driven Design Introduction
1) Giới thiệu DDD
2) Domain Model trong DDD
3) DDD patterns: Repository, Aggregate, Factory
4) Demo và tài liệu tham khảo
Performance Tuning And Optimization Microsoft SQL Database
Performance Tuning And Optimization Microsoft SQL Database
Performance issues, administrative optimization, logical optimization, architecture, coding, design, index, execution plan, monitoring and maintenance plan
Software architecture for high traffic website
Kiến trúc phần mềm cho các site chịu tải lớn – Software architecture for high traffic Website
Case study giới thiệu về kiến trúc của một site traffic lớn đó là stackoverflow.com - trang hỏi đáp về lập trình rất nổi tiếng
Bài trình bày của bạn Ngô Xuân Hòa tại Meetup 4 của Ha Noi .NET Group.
Chi tiết vui lòng xem tại: http://tungnt.net
TDD - Test Driven Development
Test Driven Development - Phương pháp phát triển phần mềm theo hướng viết test trước.
Áp dụng TDD sẽ đem lại cho bạn thiết kế phần mềm trong sáng hơn và quản lý được chất lượng từng dòng code của mình viết ra.
Bài trình bày của bạn Lê Anh tại Meetup của Ha Noi .NET Group.
Chi tiết vui lòng xem tại: http://tungnt.net
Refactoring code in .net
Refactoring code in .net - Các kĩ thuật Refactoring code trong .NET. Đây là một kỹ thuật không thể thiếu nếu các bạn muốn các dòng code của mình ngày một trong sáng, dễ hiểu hơn, clean hơn. Đặc biệt đây là một kỹ thuật không thể thiếu nếu bạn muốn áp dụng Agile/Extreme Programming với Unit Test.
http://tungnt.net/meetup-ve-cac-ky-thuat-refactoring-code-trong-net/
How to release every week case study of continuous integration
With a legacy system, the team releases weekly by having 70% unit test coverage and 1500 acceptance tests using Robot Framework, with testing via regression flows and keeping delta technical debts to 5 days or fewer while avoiding critical issues through practices like test-driven development and pairing/mobbing as feasible given the legacy code base.
Is xp still extreme
KeyNote - Is XP still Extreme? Kiro Harada. HaNoi XP Day 2015. TDD, Refactor, Simple Design, Pair Programming
Windows Phone Introduction
Giới thiệu lập trình trên nền tảng Windows Phone
- Design
- Market share
- Application Type
- Development Tool
- Features
- Application LifeCycle
Developing windows phone 7 application with silverlight
This document discusses building Windows Phone applications with Silverlight. It begins with an introduction to Windows Phone 7 and outlines the Silverlight and XNA frameworks. It then focuses on developing Windows Phone 7 applications with Silverlight. Key points covered include navigation controls, push notifications, application lifecycles, and using maps, pivots and panoramas. The presentation concludes with a demo of creating a basic "Hello World" application in the simulator and exploring additional Windows Phone 7 features and services.
Top 100 .NET Interview Questions and Answers
Top 100 câu hỏi phỏng vấn về .NET Framework dành cho lập trình viên. Top 100 .NET Interview Questions and Answers
New in Visual Studio and TFS 2013
This document summarizes new features in Visual Studio 2013 and Team Foundation Server 2013. It discusses improvements to the XAML editor, debugging experience, and Team Explorer. New features include signing into Visual Studio, notifications center, code lenses, peek definition, and enhancements for ASP.NET, web development, and TypeScript. New capabilities in TFS 2013 include portfolio backlogs, tags, team rooms, charts, support for Git, and web-based code review. The document concludes with a brief look at future releases and capabilities like Windows Azure Workstation.
Visual studio2012 tipsandtricks
This document provides tips and shortcuts for using Microsoft Visual Studio 2012. It describes features like named code regions, drag and drop code blocks, IntelliSense code completion, searching and syncing code, analyzing code clones, navigating to definitions, surrounding code with structures, and more. It also outlines basic object-oriented programming concepts like auto-implemented properties, method naming conventions, and the default methods on the object class.
UI prototyping with ms expression blend sketch flow
The document discusses using Expression Blend and SketchFlow for UI prototyping. It describes how SketchFlow allows creating interactive prototypes quickly using hand-drawn sketches to get early stakeholder feedback, before significant coding work is done. This helps validate requirements and avoid redesign work later on. The document outlines SketchFlow's features like drag-and-drop interfaces, customizable controls and styles, and the ability to package prototypes for comment. It stresses aligning a prototype with user requirements and business goals.
More from Tung Nguyen Thanh (14)
Performance Tuning And Optimization Microsoft SQL Database
Performance Tuning And Optimization Microsoft SQL Database
How to release every week case study of continuous integration
How to release every week case study of continuous integration
Developing windows phone 7 application with silverlight
Developing windows phone 7 application with silverlight
UI prototyping with ms expression blend sketch flow
UI prototyping with ms expression blend sketch flow
Recently uploaded
GNSS spoofing via SDR (Criptored Talks 2024)
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
AppSec PNW: Android and iOS Application Security with MobSF
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...Pitangent Analytics & Technology Solutions Pvt. Ltd
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
Dandelion Hashtable: beyond billion requests per second on a commodity server
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Mutation Testing for Task-Oriented Chatbots
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
"Choosing proper type of scaling", Olena Syrota
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Artificial Intelligence and Electronic Warfare
Artificial Intelligence and Electronic WarfarePapadakis K.-Cyber-Information Warfare Analyst & Cyber Defense/Security Consultant-Hellenic MoD
AI & Electronic WarfarezkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Dmitrii Kamaev, PhD
Senior Product Owner - QIAGEN
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Gursev Pirge, PhD
Senior Data Scientist - JohnSnowLabs
Recently uploaded (20)
AppSec PNW: Android and iOS Application Security with MobSF
AppSec PNW: Android and iOS Application Security with MobSF
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Workshop fight legacy code write unit test
- 1. www.odd-e.com Fight Legacy Code! Write Unit Test! Stanly Lau
- 2. 2 I’m Stanly • Lives in Singapore! • Agile coach, SW developer! • Worked in small to large companies! • Experienced in Insurance, Mobile Safety, Education, Logistics and Banking! • Java, .Net, JavaScript, Objective-C stanly@odd-e.com
- 5. 5 What is Legacy Code?! ! The Problem! ! How to deal with it?
- 6. 6
- 7. What is legacy code? 7
- 8. Legacy Code is! Code without Unit Test 8 Michael Feathers
- 9. 9 It is not a unit test when: • It talks to the database! • It communicates across the network! • It touches the file system! • It can't run at the same time as any of your other unit tests! • You have to do special things to your environment (such as editing config files) to run it. Michael Feathers
- 10. The problem 10
- 12. 14 Code tends to grow
- 13. 15 amount of bad code panic amount of code smells time spend on bug fixing motivation developers quick hacks opportunity for # of bugs indicates O refactoring O
- 14. 16 Existing Behaviour New This is where we spent most time on,! preserving behaviour! Codebase
- 15. 17 Productive Working duration in a day Does your day looks like this?
- 16. 18 Productive =( Don’t know why the ‘if’ doesn’t work
- 17. 19 Productive =( Stuck on understanding what the code is doing
- 18. 20 Productive =( Stuck on thinking of a general solution to solve multiple problems
- 19. 21 Productive =( Realised you misunderstood the requirements
- 21. 23 Features Estimates Business Developers Competitive dynamic Limits everyone’s perspectives
- 22. 24 James Grenning “Software change is part of being a developer, so you better get used to it. ! Even more, you better get good at it!”
- 23. How to deal with it? 25
- 25. 27 Test-driven development •Increments of functionality! •Always in working state Code and fix •Large functionalities! •Long time to get to a working statef t
- 26. The Legacy Code Dilemma 30 When we change code, we should have tests in place. To put tests in place, we often have to change code.
- 27. But I don't understand the code well enough to change It =( 31 Scratch Refactoring Notes/Sketching Delete Unused Code
- 28. Legacy code algorithm 32 1. Identify change point! 2. Find test points! 3. Break dependencies! 4. Write tests! 5. Make changes and refactor
- 30. Are we going faster? 34 Feels faster Feels slower
- 31. 35 Kent Beck “I'm not a great programmer;! I'm just a good programmer with great habits”
- 32. Closing 36
- 33. Books - Technical Practices 37
- 34. 38 @avernois