# Marathon's book
---


Configurations and ways to fire up the scripts

## Go

```sh
$ export PATH=$PATH:/opt/go/bin
$ export GOPATH=$HOME/Documents/golang
$ export GOROOT=/opt/go

$ go run filename.go

```

## Java

```sh
$ export JAVA_HOME=/usr/local/jdk1.8.0_111
$ export PATH=$JAVA_HOME/bin:$PATH


$ javac filename.java
$ java filename
```


License
----

MIT

Source code is your BABY!

So keep it clean, consistent and beautiful. When I say beautiful,
it really means beautiful. If your code looks beautiful, then it 
would be easy for others to read and understand it. If you will 
keep changing coding rules everyday, then after few days you,
yourself would not be able to read and understand the code 
written by you.


Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

references
tutorials point
python std




# Marathon's book
---


Configurations and ways to fire up the scripts

## Go

```sh
$ export PATH=$PATH:/opt/go/bin
$ export GOPATH=$HOME/Documents/golang
$ export GOROOT=/opt/go

$ go run filename.go

```

## Java

```sh
$ export JAVA_HOME=/usr/local/jdk1.8.0_111
$ export PATH=$JAVA_HOME/bin:$PATH


$ javac filename.java
$ java filename
```


Acknowledgements
----

 - Bjarki Ágúst Guðmundsson : Some awesome algorithms of this book were created by him. 




references
tutorials point
python std




Add first version acknowledments Bjarki :+1:
Add first version acknowledments Bjarki :+1:
