first two session ideas

BOOKS.md

+# Software development
+
+
+# Algorithms
+
+
+# Writing
\ No newline at end of file

LINKS.md

+# Good practice
+
+- [Keeping a changelog](https://keepachangelog.com/en/1.0.0/)
\ No newline at end of file

README.md

@@ -4,23 +4,34 @@ A repo describing the operations of the Marine Engineering code review sessions.
 
 ## What
 
-A weekly session where we gather to share out problems with code. 
+A weekly session where we gather to share out problems with code and broaden our understanding of concepts in software engineering.
 
 ## Why
 
 Coding is easier when your problems are shared. This session can also act as a code review process for those preparing to share code for papers, theses or commercial practice.
 
+Sharing coding problems and strategies is a good way of working through [impostor syndrome](https://stackoverflow.blog/2020/02/10/hello-world-curing-imposter-syndrome-by-embracing-the-suck/).
+
 ## How
 
 1. Weekly session to physically gather and share problems. We'll have a specific theme to talk about for 5 minutes at the start of every meeting. 
 2. Use of this repository to gather useful resources
+    1. Links in ```LINKS.md```
+    2. Good books in ```BOOKS.md```
+    3. The ```session_notes``` folder has markdown documents 
 
 # Weekly session
 
-Vote on when you would like the weekly session to be held; https://vevox.app/m#/139064584
+To be held on Mondays at 1400 somewhere on Boldrewood Campus. The format will be a short 5-10 minute presentation on a topic in software engineering before everyone splits into groups to start going through problems that they are having.
 
 ## Dates
 
-| Date | Theme      | Sources |
-|------|------------|---------|
-| ??   | Commenting |         |
+| Date  | Theme           | Location |
+|-------|-----------------|----------|
+| 24/02 | Code commenting | 176/2013 |
\ No newline at end of file
+| 03/03 | Big Oh notation | 176/2013 |
+
+
+# Contributing
+
+Please contribute any ideas you have. We want to learn more. Ideas for session themes, good resources and more are all welcome.
\ No newline at end of file

session_notes/big_o_notation.md

+# Big O notation
+
+Big O notation is a way of analysing algorithms. 
+
+## Sources
+
+1. p31, Algorithm Analysis - The Algorithm Design Manual, Steven S. Skiena
+1. p177, Algorithm Speed - The Pragmatic Programmer
\ No newline at end of file

session_notes/comments.md

+# Comments
+
+![Code quality](https://i.redd.it/btd5aebzr5h01.jpg)
+
+Commenting your code is important if you want other people to use it after you. This does happen in academia and I'm told it happens in industry all the time.
+
+> English is another programming language. (From the It's all writing section)
+
+## Sources
+
+1. Chapter 4, Clean code by Robert C. Martin.
+1. It's all writing, The Pragmatic Programmer by Hunt and Thomas.