This document asks questions about the Bible and then provides information in response. It discusses how the Bible is a living book, contains prophecies that have come true, has stood the test of time, and has historical accuracy validated by ancient manuscripts. The Bible was written over 1500 years, in three languages, by over 40 authors in different places and times, yet maintains a continuity of purpose centered around Jesus Christ. The logical conclusion is that the Bible was divinely inspired by God and reliably conveys his message of redemption through Christ.
This document provides an overview of the Simple Record Web (SRU) protocol and how it can be used with Lucene to provide search and retrieval of XML database records. It describes key SRU features like explain records, CQL query grammar, persistent result sets, XML record returns, and index browsing. It also provides details and examples of how to configure an SRU server using Lucene by modifying configuration files and properties.
The document discusses improving communication during interactions. It provides an example where someone was blamed for a bug found in production. They responded angrily by saying "We couldn't have found that bug in test". The document advises to check your feelings before responding, ask clarifying questions instead of making assumptions, and consider different interpretations of what was said. It also notes that debugging interactions can be difficult and you shouldn't respond if you're not okay with your feelings.
This document lists several consumer product patents including a housekeeping cart, cleaning cart, health care walker wheel, youth high chair, and cane handle. The portfolio contains patents for various household and medical devices designed for consumer use.
This document asks questions about the Bible and then provides information in response. It discusses how the Bible is a living book, contains prophecies that have come true, has stood the test of time, and has historical accuracy validated by ancient manuscripts. The Bible was written over 1500 years, in three languages, by over 40 authors in different places and times, yet maintains a continuity of purpose centered around Jesus Christ. The logical conclusion is that the Bible was divinely inspired by God and reliably conveys his message of redemption through Christ.
This document provides an overview of the Simple Record Web (SRU) protocol and how it can be used with Lucene to provide search and retrieval of XML database records. It describes key SRU features like explain records, CQL query grammar, persistent result sets, XML record returns, and index browsing. It also provides details and examples of how to configure an SRU server using Lucene by modifying configuration files and properties.
The document discusses improving communication during interactions. It provides an example where someone was blamed for a bug found in production. They responded angrily by saying "We couldn't have found that bug in test". The document advises to check your feelings before responding, ask clarifying questions instead of making assumptions, and consider different interpretations of what was said. It also notes that debugging interactions can be difficult and you shouldn't respond if you're not okay with your feelings.
This document lists several consumer product patents including a housekeeping cart, cleaning cart, health care walker wheel, youth high chair, and cane handle. The portfolio contains patents for various household and medical devices designed for consumer use.
The document discusses the benefits of early testing in software development. It uses a dice product challenge exercise to demonstrate how misunderstandings can occur when requirements are not well understood. Without asking questions, the delivered product may not match what was intended. Early testing allows teams to identify assumptions and gaps. By questioning requirements upstream during design and development, testing can help ensure the final product meets expectations.
The document discusses jQuery, a lightweight JavaScript library. It provides an overview of why jQuery is useful for DOM navigation and handling browser differences. It also discusses how Microsoft will include jQuery with Visual Studio to provide IntelliSense support. Finally, it lists some additional resources for learning more about jQuery.
The document discusses the importance of shared understanding over just shared documentation. It notes that misunderstandings can lead to incorrect assumptions and undesired outcomes. Testing helps squash assumptions by asking questions early. The earlier questions are asked, the sooner assumptions can be addressed to deliver the desired product. It then provides an example exercise where teams build dice products with implicit requirements without talking in the first round, but can ask questions in the second round to develop shared understanding.
The document discusses Cynefin, a framework for decision making that categorizes systems as obvious, complicated, complex, or chaotic based on the relationship between cause and effect. It shows how Cynefin can be applied to software testing to help categorize different types of bugs and determine the appropriate testing approach. Cynefin is presented as a model to aid testers in decision making under uncertainty.
This document discusses using Lucene to index both static and dynamic web pages. It describes parsing Apache web server logs to extract parameters for dynamic pages and generate URLs. These URLs are then used to fetch results pages, which are analyzed and indexed. The indexing process is implemented in a Java program that reads logs, generates URLs, and uses Lucene to extract text and build an index from the dynamic content. A demo shows searching the index from both a command prompt and web interface. Lucene provides powerful yet easy to use search capabilities and can index dynamic pages not normally accessible to search engines.
Programmers testing their own code is not a new phenomenon, but with the emergence of agile development practices and code craftsmanship, there has been a move towards Programmers visibly taking more accountability for the code they write.
This is great news for those Testers used to being the gatekeepers to quality and answering the “why wasn’t this found in test?” question.
Programmers and Testers are now helping to improve the quality of code, but there is still one anti-pattern I have observed in teams in which both Programmers and Testers are testing the code – they are not actually working with each other when establishing a unified testing strategy.
This results in gaps in test coverage and / or unnecessarily duplicated testing.
This slide deck is from my Agile North presentation.where I presented my ICEBERG model for helping Programmers & Testers work more collaboratively. I also introduced another model I use for helping teams work together - Virginia Satir's Interaction Model.
The Bullitt Center in Seattle is the world's largest commercial building to achieve the rigorous Living Building Challenge certification. It uses solar power, rainwater catchment and super-insulated walls to generate more energy than it uses and collect all of its water needs on site. The six-story building aims to have a net-zero energy use and zero carbon emissions over a full year of operation.
The document is about the Semantic Web conference to be held in Honolulu, Hawaii from May 7-11, 2002. It provides information about the conference name, location, date, slogan, and lists some of the expected participants. XML markup is suggested to add structure and meaning to the information for machines to better understand the document.
Slides from my "Cynefin & Software Testing" workshop.
I've swapped out my description of the framework & added a video of Dave describing his framework in slide 3 (the black slide)
This allows me to get to the workshop element sooner.
Duplicate slides towards the end of the deck provide a reference point during the workshop element.
The document discusses the benefits of early testing in software development. It uses a dice product challenge exercise to demonstrate how misunderstandings can occur when requirements are not well understood. Without asking questions, the delivered product may not match what was intended. Early testing allows teams to identify assumptions and gaps. By questioning requirements upstream during design and development, testing can help ensure the final product meets expectations.
The document discusses jQuery, a lightweight JavaScript library. It provides an overview of why jQuery is useful for DOM navigation and handling browser differences. It also discusses how Microsoft will include jQuery with Visual Studio to provide IntelliSense support. Finally, it lists some additional resources for learning more about jQuery.
The document discusses the importance of shared understanding over just shared documentation. It notes that misunderstandings can lead to incorrect assumptions and undesired outcomes. Testing helps squash assumptions by asking questions early. The earlier questions are asked, the sooner assumptions can be addressed to deliver the desired product. It then provides an example exercise where teams build dice products with implicit requirements without talking in the first round, but can ask questions in the second round to develop shared understanding.
The document discusses Cynefin, a framework for decision making that categorizes systems as obvious, complicated, complex, or chaotic based on the relationship between cause and effect. It shows how Cynefin can be applied to software testing to help categorize different types of bugs and determine the appropriate testing approach. Cynefin is presented as a model to aid testers in decision making under uncertainty.
This document discusses using Lucene to index both static and dynamic web pages. It describes parsing Apache web server logs to extract parameters for dynamic pages and generate URLs. These URLs are then used to fetch results pages, which are analyzed and indexed. The indexing process is implemented in a Java program that reads logs, generates URLs, and uses Lucene to extract text and build an index from the dynamic content. A demo shows searching the index from both a command prompt and web interface. Lucene provides powerful yet easy to use search capabilities and can index dynamic pages not normally accessible to search engines.
Programmers testing their own code is not a new phenomenon, but with the emergence of agile development practices and code craftsmanship, there has been a move towards Programmers visibly taking more accountability for the code they write.
This is great news for those Testers used to being the gatekeepers to quality and answering the “why wasn’t this found in test?” question.
Programmers and Testers are now helping to improve the quality of code, but there is still one anti-pattern I have observed in teams in which both Programmers and Testers are testing the code – they are not actually working with each other when establishing a unified testing strategy.
This results in gaps in test coverage and / or unnecessarily duplicated testing.
This slide deck is from my Agile North presentation.where I presented my ICEBERG model for helping Programmers & Testers work more collaboratively. I also introduced another model I use for helping teams work together - Virginia Satir's Interaction Model.
The Bullitt Center in Seattle is the world's largest commercial building to achieve the rigorous Living Building Challenge certification. It uses solar power, rainwater catchment and super-insulated walls to generate more energy than it uses and collect all of its water needs on site. The six-story building aims to have a net-zero energy use and zero carbon emissions over a full year of operation.
The document is about the Semantic Web conference to be held in Honolulu, Hawaii from May 7-11, 2002. It provides information about the conference name, location, date, slogan, and lists some of the expected participants. XML markup is suggested to add structure and meaning to the information for machines to better understand the document.
Slides from my "Cynefin & Software Testing" workshop.
I've swapped out my description of the framework & added a video of Dave describing his framework in slide 3 (the black slide)
This allows me to get to the workshop element sooner.
Duplicate slides towards the end of the deck provide a reference point during the workshop element.