The document describes the format of a coderetreat event with 90 coders and 2200 passionate software developers. The format involves periods of deep coding practice and challenge, receiving feedback without pressure, and experimenting freely. Sessions involve 45 minutes of coding, 10 minutes of retrospectives, and breaks in between. Coding tasks follow principles of passing all tests, clear intent, no duplication, and no superfluous parts. Code is deleted after each session and paired programming is used. Variations on the tasks are described. The Game of Life simulation is provided as an example coding task.
This document demonstrates how the oplog in MongoDB replica sets works by replicating operations from the primary to secondaries. It shows insert, update, remove operations on a collection on the primary and then verifies that the same operations have been replicated to the oplog and applied on a secondary by finding the same document changes. It also shows getMore commands from secondaries tailing the oplog on the primary to stay up to date as new operations are applied.
Python type hints allow annotating function and variable types in Python code. They were introduced in PEP 484 for Python 3.5 and provide documentation of types without runtime enforcement. Using type hints and tools like mypy enables type checking of code without execution, improving code quality and readability. They help with code completion, refactoring Python 2 code to Python 3, and catching type errors during development.
The document discusses a presentation on the benefits of type hints in Python. It provides an outline of the presentation which includes an introduction to type hints, how to use type hints, and the benefits of type hints. Some key benefits mentioned are improved code completion, the ability to catch type errors without running code, and using type hint tools for static type analysis.
Build a RESTful API with the Serverless Frameworkmasahitojp
The document discusses how to build a RESTful API using the Serverless framework on AWS. It introduces the Amazon API Gateway for creating API endpoints and AWS Lambda for hosting backend functions. The Serverless framework simplifies deploying Lambda functions by packaging code and dependencies, testing functions locally, and deploying with a single command. It also addresses challenges like installing Python libraries and supporting non-Python modules through Docker.
The document discusses using Python with AWS Lambda. It introduces serverless frameworks like AWS Lambda, Google Cloud Functions, and Microsoft Azure Functions. It then focuses on using Python with AWS Lambda, including how to package dependencies, deploy code, and leverage the Serverless framework to simplify deployments. Logging to CloudWatch Logs and adding unit tests are also covered.
The speaker discussed the benefits of type hints in Python. Type hints allow specifying the expected types of function parameters and return values, improving code readability, enabling code completion in editors, and allowing static type checking tools to analyze the code for type errors. The speaker demonstrated how to write type hints according to PEP 484 and PEP 526 standards and how to retrieve type information. Tools like Mypy were presented for doing static type analysis to catch errors. Using type hints and type checkers in continuous integration was recommended to catch errors early when collaborating on projects. The speaker concluded by explaining how using type hints made it easier for their team to port code from Python 2 to Python 3.
Pyston is a JIT-based implementation of Python 2.7 built using LLVM. It compiles Python code to LLVM IR for optimization and execution via LLVM's JIT engine. Current benchmarks show recursion sees benefits from LLVM JIT, while loops do not, and the implementation is missing major parts of the Python language. Future versions aim to add exceptions, classes, arguments and more.
This document discusses Play! Scala, a framework that allows building web applications in Scala on the Play! platform. It can use Scala instead of Java for the Play! framework. Anorm is used to interact with databases instead of JPA/Hibernate. Play! Scala applications can be deployed to PaaS platforms like Heroku and CloudBees. The document provides links for documentation, mailing lists and the GitHub repository for further information.
18. Probably since it needs more
bug fixes and documentation
than Play
1.2.x that is 3 years old and well
documented.
Gia
http://groups.google.com/group/play-framework/
browse_thread/thread/615888c1ed2fc4da?pli=1