Search microservice
•
1 like•130 views
This document summarizes a discussion about moving a search functionality to a service at a company called GYG. It outlines the current search capabilities, considerations for the software architecture and infrastructure, and an iterative approach to implementing the first use cases. The goals are to enable more engineers to work in parallel, evolve search independently of other code, and build momentum for additional use cases in the next quarter. Principles discussed include keeping the initial implementation simple, delaying decisions, embracing change, and allowing the architecture to scale with complexity rather than planning for all possible features upfront. Feedback is requested to help the team learn.
Report
Share
Report
Share
Download to read offline
Recommended
Android Devops : Master Continuous Integration and Delivery
Learn how to Master Continuous integration and delivery for Android Development using Gitlab CI, Fastlane, Gradle , fabric beta and google play
Extreme Programming
Introduction to the fundamentals of eXtreme programming (XP). XP is a software development approach which stresses on improving software quality and respond according to changing business requirements.
Java Code Quality Improvements - DevWeek
This document discusses code quality improvements made to the Client Engagement Platform. The challenges included stabilizing the risk and commercial engine, integrating continuous integration with Azure DevOps, and complying with various policies. The approach taken was to increase engine stability through automated testing, and increase quality using QA tools and continuous integration. QA tools used included CheckStyle, PMD, SpotBugs, and SonarQube. Lessons learned included not treating any tool as a silver bullet, focusing on the highest impact issues using the 80/20 rule, and creating unit tests for new code.
Agility - Part 1 of 2
The document discusses the principles of agile software development, emphasizing individuals and interactions, working software, customer collaboration, and responding to change over strict plans. It describes iterations as fixed time periods for measuring results, course correcting, and failing fast. Iteration 0 involves technical setup, and subsequent iterations involve daily standups, testing, pair programming, and retrospectives at the end to demo work and track velocity and progress.
(Agile) engineering best practices - What every project manager should know
Non technical guide to engineering best practices. Should be applied on IT projects, regardless of Agile or not.
Xp exterme-programming-model
Extreme Programming (XP) is a software development methodology intended to improve quality and responsiveness to changing requirements. It involves 5 activities - planning, managing, designing, coding, and testing. Planning includes writing user stories, release planning, and frequent small releases. Managing involves dedicated workspace, stand-up meetings, and measuring velocity. Design focuses on simplicity, metaphors, CRC cards, and refactoring. Coding uses pair programming, tests first, and integration testing. All code must have unit tests that pass before release.
Page Objects - You're Doing it Wrong by Titus Fortner
Page Objects are the most commonly used abstraction pattern for functional UI Tests. They have the ability to enable users with little Selenium knowledge to write sophisticated tests against an application at scale, while reducing the maintenance costs as the application changes. Based on Sauce Labs Solution Architect code reviews, though, it is one of the most poorly understood and abused tools in a team’s framework. As an SDET at 5 companies before joining Sauce Labs, Titus has tried a number of different approaches and knows first-hand what works well and what can cause problems. Experienced people will have disagreements with many of the points he outlines, and he presents both sides along with the reasons for his preferences.
ACCENTURE - PERIOD OF EMPLOYMENT
John Doe worked as a Software Engineer Sr. Analyst for Accenture Philippines from February 2011 to July 2014. He held several roles on projects for major banks in the UK and Mexico, including project coordinator, development support, and senior programmer. In his roles, he planned resources, ensured on-time delivery, reviewed designs, performed code reviews, created tools to automate processes, answered testing queries, resolved issues, translated designs into code, and created documentation. He was also an SME for the Altamira CICS product and conducted training sessions for peers.
Recommended
Android Devops : Master Continuous Integration and Delivery
Learn how to Master Continuous integration and delivery for Android Development using Gitlab CI, Fastlane, Gradle , fabric beta and google play
Extreme Programming
Introduction to the fundamentals of eXtreme programming (XP). XP is a software development approach which stresses on improving software quality and respond according to changing business requirements.
Java Code Quality Improvements - DevWeek
This document discusses code quality improvements made to the Client Engagement Platform. The challenges included stabilizing the risk and commercial engine, integrating continuous integration with Azure DevOps, and complying with various policies. The approach taken was to increase engine stability through automated testing, and increase quality using QA tools and continuous integration. QA tools used included CheckStyle, PMD, SpotBugs, and SonarQube. Lessons learned included not treating any tool as a silver bullet, focusing on the highest impact issues using the 80/20 rule, and creating unit tests for new code.
Agility - Part 1 of 2
The document discusses the principles of agile software development, emphasizing individuals and interactions, working software, customer collaboration, and responding to change over strict plans. It describes iterations as fixed time periods for measuring results, course correcting, and failing fast. Iteration 0 involves technical setup, and subsequent iterations involve daily standups, testing, pair programming, and retrospectives at the end to demo work and track velocity and progress.
(Agile) engineering best practices - What every project manager should know
Non technical guide to engineering best practices. Should be applied on IT projects, regardless of Agile or not.
Xp exterme-programming-model
Extreme Programming (XP) is a software development methodology intended to improve quality and responsiveness to changing requirements. It involves 5 activities - planning, managing, designing, coding, and testing. Planning includes writing user stories, release planning, and frequent small releases. Managing involves dedicated workspace, stand-up meetings, and measuring velocity. Design focuses on simplicity, metaphors, CRC cards, and refactoring. Coding uses pair programming, tests first, and integration testing. All code must have unit tests that pass before release.
Page Objects - You're Doing it Wrong by Titus Fortner
Page Objects are the most commonly used abstraction pattern for functional UI Tests. They have the ability to enable users with little Selenium knowledge to write sophisticated tests against an application at scale, while reducing the maintenance costs as the application changes. Based on Sauce Labs Solution Architect code reviews, though, it is one of the most poorly understood and abused tools in a team’s framework. As an SDET at 5 companies before joining Sauce Labs, Titus has tried a number of different approaches and knows first-hand what works well and what can cause problems. Experienced people will have disagreements with many of the points he outlines, and he presents both sides along with the reasons for his preferences.
ACCENTURE - PERIOD OF EMPLOYMENT
John Doe worked as a Software Engineer Sr. Analyst for Accenture Philippines from February 2011 to July 2014. He held several roles on projects for major banks in the UK and Mexico, including project coordinator, development support, and senior programmer. In his roles, he planned resources, ensured on-time delivery, reviewed designs, performed code reviews, created tools to automate processes, answered testing queries, resolved issues, translated designs into code, and created documentation. He was also an SME for the Altamira CICS product and conducted training sessions for peers.
Test Driven Development
TDD
TAD
Why TDD
Test Driven Development
Issues without unit tests
Benefits of writing unit tests
Agile engineering practices – a short overview
This document provides a short overview of agile engineering practices, including Scrum, XP, Kanban, FDD, and DSDM. It summarizes key practices such as pair programming, test-driven development, behavior driven development, acceptance testing, exploratory testing, polyglot programming, domain specific languages, continuous integration, continuous testing, static code checking, agile databases, lightweight domain modeling, and continuous delivery. Each practice is briefly described in one slide with information on feedback time, styles, and challenges.
Extreme programming - a quick and agile overview !
Tried putting things in the deck that I learnt about Extreme programming in XP Conference held in Bangalore. I have tried to keep it at very high level added with light moments, so that it doesn't getting boring and makes sense for most of us
Tdd and bdd
a brief introduction to Test Driven Development and Behavior Driven Development and the main differences between both.
TDD and Unit Testing in Golang
Test-driven development (TDD) is a process where test cases are created to validate requirements before functional code is written. The primary goals of TDD are to help specify requirements and design and to produce clean, bug-free code through a short development cycle of writing tests then code to pass those tests. Good unit tests for TDD should run fast, isolate dependencies, clearly define their scope, not require special setup, and clearly indicate their intention. In Golang, the testing package and go test command provide tools for writing and running tests, and go test can measure test coverage.
Tech talks #1- Unit testing and TDD
The document discusses unit testing and test-driven development (TDD). It introduces unit testing and TDD, explaining their benefits and how they can improve quality. It also provides an overview of JUnit for unit testing in Java and the red-green-blue process for TDD. The document concludes with a live demo of TDD and suggestions for implementing TDD and acceptance test-driven development.
Agile versus waterfall
This document compares and contrasts the Waterfall and Agile project management methodologies. It outlines the key differences between the two approaches, such as Waterfall being rigid and inflexible while Agile is iterative and flexible. It also discusses how they have similar elements like planning and tracking progress. The document notes that while Waterfall is best for long-term, stable projects, Agile has grown in popularity for its ability to adapt to changes. It concludes that a hybrid approach combining aspects of both methodologies can work best depending on the specific project's needs.
Introduction To Extreme Programming
Extreme Programming (XP) is an agile software development methodology that focuses on rapid software development and frequent delivery of working software. It emphasizes customer collaboration, small releases, and frequent testing. Key practices of XP include writing tests first, continuous integration, pair programming, and customer involvement.
Agile model in software testing
The agile model is an incremental software development model where testing is done after each release to ensure software quality. It allows for changes to be implemented at low cost by rolling back work done in previous sprints. Some advantages are flexibility to changing requirements, ability to incorporate last minute changes, and satisfied customers through iterative releases. Communication between developers and customers is emphasized over process. Potential disadvantages include lack of documentation and difficulty estimating efforts for large projects initially.
Agile code quality metrics
The document discusses various code quality metrics that can be used to understand software quality, including defects density, unit test density, code and test coverage, cyclomatic complexity, fan-in and fan-out, and WTFs per minute. While metrics can help identify issues, they cannot determine the precise cause. Metrics should be used carefully to avoid incentivizing behaviors like hiding bugs. Maintaining pride in craftsmanship is important for quality.
Infopulse: How we do Scrum
The document discusses an agile software development process and challenges. It mentions experience with J2EE 1.4, UML, MDA, Flex3 and ViewXP technologies. The company is seeking investors and uses Scrum methodology with 15 hour tasks, 30 minute standups, failed demos, late team members, story points, planning poker, and velocity metrics for estimation. Builds and testing are also mentioned.
TestIstanbul 2017 Keynote: "Characteristics Of A Modern Test Process" by Jan ...
TestIstanbul 2017 Keynote: "Characteristics Of A Modern Test Process" by Jan ...Turkish Testing Board
When most of the well-known test methods where originated the world looked different. Back than making comprehensive strategies and plans was important, (test) engineering was focussed on doing things thoroughly and following (international) standards was important for organizations. Now other values are considered more important, like speed, craftsmanship, flexibility, goal orientation and pragmatism. In this keynote Jan Jaap will consider the changes testers and test organizations face today and explore the consequences of these changes for the test process and the individual tester.
TDD Mini Workshop @ Bucharest JUG 2014 04 24
This document introduces Test-Driven Development (TDD) as an incremental approach to software design that involves writing tests before code. TDD follows three main steps - write a test, add minimum code to pass the test, and refactor code and tests. It allows requirements to change more easily by starting with examples and extracting abstractions based on patterns rather than predefining all designs upfront. The document notes two main difficulties with TDD as thinking at the problem level rather than solution and using proof-based rather than assumption-based design, and provides guidance on getting started with TDD by focusing on the next test and design direction.
What is xp
XP is an agile software development methodology based on values of communication, simplicity, feedback, courage, and respect. It emphasizes coding, testing, listening, and designing activities. Core practices include pair programming, test-driven development, small releases, refactoring, and collective code ownership. Testing is done through automated unit tests written by developers and acceptance tests defined by customers.
DevOps interview questions and answers
The document provides information on various DevOps concepts through a question and answer format. It defines design patterns as solutions to common problems faced by developers that represent best practices. It describes continuous deployment as instrumenting important project life cycle steps when moving code to production. It distinguishes between functional testing which targets business goals and requirements, and non-functional testing which focuses on aspects like performance and security. It explains the differences between white box testing which uses internal knowledge and black box testing which does not. It provides examples of resilience test tools like Hystrix and Chaos Monkey. It describes extreme programming as an agile methodology focused on customer satisfaction and team collaboration. It defines pair programming as two programmers working together on the same code. Finally
Agile Engineering Practices
Agile engineering practices from XP and FDD focusing on FDD. (Based on cultural challenges that XP faces.)
Sdlc + agile business analysis
The document discusses software testing and agile methodologies. It defines software testing as executing a program with the intent of finding errors. A good test case has a high probability of finding undiscovered errors. It also discusses why software has defects such as bad communication, design, and coding. The document then covers agile methodologies like Scrum, which is an iterative development process involving sprints, daily stand-ups, and product backlogs. It provides synonyms for "agile" and discusses concepts like story mapping in agile projects.
Shift left as first transformation step into Quality Assurance
Do you work in a company which has established effective testing process, which ensure high quality and support Agile methodologies? Can your testing process be used as a model for other companies? Fortunately, we were in that place a few years ago and had to ask ourselves a question about the next step. The answer was: Let’s be Quality Assurance Engineers rather than Testers. But what should we do? How can we do this transformation?
At the same time, I got feedback from my colleague – Head of Java practice: “Your testers found defects in areas / scenarios which weren’t included in development scope / my devs didn’t know that should cover those edge cases. What can we do with that?”
I had to agree with him. There is no sense to test scenarios which weren’t implemented. This was the starting point of our transformation. We decided to implement Shift left model as it looks like the most promising one. But when we implemented it not everything worked as smooth as we wished. New challenges appeared, but more in my presentation.
Introduction of sdlc
This document introduces the software development life cycle (SDLC), including its definition as a sequential process for building software or systems, its main phases such as requirements analysis, planning, designing, building, testing and deployment, and some common SDLC models like the waterfall model, prototyping, rapid application development and extreme programming. The document was presented by Md Abdullah Al Rumy and provides his contact information at the end.
2016 04-25 continuous integration at google scale
Google runs continuous integration at an enormous scale, with over 30,000 developers submitting changes 30,000 times per day. They developed techniques like just-in-time scheduling to efficiently run the 150+ million tests per day in a linear rather than quadratic time complexity. This allows them to provide fast feedback to developers while keeping compute costs reasonable as the number of changes, tests, and developers grows enormously over time.
[DPE Summit] How Improving the Testing Experience Goes Beyond Quality: A Deve...
[DPE Summit] How Improving the Testing Experience Goes Beyond Quality: A Deve...Roberto Pérez Alcolea
It is well known that organizations connect software testing with software quality: making sure that the code does what it supposed to do.
Unfortunately, many organizations believe that testing is a slow process that causes stagnancy in the project. Organizations say that due to slow testing process they are not able to meet set milestones, but it doesn’t have to be this way.
The testing stage is also part of the developer experience, and making it such that engineers are productive and continue delivering software not only fast but with confidence is crucial.
In this talk, we will explore a few approaches that we are taking in order to deliver a more consistent and delightful testing experience for JVM engineers at Netflix. The end goal: speed up engineers’ feedback loop by running tests locally constantly as much as possible.Dealing With Legacy: The Real-World Experience
This document summarizes the experience of a team dealing with legacy code in a critical ordering application. Some of the challenges they faced included a mix of junior and senior developers, preparing for an upgrade, and planning a major design overhaul of legacy code with little documentation. Things that worked well included Scrum processes, bi-weekly releases, automation, and opportunistic refactoring. Areas for improvement included larger design refactors, more testing, and test-driven development. In the future, the author would have liked living documentation, monitoring, and more efficient UI testing. The presentation warns against creating legacy code and encourages design refactoring and better practices.
More Related Content
What's hot
Test Driven Development
TDD
TAD
Why TDD
Test Driven Development
Issues without unit tests
Benefits of writing unit tests
Agile engineering practices – a short overview
This document provides a short overview of agile engineering practices, including Scrum, XP, Kanban, FDD, and DSDM. It summarizes key practices such as pair programming, test-driven development, behavior driven development, acceptance testing, exploratory testing, polyglot programming, domain specific languages, continuous integration, continuous testing, static code checking, agile databases, lightweight domain modeling, and continuous delivery. Each practice is briefly described in one slide with information on feedback time, styles, and challenges.
Extreme programming - a quick and agile overview !
Tried putting things in the deck that I learnt about Extreme programming in XP Conference held in Bangalore. I have tried to keep it at very high level added with light moments, so that it doesn't getting boring and makes sense for most of us
Tdd and bdd
a brief introduction to Test Driven Development and Behavior Driven Development and the main differences between both.
TDD and Unit Testing in Golang
Test-driven development (TDD) is a process where test cases are created to validate requirements before functional code is written. The primary goals of TDD are to help specify requirements and design and to produce clean, bug-free code through a short development cycle of writing tests then code to pass those tests. Good unit tests for TDD should run fast, isolate dependencies, clearly define their scope, not require special setup, and clearly indicate their intention. In Golang, the testing package and go test command provide tools for writing and running tests, and go test can measure test coverage.
Tech talks #1- Unit testing and TDD
The document discusses unit testing and test-driven development (TDD). It introduces unit testing and TDD, explaining their benefits and how they can improve quality. It also provides an overview of JUnit for unit testing in Java and the red-green-blue process for TDD. The document concludes with a live demo of TDD and suggestions for implementing TDD and acceptance test-driven development.
Agile versus waterfall
This document compares and contrasts the Waterfall and Agile project management methodologies. It outlines the key differences between the two approaches, such as Waterfall being rigid and inflexible while Agile is iterative and flexible. It also discusses how they have similar elements like planning and tracking progress. The document notes that while Waterfall is best for long-term, stable projects, Agile has grown in popularity for its ability to adapt to changes. It concludes that a hybrid approach combining aspects of both methodologies can work best depending on the specific project's needs.
Introduction To Extreme Programming
Extreme Programming (XP) is an agile software development methodology that focuses on rapid software development and frequent delivery of working software. It emphasizes customer collaboration, small releases, and frequent testing. Key practices of XP include writing tests first, continuous integration, pair programming, and customer involvement.
Agile model in software testing
The agile model is an incremental software development model where testing is done after each release to ensure software quality. It allows for changes to be implemented at low cost by rolling back work done in previous sprints. Some advantages are flexibility to changing requirements, ability to incorporate last minute changes, and satisfied customers through iterative releases. Communication between developers and customers is emphasized over process. Potential disadvantages include lack of documentation and difficulty estimating efforts for large projects initially.
Agile code quality metrics
The document discusses various code quality metrics that can be used to understand software quality, including defects density, unit test density, code and test coverage, cyclomatic complexity, fan-in and fan-out, and WTFs per minute. While metrics can help identify issues, they cannot determine the precise cause. Metrics should be used carefully to avoid incentivizing behaviors like hiding bugs. Maintaining pride in craftsmanship is important for quality.
Infopulse: How we do Scrum
The document discusses an agile software development process and challenges. It mentions experience with J2EE 1.4, UML, MDA, Flex3 and ViewXP technologies. The company is seeking investors and uses Scrum methodology with 15 hour tasks, 30 minute standups, failed demos, late team members, story points, planning poker, and velocity metrics for estimation. Builds and testing are also mentioned.
TestIstanbul 2017 Keynote: "Characteristics Of A Modern Test Process" by Jan ...
TestIstanbul 2017 Keynote: "Characteristics Of A Modern Test Process" by Jan ...Turkish Testing Board
When most of the well-known test methods where originated the world looked different. Back than making comprehensive strategies and plans was important, (test) engineering was focussed on doing things thoroughly and following (international) standards was important for organizations. Now other values are considered more important, like speed, craftsmanship, flexibility, goal orientation and pragmatism. In this keynote Jan Jaap will consider the changes testers and test organizations face today and explore the consequences of these changes for the test process and the individual tester.
TDD Mini Workshop @ Bucharest JUG 2014 04 24
This document introduces Test-Driven Development (TDD) as an incremental approach to software design that involves writing tests before code. TDD follows three main steps - write a test, add minimum code to pass the test, and refactor code and tests. It allows requirements to change more easily by starting with examples and extracting abstractions based on patterns rather than predefining all designs upfront. The document notes two main difficulties with TDD as thinking at the problem level rather than solution and using proof-based rather than assumption-based design, and provides guidance on getting started with TDD by focusing on the next test and design direction.
What is xp
XP is an agile software development methodology based on values of communication, simplicity, feedback, courage, and respect. It emphasizes coding, testing, listening, and designing activities. Core practices include pair programming, test-driven development, small releases, refactoring, and collective code ownership. Testing is done through automated unit tests written by developers and acceptance tests defined by customers.
DevOps interview questions and answers
The document provides information on various DevOps concepts through a question and answer format. It defines design patterns as solutions to common problems faced by developers that represent best practices. It describes continuous deployment as instrumenting important project life cycle steps when moving code to production. It distinguishes between functional testing which targets business goals and requirements, and non-functional testing which focuses on aspects like performance and security. It explains the differences between white box testing which uses internal knowledge and black box testing which does not. It provides examples of resilience test tools like Hystrix and Chaos Monkey. It describes extreme programming as an agile methodology focused on customer satisfaction and team collaboration. It defines pair programming as two programmers working together on the same code. Finally
Agile Engineering Practices
Agile engineering practices from XP and FDD focusing on FDD. (Based on cultural challenges that XP faces.)
Sdlc + agile business analysis
The document discusses software testing and agile methodologies. It defines software testing as executing a program with the intent of finding errors. A good test case has a high probability of finding undiscovered errors. It also discusses why software has defects such as bad communication, design, and coding. The document then covers agile methodologies like Scrum, which is an iterative development process involving sprints, daily stand-ups, and product backlogs. It provides synonyms for "agile" and discusses concepts like story mapping in agile projects.
Shift left as first transformation step into Quality Assurance
Do you work in a company which has established effective testing process, which ensure high quality and support Agile methodologies? Can your testing process be used as a model for other companies? Fortunately, we were in that place a few years ago and had to ask ourselves a question about the next step. The answer was: Let’s be Quality Assurance Engineers rather than Testers. But what should we do? How can we do this transformation?
At the same time, I got feedback from my colleague – Head of Java practice: “Your testers found defects in areas / scenarios which weren’t included in development scope / my devs didn’t know that should cover those edge cases. What can we do with that?”
I had to agree with him. There is no sense to test scenarios which weren’t implemented. This was the starting point of our transformation. We decided to implement Shift left model as it looks like the most promising one. But when we implemented it not everything worked as smooth as we wished. New challenges appeared, but more in my presentation.
Introduction of sdlc
This document introduces the software development life cycle (SDLC), including its definition as a sequential process for building software or systems, its main phases such as requirements analysis, planning, designing, building, testing and deployment, and some common SDLC models like the waterfall model, prototyping, rapid application development and extreme programming. The document was presented by Md Abdullah Al Rumy and provides his contact information at the end.
2016 04-25 continuous integration at google scale
Google runs continuous integration at an enormous scale, with over 30,000 developers submitting changes 30,000 times per day. They developed techniques like just-in-time scheduling to efficiently run the 150+ million tests per day in a linear rather than quadratic time complexity. This allows them to provide fast feedback to developers while keeping compute costs reasonable as the number of changes, tests, and developers grows enormously over time.
What's hot (20)
Extreme programming - a quick and agile overview !
Extreme programming - a quick and agile overview !
TestIstanbul 2017 Keynote: "Characteristics Of A Modern Test Process" by Jan ...
TestIstanbul 2017 Keynote: "Characteristics Of A Modern Test Process" by Jan ...
Shift left as first transformation step into Quality Assurance
Shift left as first transformation step into Quality Assurance
Similar to Search microservice
[DPE Summit] How Improving the Testing Experience Goes Beyond Quality: A Deve...
[DPE Summit] How Improving the Testing Experience Goes Beyond Quality: A Deve...Roberto Pérez Alcolea
It is well known that organizations connect software testing with software quality: making sure that the code does what it supposed to do.
Unfortunately, many organizations believe that testing is a slow process that causes stagnancy in the project. Organizations say that due to slow testing process they are not able to meet set milestones, but it doesn’t have to be this way.
The testing stage is also part of the developer experience, and making it such that engineers are productive and continue delivering software not only fast but with confidence is crucial.
In this talk, we will explore a few approaches that we are taking in order to deliver a more consistent and delightful testing experience for JVM engineers at Netflix. The end goal: speed up engineers’ feedback loop by running tests locally constantly as much as possible.Dealing With Legacy: The Real-World Experience
This document summarizes the experience of a team dealing with legacy code in a critical ordering application. Some of the challenges they faced included a mix of junior and senior developers, preparing for an upgrade, and planning a major design overhaul of legacy code with little documentation. Things that worked well included Scrum processes, bi-weekly releases, automation, and opportunistic refactoring. Areas for improvement included larger design refactors, more testing, and test-driven development. In the future, the author would have liked living documentation, monitoring, and more efficient UI testing. The presentation warns against creating legacy code and encourages design refactoring and better practices.
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
Slides from the St. Louis Big Data IDEA meetup. Kit Menke presented on how to test your Apache Spark applications. May 2021 meetup notes
software lecture
The document discusses various software development processes including traditional/waterfall methods, prototyping, rapid application development, evolutionary/incremental/spiral development, agile methods like extreme programming, formal methods, and fourth generation techniques. It provides details on the characteristics, advantages, and disadvantages of each approach.
Path Dependent Development (PyCon AU)
(Image on page 3: it's the traditional fast/good/cheap trade-off. Something glitched in the conversion))
The decisions we make in getting software ready to ship can have lasting consequences for later versions. Early priorities can end up setting the direction for the whole project.
My presentation from PyConAU 2012 (including bonus slides that were cut before the talk due to time limitations)
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.
Path dependent-development (PyCon India)
(Image on page 3: it's the traditional fast/good/cheap trade-off. Something glitched in the conversion))
Agile Methods and Data Warehousing (2016 update)
This presentation takes a look at the Agile Manifesto and the 12 Principles of Agile Development and discusses how these apply to Data Warehousing and Business Intelligence projects. Several examples and details from my past experience are included. Includes more details on using Data Vault as well. (I gave this presentation at OUGF14 in Helsinki, Finland and again in 2016 for TDWI Nashville.)
Software Development Methodologies
The document discusses various software development methodologies including Agile, Scrum, XP, Kanban, Lean, Crystal, DSDM, FDD, V-Model, Incremental Model, Evolutionary Prototyping, Cowboy Coding, and Personal Software Process. It describes how each methodology works, the roles involved, advantages and disadvantages. For example, it states that Agile is responsive to market changes, Scrum uses sprints, planning meetings and burndown charts, and Cowboy Coding lacks structure but allows for experimentation.
Keeping code clean
One of the main hindrances to teams being able to respond rapidly to new features are technical problems resulting from bad coding practices, also known as technical debt. Melissa and Brett will cover Agile tools and practices that help development teams write better code and increase maintainability. Topics that will be covered include:
Pair programming
Automated Unit Testing
Refactoring
Test-Driven Development
Agile Architecture
Acceptance Test Driven Development
Presentation about using acceptance testing to write first acceptance criteria using scenarios to ensure what you get is what you wanted
Mastering BDD - Eran Kinsbruner Workshop Quest 2018
a 3.5 hours workshop on digital trends and BDD, and how teams can leverage BDD practices to assure high quality for their mobile and web apps
Developer Productivity Engineering with Gradle
Presented by: Justin Reock & Sterling Greene
Presented at the All Things Open 2021
Raleigh, NC, USA
Raleigh Convention Center
Abstract: In 2007, Hans Dockter invented the Gradle Build Tool because he felt that developers deserved less friction in their toolchain. The prevailing build technologies of the time were adequate but inefficient, not taking advantage of possible acceleration technologies and, with some exceptions, very limited in their language and framework support. Gradle is now one of the most widely used build tools available, downloaded about 25 million times a month as of September of 2021. It’s the default build tool in Android Studio, and is trusted by millions of developers to create their artifacts quickly and cleanly.
The principles that originally guided the Gradle build tool towards its current popularity have continued into an emerging practice known as Developer Productivity Engineering or DPE. DPE is a new software development practice that uses acceleration technologies to speed up the software build and test process and data analytics to optimize the impact of acceleration technologies and make troubleshooting more efficient. Leading technology companies are using this practice today to accelerate feedback cycles by over 90% in some cases, improving the developer experience and increasing team velocity.
Join Sterling Greene, Lead Software Engineer for the Gradle Build Tool, and Justin Reock, Field CTO of Gradle Enterprise, to learn why DPE is swiftly becoming the most important movement in software development since the introduction of DevOps.
Attendees will walk away from this presentation with a better understanding of:
● The importance of fast feedback cycles and how to achieve them using build and test acceleration technologies
● Using build and test data to make troubleshooting and problem root cause determination more efficient.
● The importance of leveraging failure analytics to improve toolchain reliability, including managing avoidable failures like flaky tests.
● How to continuously improve performance and guard against regressions through trend and metric observability.
● The Cost of Inaction (CoI) by not investing in developer productivity across your local build environments and CI/CD pipelines in terms of engineering cost, TTM and software quality.
● How to elevate the strategic priority of DPE in your organization.
Best Kept Secret of Transformation – Release Frequently
Given by Jon Dickinson (Partner at Equal Experts) at Agile Yorkshire Feb 2016.
In this talk Jon presents a case study where Equal Experts were engaged with a large finance client to deliver new versions of their payment service while improving their delivery practices and supporting an 'agile transformation'. There were many attempts to introduce new working practices, tools and techniques. One change in particular was orders of magnitude more effective than any other and proved the catalyst for embedding most of the change that had failed to stick before.
Usable Software Design
How to improve software design by using UX mindset, techniques and practices, given that the user of software design is the developer.
3 Keys to Performance Testing at the Speed of Agile
Many teams on the journey toward true agility attempt to “go faster,” but most fail to bake performance checks into their delivery process. This leads to more rework than new work, fighting fires in production, burnout, a poor customer experience, and maybe most importantly, no real improvement in speed.
Join this web seminar to learn how to fit performance testing into a tight work schedule and discover how to create a performance testing strategy that meets the agile cadence of small batch sizes and sprint deadlines.
www.neotys.com
Behaviour Driven Development: Oltre i limiti del possibile
The QA Financial Forum: Milan 2019
23 January at the Excelsior Hotel Gallia.
Anna-Maria Lukina, Exactpro Business Development Director
The QA Financial Forum: Milan is one of the leading fintech conferences in Italy. The event focuses on the latest achievements in software risk management and automation of software testing. The predominant theme of the Milan event will be Quality Assurance for the entire Software Development Life Cycle (SDLC).
The topics under discussion will feature:
- Technologies for Automation & AI
- DevOps & CI/CD
- Value Stream Management
- Test Data Management
- Regulatory Compliance
- App Security & DevSecOps
- Testing and quality assurance of Blockchain platforms
The official language of the event is Italian.
Loopt unit test experiences
We all hear how unit tests can ensure higher quality code and help us in day to day refactoring, but is it feasible to write and maintain unit tests in a fast paced startup company?
This is a presentation by server lead, Heine Frifeldt, on how unit tests was gradually introduced into the server code base at Loopt, which tools are used in the continuous build environment, coding techniques and lessons learned.
Bridging the Gap Between Development and Regulatory Teams
Bridging the gap between development and regulatory teams requires addressing their different workflows and tendencies.
1) Development teams prefer an agile approach with early iteration, while regulatory teams require a defined process. This leads to a gap if development starts without any process in place.
2) Managing complex, layered software and inevitable late changes is difficult under regulatory constraints. Processes need to assume change and minimize its impact.
3) Individual cognitive overload from balancing technical and regulatory demands can be reduced with simple, clear processes and guidelines.
Bridging the gap requires starting development with even a minimal interim process, keeping obligations simple, leveraging prototypes to reduce late changes, and optimizing document management between teams.
Laptop Devops: Putting Modern Infrastructure Automation to Work For Local Dev...
A talk around various development environment automations us and other ThoughtWorkers have seen and built on many different projects, and learnings around best practices. We've seen serious work put into this drastically increase the productivity of developers, and solve a lot of the problems that microservices can otherwise cause.
Similar to Search microservice (20)
[DPE Summit] How Improving the Testing Experience Goes Beyond Quality: A Deve...
[DPE Summit] How Improving the Testing Experience Goes Beyond Quality: A Deve...
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
May 2021 Spark Testing ... or how to farm reputation on StackOverflow
Mastering BDD - Eran Kinsbruner Workshop Quest 2018
Mastering BDD - Eran Kinsbruner Workshop Quest 2018
Best Kept Secret of Transformation – Release Frequently
Best Kept Secret of Transformation – Release Frequently
3 Keys to Performance Testing at the Speed of Agile
3 Keys to Performance Testing at the Speed of Agile
Behaviour Driven Development: Oltre i limiti del possibile
Behaviour Driven Development: Oltre i limiti del possibile
Bridging the Gap Between Development and Regulatory Teams
Bridging the Gap Between Development and Regulatory Teams
Laptop Devops: Putting Modern Infrastructure Automation to Work For Local Dev...
Laptop Devops: Putting Modern Infrastructure Automation to Work For Local Dev...
More from Jean Carlo Machado
Python clean code for data producs
The document discusses clean code practices for machine learning projects. It defines clean code as code where each routine does what is expected. Clean ML code can lead to fewer bugs, less technical debt, and easier handovers. The document outlines practices for small-scale clean code like decorators, list comprehensions, and avoiding else blocks. It also discusses type systems, domain-driven design, and side effects for large-scale clean code. Overall, clean code aims to reduce complexity and make code more readable and maintainable.
Domain Driven Design Made Functional with Python
This document discusses using domain modeling with types in Python using the static type checker Mypy. It motivates the use of types for domain-driven design and functional programming concepts. It then provides examples of building blocks for Mypy's type system algebra, including simple values with new types, combinations of values, modeling choices with unions, type functions, classes, generics, and putting the concepts together in a workflow. It also discusses limitations of Mypy and resources for further learning. The overall goal is to leave the reader inspired to learn more about applying type systems to domain modeling.
Git avançado
This document discusses advanced Git topics including patches, commands that generate diffs, rewriting history, bisecting, rerere, moving code, and plumbling. It also explains how Git stores content in blobs by compressing a header, content, and SHA-1 hash into a file in the .git/objects directory based on the hash. Contact information is provided for questions.
Functional php
This document discusses functional programming concepts in PHP like pure functions, higher-order functions, and recursion. It provides examples of mapping, folding, and partial function application. Modularization with functional programming encourages decomposing problems into smaller parts and recomposing them with lazy evaluation and higher-order functions to reduce complexity.
Why functional programming matters
O documento discute as vantagens da programação funcional, incluindo facilitar a modularização, permitir concorrência nativa e desacelerar o apodrecimento do código. A programação funcional evita mudanças de estado e decompõe problemas em partes menores que são recompostas com funções de alta ordem.
Clean code v3
O documento discute os princípios do Clean Code, focando na legibilidade, manutenibilidade e facilidade de entendimento do código. Ele aborda tópicos como nomes significativos, funções curtas, comentários úteis, alta coesão e baixo acoplamento entre módulos. O documento também recomenda práticas como programação em pares, desenvolvimento guiado por testes e revisão sistemática do código.
Clean Code V2
The document discusses the importance of clean code and avoiding software rot. It outlines characteristics of rotting software like rigidity, fragility, immobility and viscosity. The solution discussed is adopting good practices like those in software craftsmanship and clean code skills. These include principles like DRY, keeping methods small, using descriptive names and comments, following SOLID principles, and prioritizing readability and maintainability over optimizations.
Review articles bio inspired algorithms
Este documento resume e classifica vários algoritmos de computação bioinspirados. Ele discute como algoritmos como enxames de partículas, algoritmos genéticos e de formigas imitam processos naturais para resolver problemas de otimização. O documento também analisa a popularidade destes algoritmos e áreas para futuras pesquisas, como a redução de parâmetros e a coevolução.
Introduction to Rust
This document provides an introduction to the Rust programming language. It describes that Rust was developed by Mozilla Research beginning in 2009 to combine the type safety of Haskell, concurrency of Erlang, and speed of C++. Rust reached version 1.0 in 2015 and is a generic, multiparadigm systems programming language that runs on platforms including ARM, Apple, Linux, Windows and embedded devices. It emphasizes security, performance and fine-grained memory safety without garbage collection.
Limitações do HTML no Desenvolvimento de Jogos Multiplataforma
- O documento discute as limitações do HTML no desenvolvimento de jogos multiplataforma, identificando 42 limitações com base no estudo de várias tecnologias da web e na criação de um protótipo. Muitas limitações são problemas nas especificações ou filosofias da web, embora a maioria seja contornável.
Clean code
The document discusses principles and practices for writing clean code, including:
- Clean code is code that is readable, writable, and maintainable. It focuses on the needs of human readers over the computer.
- Broken windows theory states that one piece of low-quality code leads to more as developers get used to a lower standard. This can lead to software rot and eventual system rewrites.
- Characteristics of rotting software include rigidity, fragility, immobility, and viscosity.
- Following principles like SOLID, DRY, Law of Demeter, and object calisthenics can help avoid rot and keep code clean.
- Practices like using self-document
More from Jean Carlo Machado (11)
Limitações do HTML no Desenvolvimento de Jogos Multiplataforma
Limitações do HTML no Desenvolvimento de Jogos Multiplataforma
Recently uploaded
What is Augmented Reality Image Tracking
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
OpenMetadata Community Meeting - 5th June 2024
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Unveiling the Advantages of Agile Software Development.pdf
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
GreenCode-A-VSCode-Plugin--Dario-Jurisic
Presentation about a VSCode plugin from Dario Jurisic at the GSD Community Stage meetup
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
How to write a program in any programming language
How to write a program in any programming language
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
SWEBOK and Education at FUSE Okinawa 2024
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS Security Version 1.2 was adopted in 2024. This revision strengthens support for long runnings systems adding new cryptographic algorithms, certificate revocation, and hardness against DoS attacks.
Empowering Growth with Best Software Development Company in Noida - Deuglo
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
The quest for the best AI face swap solution is marked by an amalgamation of technological prowess and artistic finesse, where cutting-edge algorithms seamlessly replace faces in images or videos with striking realism. Leveraging advanced deep learning techniques, the best AI face swap tools meticulously analyze facial features, lighting conditions, and expressions to execute flawless transformations, ensuring natural-looking results that blur the line between reality and illusion, captivating users with their ingenuity and sophistication.
Web:- https://undressbaby.com/
Using Query Store in Azure PostgreSQL to Understand Query Performance
Microsoft has added an excellent new extension in PostgreSQL on their Azure Platform. This session, presented at Posette 2024, covers what Query Store is and the types of information you can get out of it.
SMS API Integration in Saudi Arabia| Best SMS API Service
Discover the benefits and implementation of SMS API integration in the UAE and Middle East. This comprehensive guide covers the importance of SMS messaging APIs, the advantages of bulk SMS APIs, and real-world case studies. Learn how CEQUENS, a leader in communication solutions, can help your business enhance customer engagement and streamline operations with innovative CPaaS, reliable SMS APIs, and omnichannel solutions, including WhatsApp Business. Perfect for businesses seeking to optimize their communication strategies in the digital age.
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise EditionEnvertis Software Solutions
Odoo ERP software
Odoo ERP software, a leading open-source software for Enterprise Resource Planning (ERP) and business management, has recently launched its latest version, Odoo 17 Community Edition. This update introduces a range of new features and enhancements designed to streamline business operations and support growth.
The Odoo Community serves as a cost-free edition within the Odoo suite of ERP systems. Tailored to accommodate the standard needs of business operations, it provides a robust platform suitable for organisations of different sizes and business sectors. Within the Odoo Community Edition, users can access a variety of essential features and services essential for managing day-to-day tasks efficiently.
This blog presents a detailed overview of the features available within the Odoo 17 Community edition, and the differences between Odoo 17 community and enterprise editions, aiming to equip you with the necessary information to make an informed decision about its suitability for your business.socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
Webinar On-Demand: Using Flutter for Embedded
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Recently uploaded (20)
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
Unveiling the Advantages of Agile Software Development.pdf
Unveiling the Advantages of Agile Software Development.pdf
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
How to write a program in any programming language
How to write a program in any programming language
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS-Security 1.2 - What's New? Stronger security for long-running systems
Empowering Growth with Best Software Development Company in Noida - Deuglo
Empowering Growth with Best Software Development Company in Noida - Deuglo
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Using Query Store in Azure PostgreSQL to Understand Query Performance
Using Query Store in Azure PostgreSQL to Understand Query Performance
SMS API Integration in Saudi Arabia| Best SMS API Service
SMS API Integration in Saudi Arabia| Best SMS API Service
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition
Search microservice
- 1. Crafting Software at GYG The Search Case By Jean Carlo Machado & Leandro Lages
- 2. Purpose ● Share decision making mindset ● Practices to craft software ● Learnings ● Collect feedback, learn more! Duration: 30 min
- 3. Q4 Quest: move search to a service 1 Enable 2x engineers 2 Scale/evolve separately 3 Move 3 use cases/create momentum for Q1
- 6. What search does? ● Add ranking formulas based on ML models ● Filter by availability ● Reorder results in memory ● Retry on no results ● AB testing
- 10. Use cases ● Get documents ● Filter by availability ● Add diversity (CL) ● Trade off cost/value ● Incremental difficulty ● A complete case Reasons
- 11. Iteration 1 - Get documents ● Simple scenario ● To lay the architecture foundation is hard ● To put in prod is hard Monitoring Stress testing/Incremental distribution Fallback
- 13. Iteration 2 - Availability ● Complex scenario in GYG ● isAvailable: Date -> Activity -> Boolean ● Not clearly spec we are not there yet
- 15. Pick a language The only hard thing to change
- 16. Software Architecture 1 Communication of Intent 2 Allows delaying decisions
- 18. Domain ● Add first business rules ● Testing ● A little architecture
- 23. Infrastructure Elasticsearch SDK Api directly (Guzzle) No retry Simplest Official (Elastic) Internal retry Paid devs Small Used previously (Elastica) Internal retry Good query builder setup Not 100% in sync with new features Big
- 25. Application ● Routing Solution ● Dependency injection ● Input validation
- 26. PSR 7 dependent routing
- 27. PSR 11 dependent injection & validation
- 30. Requirement added: swagger 3.0
- 31. Principles & lessons Simple is not easy Stick with concepts/standards instead of solutions Write less software, delay decisions, embrace change Admit your own ignorance, there are things you don’t know you don’t know trust refactoring -> Testing
- 32. Principles & lessons Scale architecture with complexity Relatively simple things can tolerate a certain level of disorganization. However, as complexity increases, disorganization becomes suicidal. Robert Martin
- 33. I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult. Tony Hoare
- 34. QUESTIONS?
- 35. Thanks