[Japanese] Skinny Framework で始める Scala #jjug_ccc #ccc_r24Kazuhiro Sera
English version is here: http://www.slideshare.net/seratch/jjug-ccc-2014springeng
http://www.java-users.jp/?page_id=1048#R2-4
[Japanese] Skinny Framework で始める Scala #jjug_ccc #ccc_r24Kazuhiro Sera
English version is here: http://www.slideshare.net/seratch/jjug-ccc-2014springeng
http://www.java-users.jp/?page_id=1048#R2-4
This document discusses various technologies used in the DevelopersIO CAFE platform, including AWS services like Lambda, API Gateway, DynamoDB, Step Functions, and Auth0 for authentication. It provides examples of building APIs with Lambda and API Gateway, using layers to share code between functions, and storing data in DynamoDB. The platform utilizes serverless architecture with continuous delivery via CodePipeline and integrates SaaS services through APIs.
The document appears to be a collection of image URLs and code snippets without much context. It includes 10 Flickr image URLs, some text about different types of testing, and two short code snippets - one containing comma separated numbers and letters, and the other showing a symbol and number. No overall purpose or meaning is clear from the limited information provided.
The document discusses test-driven development (TDD) and common smells or issues that can arise when practicing TDD. It notes that TDD aims to increase code quality by writing tests before code, but that tests can become overly complex or fail to adequately test the code. The document suggests some heuristics to address these potential problems with TDD, such as keeping tests simple, focusing tests on interfaces, and refactoring tests along with code.
The document outlines the schedule and topics for a Test Driven Development Boot Camp (TDDBC) held on September 26, 2011. The camp schedule includes sessions on TDD, BDD, Jenkins, and heuristics. Additional details are provided on the camp website.
The document discusses integrating Trac and Jenkins for continuous integration. It provides an agenda that outlines the history of using version control systems like CVS and SVN with Trac from 2010 to 2011, and how JenkinsCI was introduced in 2011 for continuous integration with tools like Maven, JUnit, and version control systems like Mercurial. The document also compares features of Trac, Google Code, and Trac/Kanon.