tobiasoberrauch

# Technology
Angular 

# Create new app
ng new frontend --directory=./frontend --interactive=false --routing=true --style=scss --packageManager=yarn

# Start app
yarn start

tobiasoberrauch

tobiasoberrauch

Arkans-MacBook-Pro:word-vector-service tobiasoberrauch$ now
> Deploying ~/Repositories/tobiasoberrauch/word-vector-service under tobias.oberrauch@gmx.de
> https://word-vector-service-osrvnzchvh.now.sh [in clipboard] (bru1) [5s]
> Building…
> ▲ docker build
Sending build context to Docker daemon 13.31 kBkB
> Step 1/14 : FROM python:3.6-jessie
>  ---> 11aa3556fb90
> Step 2/14 : MAINTAINER Tobias Oberrauch "tobias.oberrauch@tob.ag"
>  ---> Using cache

tobiasoberrauch

Documentation-Driven Development

The philosophy behind Documentation-Driven Development is a simple: from the perspective of a user, if a feature is not documented, then it doesn't exist, and if a feature is documented incorrectly, then it's broken.

• Document the feature first. Figure out how you're going to describe the feature to users; if it's not documented, it doesn't exist. Documentation is the best way to define a feature in a user's eyes.
• Whenever possible, documentation should be reviewed by users (community or Spark Elite) before any development begins.
• Once documentation has been written, development should commence, and test-driven development is preferred.
• Unit tests should be written that test the features as described by the documentation. If the functionality ever comes out of alignment with the documentation, tests should fail.
• When a feature is being modified, it should be modified documentation-first.
• When documentation is modified, so should be the tests.

tobiasoberrauch

xdebug.auto_trace=1
;;Type: boolean, Default value: 0
;;When this setting is set to on, the tracing of function calls will be enabled just before the script is run. This makes it possible to trace code in the auto_prepend_file.

xdebug.cli_color=1
;;Type: integer, Default value: 0, Introduced in Xdebug 2.2
;;If this setting is 1, Xdebug will color var_dumps and stack traces output when in CLI mode and when the output is a tty. On Windows, the ANSICON tool needs to be installed.
;;If the setting is 2, then Xdebug will always color var_dumps and stack trace, no matter whether it's connected to a tty or whether ANSICON is installed. In this case, you might end up seeing escape codes.

;xdebug.collect_assignments=0

tobiasoberrauch

(function(){

    var Cache = function() {
        var data = [];
    };
    Cache.prototype = {
        set: function(key, value) {
            this.data[key] = value;
        },
        get: function(key) {

tobiasoberrauch

Whoops, looks like something went wrong.

1/1RuntimeException: An error occurred while executing the command '/usr/local/bin/bower' 'list' '--map'. The error was: "node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
TypeError: Object # has no method 'tmpDir'
at Object. (/usr/local/lib/node_modules/bower/node_modules/update-notifier/node_modules/configstore/configstore.js:13:53)
at Module._compile (module.js:441:26)
at Object..js (module.js:459:10)
at Module.load (module.js:348:32)

tobiasoberrauch

{
   "name": "symfony/framework-standard-edition",
   "description": "The \"Symfony Standard Edition\" distribution",
   "autoload": {
      "psr-0": {
         "": "src/"
      }
   },
   "require": {
      "php": ">=5.3.3",

tobiasoberrauch

Problem 1
    - Conclusion: don't install symfony/symfony v2.1.9
    - Conclusion: don't install symfony/symfony v2.1.8
    - Conclusion: remove symfony/symfony v2.1.7
    - Conclusion: don't install symfony/symfony v2.1.7
    - Conclusion: don't install symfony/symfony v2.1.6
    - Conclusion: don't install symfony/symfony v2.1.5
    - Conclusion: don't install symfony/symfony v2.1.4
    - Conclusion: don't install symfony/symfony v2.1.3
    - Conclusion: don't install symfony/symfony v2.1.2

tobiasoberrauch

var robots	= new Array();



//FightCode can only understand your robot
//if its class is called Robot
var Robot = function(robot) {
};

Robot.prototype.start			= function( ev ){