Merge branch 'dev' of git.gvk.idi.ntnu.no:jobnb/cloudproject into dev

README.md

@@ -13,3 +13,52 @@ The endpoint can be reached at /altocumulus/v1/turer
 ## Tur
 This endpoint can be reached at /altocumulus/v1/tur/524081f9b8cb77df150007fa.
 The string at the end is the id of the trip and can be replaced with any other valid id gotten from for example the turer endpoint
+
+brief description of the original project plan, and what has and has not been achieved/changed in the final product
+
+ ######Reflection of what went well and what went wrong with the project
+    In our project, we tried many different ideas and techniques in GO, in group working,
+     and other best pratices. This means that we as programmers, and team members
+     have developed at pace with our project. 
+     
+     We could have improved in many ways, as you often can. Out primary point of improvement
+     we imagine must be organization of tasks, even more professional workflow, and of course
+     writing better, more consistent, conscise and best+practice oriented code.
+ 
+ ######Reflection on the hard aspects of the project
+    There are always challenges to be overcome during any task. In this project, we encountered many
+    The first of our problems, was that Twitter was hesitant to give us a developer account;
+    which thrashed our original idea of having an IT-security tiwtter based API.
+    
+    However, we found another project and ended up creating an API to accumulate walking route
+    data with weather data, to see what kind of weather you are to expect when going that route
+    on a given day.
+    
+    What made this difficult was firstly, that we had very few API calls. This, however
+    was mitigated by one of our group members gaining developer access.
+    
+    The second thing We also struggled with, was converting XML to JSON. This worked out in the end, 
+    as we started to develop procedures to ectract the data and fields that we needed
+    from the XML file.
+    
+    Lastly we struggled with getting a good test coverage, as we worte most of the code
+    before we wrote the tests. 
+
+ ######What new has the group learned
+    We have learned to choose an Idea and stick with it, to the end. We have also learned more
+    about the challenges faced by developers in their adily lives, and have therefore
+    understood why we do things a certain way. As well as why we use ceratin workflows.
+    
+    An couple of exaples on this would be:
+     * Using branches correctly to be able to develop without destroying someone
+      elses or your own work.
+     * Using good ommenting to understand what other team members have done, and also allow
+     them to understand your code
+     * Writing tests before the programming of the project actually strts in order
+     to both get good test coverage, and setting a specification
+     
+     
+
+ ######Total work hours dedicated to the project cumulatively by the group
+ 
+    TBA
\ No newline at end of file