What do we learn from this demo? (e.g. this demo showcases feature X, etc)
What are the models used in this demo? (with links to the online documentation)
- Model: i
- Router: xyz
| import json | |
| from sys import argv | |
| if len(argv) < 2: | |
| exit("usage: {} filename".format(argv[0])) | |
| filename = argv[1] | |
| f = open(filename) | |
| line = f.readline() | |
| f.close() |
| #!/usr/bin/env python | |
| import os | |
| import itertools | |
| from jinja2 import Environment, FileSystemLoader | |
| PATH = os.path.dirname(os.path.abspath(__file__)) | |
| TEMPLATE_ENVIRONMENT = Environment( | |
| autoescape=False, | |
| loader=FileSystemLoader(PATH), | |
| trim_blocks=False) |
Published: 24 Jul 2007.
By: Simone Busoli
Inversion of Control (IoC) and Dependency Injection (DI) are two related practices in software development which are known to lead to higher testability and maintainability of software products. While some people employ them daily in their work, many others still don't know much about them, mostly because they require in the former a shift in the usual thinking process.
This article introduces these notions in a simple and affordable fashion, with a real example which evolves step by step to take advantage from IoC and DI, leveraging the features offered by an open source framework called Castle Project.
Refer to https://clang-omp.github.io/ .
We need to install something:
brew install libiomp
brew install clang-ompThen we need to set the environment:
Visit my blog or connect with me on Twitter
git init
or
| # If you already have a webserver running you most likely won't be able to get GitLab | |
| # woring on ports 80 and 443. Port 22 should work because we change the default SSH | |
| # port on the host during server provisioning. | |
| HTTP_PORT=8080 | |
| HTTPS_PORT=8443 | |
| SSH_PORT=22 | |
| # Install Docker (don't use Ubuntu's repositories, they're out of date). | |
| wget -qO- https://get.docker.com/ | sudo sh |
Custom recipe to get OS X 10.11 El Capitan running from scratch, setup applications and developer environment. This is very similar (and currently mostly the same) as my 10.10 Yosemite setup recipe (as found on this gist https://gist.github.com/kevinelliott/0726211d17020a6abc1f). Note that I expect this to change significantly as I install El Capitan several times.
I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. On average, I reinstall each computer from scratch every 6 months, and I do not perform upgrades between distros.
This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.
You are encouraged to fork this and modify it to your heart's content to match your own needs.