Deliberate practice agile2012_alex_aitken
•
0 likes•215 views
This document outlines an agenda for a talk on deliberate practice for becoming a better programmer. The agenda includes defining deliberate practice, conducting a FizzBuzz coding exercise, demonstrating object calisthenics principles, and discussing how to get started with deliberate practice. Object calisthenics principles constrain code to be more readable and maintainable, such as limiting indentation levels and class properties. The talk concludes by referencing additional resources on katas, constraint exercises, and practicing with a team.
Report
Share
Report
Share
Download to read offline
Recommended
Life Behind The Curve - MKGN #5
The document discusses how to stay up-to-date in the fast-paced web industry. It recommends focusing on relevant workflows and processes rather than trying to learn everything. Resources mentioned include articles, podcasts, conferences, and Twitter accounts to follow. However, the key point is that it's impossible to keep up with everything, so one should only learn what's needed and not feel pressured to know the latest trends or doubt their abilities from others' knowledge. True knowledge is accepting that there's always more to learn.
How To Pass A Ruby Code Test
After throwing down a few code tests I've started to have some ideas about what I want to see in a code test submission.
Week 1 presentation
This document outlines the plan and topics for the first week of a tech orientation program for mothers, including an introduction, an overview of the plan and tools to be used, sections on computer anatomy and web stacks, explanations of MVC and development cycles, and descriptions of development team roles and sources for more information.
Week 2
The document outlines the milestones and requirements for an art project. It includes:
1) Milestones such as submitting a proposal, creating a rubric and flowchart, presenting a prototype, and a final presentation and project.
2) Each milestone is assigned a percentage of the overall grade.
3) Deadlines are provided for submitting the proposal, rubric and flowchart, and prototype.
4) Instructions are given to create forums to collaborate with a team and start working on proposals and rubrics.
Drupal ladder Cebu : Learn to contribute | November 2013
First drupal ladder in the Philippines.
Saturday 23rd November 2013.
Hosted and sponsored by Promet Source.
Crafting a Ruby-on-Rails Course for Developers
This document summarizes Daniel Doubrovkine's proposed curriculum for a Ruby on Rails course for developers in NYC. The course would be held over 8 weeks, twice a week for 6-8 people per class. It would take a bottom-up approach, starting with Ruby basics and building up to authentication, APIs, and NoSQL. Students would build a complete Rails application as a final project. The curriculum aims to provide real-world experience and connections for career development. Feedback is discussed on ways to improve the class structure and learning experience.
WAE Project - Proposals.
My "Web Application Engineering" Project proposals. I'm doing this kind of thing just for fun. But I think I'll gonna change the project anyway.
CLC Orientation (Short Form)
This document outlines an agenda to discuss the vision, rules and guidelines, student learning, logistics, and practicalities of a laptop program. It discusses signing a responsible use policy and laptop acceptance form, which outline financial obligations for loss, damage, or repairs. It details the laptop allocation and replacement cycle by grade level. It also addresses parent controls and asks if there are any questions.
Recommended
Life Behind The Curve - MKGN #5
The document discusses how to stay up-to-date in the fast-paced web industry. It recommends focusing on relevant workflows and processes rather than trying to learn everything. Resources mentioned include articles, podcasts, conferences, and Twitter accounts to follow. However, the key point is that it's impossible to keep up with everything, so one should only learn what's needed and not feel pressured to know the latest trends or doubt their abilities from others' knowledge. True knowledge is accepting that there's always more to learn.
How To Pass A Ruby Code Test
After throwing down a few code tests I've started to have some ideas about what I want to see in a code test submission.
Week 1 presentation
This document outlines the plan and topics for the first week of a tech orientation program for mothers, including an introduction, an overview of the plan and tools to be used, sections on computer anatomy and web stacks, explanations of MVC and development cycles, and descriptions of development team roles and sources for more information.
Week 2
The document outlines the milestones and requirements for an art project. It includes:
1) Milestones such as submitting a proposal, creating a rubric and flowchart, presenting a prototype, and a final presentation and project.
2) Each milestone is assigned a percentage of the overall grade.
3) Deadlines are provided for submitting the proposal, rubric and flowchart, and prototype.
4) Instructions are given to create forums to collaborate with a team and start working on proposals and rubrics.
Drupal ladder Cebu : Learn to contribute | November 2013
First drupal ladder in the Philippines.
Saturday 23rd November 2013.
Hosted and sponsored by Promet Source.
Crafting a Ruby-on-Rails Course for Developers
This document summarizes Daniel Doubrovkine's proposed curriculum for a Ruby on Rails course for developers in NYC. The course would be held over 8 weeks, twice a week for 6-8 people per class. It would take a bottom-up approach, starting with Ruby basics and building up to authentication, APIs, and NoSQL. Students would build a complete Rails application as a final project. The curriculum aims to provide real-world experience and connections for career development. Feedback is discussed on ways to improve the class structure and learning experience.
WAE Project - Proposals.
My "Web Application Engineering" Project proposals. I'm doing this kind of thing just for fun. But I think I'll gonna change the project anyway.
CLC Orientation (Short Form)
This document outlines an agenda to discuss the vision, rules and guidelines, student learning, logistics, and practicalities of a laptop program. It discusses signing a responsible use policy and laptop acceptance form, which outline financial obligations for loss, damage, or repairs. It details the laptop allocation and replacement cycle by grade level. It also addresses parent controls and asks if there are any questions.
Web security-–-everything-we-know-is-wrong-eoin-keary
1) Web application security is often approached incorrectly, focusing too much on annual penetration tests and compliance, rather than ongoing monitoring and prevention through the development process.
2) Many vulnerabilities are introduced through third party libraries and dependencies, which are not properly tested or managed. Continuous testing across the full software supply chain is needed.
3) Not all vulnerabilities are equal - context is important. A risk-based approach should prioritize the most critical issues based on factors like impact, likelihood, and the development environment. Compliance alone does not ensure real security.
Via forensics appsecusa-nov-2013
This document summarizes a presentation about the mobile security Linux distribution Santoku Linux. It discusses how Santoku Linux was created by modifying Lubuntu to include mobile forensic and security tools from the company viaForensics. Some key tools discussed include AFLogical OSE for Android logical acquisitions, iPhone Backup Analyzer, and utilities for analyzing mobile malware samples. Real-world examples of analyzing the Any.DO task manager app and Korean banking malware are also provided.
Phu appsec13
This document discusses sandboxing untrusted JavaScript from third parties to improve security. It proposes a two-tier sandbox architecture that uses JavaScript libraries and wrappers, without requiring browser modifications. Untrusted code is executed in an isolated environment defined by policy code, and can only access approved APIs. This approach aims to mediate access between code and the browser securely and efficiently while maintaining compatibility with existing third-party scripts.
Owasp2013 johannesullrich
This document discusses how HTML5 features can be used for authentication purposes and addresses some security challenges. It describes APIs like local storage, canvas, geolocation, and notifications that could be leveraged for authentication factors like passwords, patterns, and one-time passwords. However, it also notes risks like storing sensitive data on devices, spoofing locations, and notifications not being reliable. The document advocates using HTML5 responsibly and understanding privacy and user behavior when designing authentication solutions.
Owasp advanced mobile-application-code-review-techniques-v0.2
The document discusses code review techniques for advanced mobile applications. It begins with an overview of why mobile security is important given the rise in mobile usage. It then discusses different mobile application types and architectures that can be code reviewed, including native, hybrid, and HTML5 applications. The document outlines the goals of mobile application code reviews, such as understanding the application and finding security vulnerabilities. It provides the methodology for conducting code reviews, which includes gaining access to source code, understanding the technology, threat modeling, analyzing the code, and creating automation scripts. Finally, it discusses specific vulnerabilities that may be found in Windows Phone, hybrid, Android, and iOS applications.
I mas appsecusa-nov13-v2
The document discusses research conducted by Gregg Ganley and Gavin Black at MITRE in FY13-14 on iOS mobile application security. It describes their work on a tool called iMAS (iOS Mobile Application Security) which aims to provide additional security controls and containment for native iOS applications. iMAS addresses vulnerabilities related to runtime access, device access, application access, data at rest, and threats from app stores/malware. It utilizes techniques like encrypted code modules, forced inlining, secure MDM and more to raise security levels above standard iOS but below a fully customized/rooted mobile device environment. The document outlines the motivation, capabilities and future research directions for the iMAS project.
Defeating xss-and-xsrf-with-my faces-frameworks-steve-wolf
This document discusses how to defeat cross-site scripting (XSS) and cross-site request forgery (XSRF) when using JavaServer Faces (JSF) frameworks. It covers validating user input, encoding output, and protecting view states to prevent XSS, as well as configuring JSF implementations to protect against XSRF by encrypting view states and adding tokens to URLs. The presentation emphasizes testing validation, encoding, and protection in specific JSF implementations since behaviors can differ.
Csrf not-all-defenses-are-created-equal
This document summarizes a presentation on defending against CSRF (cross-site request forgery) attacks. It discusses four main design patterns for CSRF defenses: the synchronizer token pattern, double submit cookies, challenge-response systems, and checking the referrer header. It then provides details on implementing these patterns, specifically looking at libraries and features in .NET, .NET MVC, Anticsrf, CSRFGuard, and HDIV that can help implement CSRF tokens and validation. The document covers the tradeoffs of different approaches and considerations for using them effectively on the code and server level.
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
This document provides an overview of the OWASP Broken Web Applications (OWASP BWA) project. It discusses the background and motivation for the project, describes the current status including what applications are included in the virtual machine, outlines future plans, and solicits feedback to help guide and expand the project. The goal of OWASP BWA is to provide a free, open-source virtual machine containing a variety of intentionally vulnerable web applications to aid in testing tools and techniques for finding and addressing security issues.
Appsec usa roberthansen
This document provides a summary of a presentation by Robert Hansen on the future of browser security. Hansen argues that while browser developers want to improve security and privacy, their companies' business models focused on advertising revenue prohibit them from doing so. He outlines various techniques used by advertisers and browser companies to track users against their preferences. Hansen advocates for technical controls that allow users to opt out of tracking through a "can not track" approach, rather than relying on ineffective "do not track" policies. He concludes by discussing WhiteHat Security's focus on privacy and their plans to add more security and privacy features to their Aviator browser.
Appsec usa2013 js_libinsecurity_stefanodipaola
This document summarizes Stefano di Paola's talk on security issues with JavaScript libraries. It discusses how jQuery's $() method can be considered a "sink" that executes HTML passed to it, including examples of XSS via jQuery selectors and AJAX calls. It also covers problems with JSON parsing regular expressions, AngularJS expression injection, and credentials exposed in URLs. Solutions proposed include validating all input, auditing third-party libraries, and moving away from approaches like eval() that execute untrusted code.
Appsec2013 presentation-dickson final-with_all_final_edits
(1) A study surveyed 600 software developers and found that most did not have a basic understanding of software security concepts, with 73% failing an initial survey and the average score being 59% before training. (2) However, after training, developers' understanding of key concepts increased, with some areas like cross-site scripting seeing a 20 percentage point gain. (3) The study concluded that targeted security training can improve developers' knowledge in the short-term, though retention of this knowledge may require refresher training over time.
Appsec2013 presentation
This document summarizes Bruno Gonçalves de Oliveira's talk on hacking web file servers for iOS. It introduces Bruno and his background in offensive security and discusses how iOS devices store a lot of information and mobile applications are often poorly designed and vulnerable. It provides examples of vulnerable file storage apps, outlines features and vulnerabilities like lack of encryption, authentication, XSS issues, and path traversal flaws. The document demonstrates exploits like unauthorized access to file systems on jailbroken devices and how to find vulnerable systems through mDNS queries. It concludes that mobile apps are the future but designers still do not prioritize security and there are too many apps for users to vet carefully.
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
This document discusses forensic investigations of web exploitations. It presents a scenario where a web server in a DMZ zone was exploited but logs are unavailable, so network traffic must be analyzed. Wireshark will be used to analyze a PCAP file of recorded traffic to determine what happened and find any traces of commands or malware. The document also provides information on the costs of different types of cyber attacks, how to decode HTTP requests, and discusses tools that can be used for network forensics investigations like Wireshark, tcpdump, and Xplico.
Appsec2013 assurance tagging-robert martin
The document discusses engineering software systems to be more secure against attacks. It notes that reducing a system's attack surface alone is not enough, as software and networks are too complex and it is impossible to know all vulnerabilities. It then discusses characteristics of advanced persistent threats, including that the initial attack may go unnoticed and adversaries cannot be fully kept out. Finally, it argues that taking a threat-driven perspective beyond just operational defense can help balance mitigation with detection and response.
Amol scadaowasp
The document summarizes a presentation on vulnerabilities found in SCADA systems between 2009-2013. It analyzed vulnerabilities by component, with the majority (66%) found in communication components like Modbus and DNP3 protocols. Examples of vulnerabilities are described for several devices. Real-world issues with SCADA systems are discussed like lack of authentication and patching. Recommendations are provided like auditing SCADA networks, implementing secure protocols and password policies, and keeping systems updated.
Agile sdlc-v1.1-owasp-app sec-usa
This 3-page document discusses the real-world challenges of implementing an agile software development lifecycle (SDLC) approach from the perspectives of Chris Eng and Ryan O'Boyle. It was presented at the OWASP AppSec USA conference on November 20, 2013 and focuses on practical lessons learned and best practices for incorporating security throughout an agile SDLC.
Vulnex app secusa2013
This document outlines a presentation given by Simón Roses Femerling on software security verification tools. It discusses BinSecSweeper, an open source tool created by VulnEx to scan binaries and check that security best practices were followed in development. The presentation covers using BinSecSweeper to verify in-house software, assess a company's software security posture, and compare the security of popular browsers. Examples of plugin checks and reports generated by BinSecSweeper are also provided.
More Related Content
More from drewz lin
Web security-–-everything-we-know-is-wrong-eoin-keary
1) Web application security is often approached incorrectly, focusing too much on annual penetration tests and compliance, rather than ongoing monitoring and prevention through the development process.
2) Many vulnerabilities are introduced through third party libraries and dependencies, which are not properly tested or managed. Continuous testing across the full software supply chain is needed.
3) Not all vulnerabilities are equal - context is important. A risk-based approach should prioritize the most critical issues based on factors like impact, likelihood, and the development environment. Compliance alone does not ensure real security.
Via forensics appsecusa-nov-2013
This document summarizes a presentation about the mobile security Linux distribution Santoku Linux. It discusses how Santoku Linux was created by modifying Lubuntu to include mobile forensic and security tools from the company viaForensics. Some key tools discussed include AFLogical OSE for Android logical acquisitions, iPhone Backup Analyzer, and utilities for analyzing mobile malware samples. Real-world examples of analyzing the Any.DO task manager app and Korean banking malware are also provided.
Phu appsec13
This document discusses sandboxing untrusted JavaScript from third parties to improve security. It proposes a two-tier sandbox architecture that uses JavaScript libraries and wrappers, without requiring browser modifications. Untrusted code is executed in an isolated environment defined by policy code, and can only access approved APIs. This approach aims to mediate access between code and the browser securely and efficiently while maintaining compatibility with existing third-party scripts.
Owasp2013 johannesullrich
This document discusses how HTML5 features can be used for authentication purposes and addresses some security challenges. It describes APIs like local storage, canvas, geolocation, and notifications that could be leveraged for authentication factors like passwords, patterns, and one-time passwords. However, it also notes risks like storing sensitive data on devices, spoofing locations, and notifications not being reliable. The document advocates using HTML5 responsibly and understanding privacy and user behavior when designing authentication solutions.
Owasp advanced mobile-application-code-review-techniques-v0.2
The document discusses code review techniques for advanced mobile applications. It begins with an overview of why mobile security is important given the rise in mobile usage. It then discusses different mobile application types and architectures that can be code reviewed, including native, hybrid, and HTML5 applications. The document outlines the goals of mobile application code reviews, such as understanding the application and finding security vulnerabilities. It provides the methodology for conducting code reviews, which includes gaining access to source code, understanding the technology, threat modeling, analyzing the code, and creating automation scripts. Finally, it discusses specific vulnerabilities that may be found in Windows Phone, hybrid, Android, and iOS applications.
I mas appsecusa-nov13-v2
The document discusses research conducted by Gregg Ganley and Gavin Black at MITRE in FY13-14 on iOS mobile application security. It describes their work on a tool called iMAS (iOS Mobile Application Security) which aims to provide additional security controls and containment for native iOS applications. iMAS addresses vulnerabilities related to runtime access, device access, application access, data at rest, and threats from app stores/malware. It utilizes techniques like encrypted code modules, forced inlining, secure MDM and more to raise security levels above standard iOS but below a fully customized/rooted mobile device environment. The document outlines the motivation, capabilities and future research directions for the iMAS project.
Defeating xss-and-xsrf-with-my faces-frameworks-steve-wolf
This document discusses how to defeat cross-site scripting (XSS) and cross-site request forgery (XSRF) when using JavaServer Faces (JSF) frameworks. It covers validating user input, encoding output, and protecting view states to prevent XSS, as well as configuring JSF implementations to protect against XSRF by encrypting view states and adding tokens to URLs. The presentation emphasizes testing validation, encoding, and protection in specific JSF implementations since behaviors can differ.
Csrf not-all-defenses-are-created-equal
This document summarizes a presentation on defending against CSRF (cross-site request forgery) attacks. It discusses four main design patterns for CSRF defenses: the synchronizer token pattern, double submit cookies, challenge-response systems, and checking the referrer header. It then provides details on implementing these patterns, specifically looking at libraries and features in .NET, .NET MVC, Anticsrf, CSRFGuard, and HDIV that can help implement CSRF tokens and validation. The document covers the tradeoffs of different approaches and considerations for using them effectively on the code and server level.
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
This document provides an overview of the OWASP Broken Web Applications (OWASP BWA) project. It discusses the background and motivation for the project, describes the current status including what applications are included in the virtual machine, outlines future plans, and solicits feedback to help guide and expand the project. The goal of OWASP BWA is to provide a free, open-source virtual machine containing a variety of intentionally vulnerable web applications to aid in testing tools and techniques for finding and addressing security issues.
Appsec usa roberthansen
This document provides a summary of a presentation by Robert Hansen on the future of browser security. Hansen argues that while browser developers want to improve security and privacy, their companies' business models focused on advertising revenue prohibit them from doing so. He outlines various techniques used by advertisers and browser companies to track users against their preferences. Hansen advocates for technical controls that allow users to opt out of tracking through a "can not track" approach, rather than relying on ineffective "do not track" policies. He concludes by discussing WhiteHat Security's focus on privacy and their plans to add more security and privacy features to their Aviator browser.
Appsec usa2013 js_libinsecurity_stefanodipaola
This document summarizes Stefano di Paola's talk on security issues with JavaScript libraries. It discusses how jQuery's $() method can be considered a "sink" that executes HTML passed to it, including examples of XSS via jQuery selectors and AJAX calls. It also covers problems with JSON parsing regular expressions, AngularJS expression injection, and credentials exposed in URLs. Solutions proposed include validating all input, auditing third-party libraries, and moving away from approaches like eval() that execute untrusted code.
Appsec2013 presentation-dickson final-with_all_final_edits
(1) A study surveyed 600 software developers and found that most did not have a basic understanding of software security concepts, with 73% failing an initial survey and the average score being 59% before training. (2) However, after training, developers' understanding of key concepts increased, with some areas like cross-site scripting seeing a 20 percentage point gain. (3) The study concluded that targeted security training can improve developers' knowledge in the short-term, though retention of this knowledge may require refresher training over time.
Appsec2013 presentation
This document summarizes Bruno Gonçalves de Oliveira's talk on hacking web file servers for iOS. It introduces Bruno and his background in offensive security and discusses how iOS devices store a lot of information and mobile applications are often poorly designed and vulnerable. It provides examples of vulnerable file storage apps, outlines features and vulnerabilities like lack of encryption, authentication, XSS issues, and path traversal flaws. The document demonstrates exploits like unauthorized access to file systems on jailbroken devices and how to find vulnerable systems through mDNS queries. It concludes that mobile apps are the future but designers still do not prioritize security and there are too many apps for users to vet carefully.
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
This document discusses forensic investigations of web exploitations. It presents a scenario where a web server in a DMZ zone was exploited but logs are unavailable, so network traffic must be analyzed. Wireshark will be used to analyze a PCAP file of recorded traffic to determine what happened and find any traces of commands or malware. The document also provides information on the costs of different types of cyber attacks, how to decode HTTP requests, and discusses tools that can be used for network forensics investigations like Wireshark, tcpdump, and Xplico.
Appsec2013 assurance tagging-robert martin
The document discusses engineering software systems to be more secure against attacks. It notes that reducing a system's attack surface alone is not enough, as software and networks are too complex and it is impossible to know all vulnerabilities. It then discusses characteristics of advanced persistent threats, including that the initial attack may go unnoticed and adversaries cannot be fully kept out. Finally, it argues that taking a threat-driven perspective beyond just operational defense can help balance mitigation with detection and response.
Amol scadaowasp
The document summarizes a presentation on vulnerabilities found in SCADA systems between 2009-2013. It analyzed vulnerabilities by component, with the majority (66%) found in communication components like Modbus and DNP3 protocols. Examples of vulnerabilities are described for several devices. Real-world issues with SCADA systems are discussed like lack of authentication and patching. Recommendations are provided like auditing SCADA networks, implementing secure protocols and password policies, and keeping systems updated.
Agile sdlc-v1.1-owasp-app sec-usa
This 3-page document discusses the real-world challenges of implementing an agile software development lifecycle (SDLC) approach from the perspectives of Chris Eng and Ryan O'Boyle. It was presented at the OWASP AppSec USA conference on November 20, 2013 and focuses on practical lessons learned and best practices for incorporating security throughout an agile SDLC.
Vulnex app secusa2013
This document outlines a presentation given by Simón Roses Femerling on software security verification tools. It discusses BinSecSweeper, an open source tool created by VulnEx to scan binaries and check that security best practices were followed in development. The presentation covers using BinSecSweeper to verify in-house software, assess a company's software security posture, and compare the security of popular browsers. Examples of plugin checks and reports generated by BinSecSweeper are also provided.
More from drewz lin (20)
Web security-–-everything-we-know-is-wrong-eoin-keary
Web security-–-everything-we-know-is-wrong-eoin-keary
Owasp advanced mobile-application-code-review-techniques-v0.2
Owasp advanced mobile-application-code-review-techniques-v0.2
Defeating xss-and-xsrf-with-my faces-frameworks-steve-wolf
Defeating xss-and-xsrf-with-my faces-frameworks-steve-wolf
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
Chuck willis-owaspbwa-beyond-1.0-app secusa-2013-11-21
Appsec2013 presentation-dickson final-with_all_final_edits
Appsec2013 presentation-dickson final-with_all_final_edits
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
Appsec 2013-krehel-ondrej-forensic-investigations-of-web-exploitations
Deliberate practice agile2012_alex_aitken
- 1. Deliberate Practice Becoming a better programmer Alex Aitken @alexaitken <EPAM> blog.thoughtcorp.com alexaitken.com Thursday, 16 August, 12
- 2. Agenda Define Deliberate Practice One Per Week FizzBuzz Randoori Object Calisthenics Demo How do you start? Thursday, 16 August, 12
- 3. Deliberate Practice Thursday, 16 August, 12
- 4. One Hour Per Week Thursday, 16 August, 12
- 7. calisthenics Gymnastic exercises to achieve bodily fitness and grace of movement Thursday, 16 August, 12
- 8. Object Calisthenics - Jeff Bay • Use only one level of indentation per method • Don’t use the else keyword • Wrap all primitives and strings • Use only one dot per line • Don’t abbreviate • Keep all entities small • Don’t use any classes with more than two instance variables • Use first-class collections • Don’t use any getters/setters/properties Thursday, 16 August, 12
- 9. Object Calisthenics • Use only one level of indentation per method • Don’t use the else keyword • Wrap all primitives and strings • Use only one dot per line • Don’t abbreviate • Keep all entities small • Don’t use any classes with more than two instance variables • Use first-class collections • Don’t use any getters/setters/properties Thursday, 16 August, 12
- 10. Demo Thursday, 16 August, 12
- 11. Debrief Thursday, 16 August, 12
- 12. How do you start? Thursday, 16 August, 12
- 13. Thursday, 16 August, 12
- 14. References Object Calisthenics http://www.markhneedham.com/blog/2008/11/06/object-calisthenics-first-thoughts/ Katas http://codingdojo.org/cgi-bin/wiki.pl?KataCatalogue Doing practice with your team http://blog.thoughtcorp.com/2011/07/18/practice-built-in/ Constraint exercise https://gist.github.com/3355541 Thursday, 16 August, 12
- 15. Credits http://www.flickr.com/photos/ajc1/2799103829/ http://www.flickr.com/photos/totalaldo/503335275/ http://www.flickr.com/photos/magnuz/4111206/ http://www.flickr.com/photos/adam_jones/3793605961/ http://www.flickr.com/photos/paulmoody/643667931/ Thursday, 16 August, 12
- 16. Please fill out surveys Deliberate Practice Alex Aitken Aug 16 2012 Thank you Thursday, 16 August, 12