Mimir:Spring 2018 Orevaoghene Omu Log

From Openitware
Jump to: navigation, search

Week Ending February 6, 2018

  • After the grad students meeting after class, the task was to decide which chapter of the textbook we were going to work on.
  • The group was to work on chapter 4 but Patrick spoke with Prof. Jonas who said we should check out the first 3 chapters first before jumping to chapter 4.
  • Read through the first chapter and see if the information there is good enough or needs to be edited.
  • Try complete lab1.

I don't think I or most of us fully understand the project required from us.

Week Ending February 13, 2018


We didn't meet in class but we met on slack and the task was to start reviewing chapter one.

  • We review chapter one and came out with outlines. Illya made the first while we reviewed those outline.
  • On slack we divided ourselves into groups, groups were basically grouped by image creating, developing code examples, writing, editing. I joined the editing group and I'll be carrying out fact checking on images, text and codes before they are posted.

Start looking at the work already being developed, and also come up with what to do for next week.


The major concern of the group was writing organization, such as how and when each group does what so as to avoid content mismatch (for example, codes not following write-up).

Week Ending February 20, 2018

  • The Grad students met after the class on the 14th of Feb, we discussed deliverables. I'm to carry out fact checking on the images designed by Patrick/Sharmilla, and also on the document written for Chapter 1. I'll also make sure the codes wriiten by Raghava/Arjun are correct.
  • We decided to created a shared Word document for collaborative writing and editing. Andry created the the document and shared with everyone.
  • Looked into the images created on some of the different types of programming languages. Cited examples were Functional, Imperative, Logical, OOP, and Procedural. I was able to verify that all languages were grouped correctly.

Keep looking for updated content on the shared document and collaborate with pairs on slack.

  • Major concern was that we had a lot of topics but just three people doing the writing. So we hope to meet after class to split the writing, so we see how everyone could contribute to writing.

Week Ending February 27, 2018


We met in class the previous week and decided everyone was going to get involved in the writing and not just leave it to the writing group. I and Bridget chose to write chapter 1. Arjun and Raghava were going to write chapter 3, Patrick and Sharmilla were to write chapter 2, then Ilya and Andry were writing chapter 4.


I started researching into the topics, bookmarked sites I was going to use in getting points to write my topics.


Look to create outlines for my topics.


No concerns for now.

Week Ending March 6, 2018

  • Create outlines for my topics
  • Start writing my topics in Chapter 1.


I was able to create the outlines for the topics which I chose, I started writing on the topics (as my first draft) in my MS Word document


Complete my draft and push the completed work so far to the textbook.


Still no concerns.

Week Ending March 20, 2018

  • Keep reading up books related to the topics I chose to write in Chapter 1.
  • Complete my draft and push to the textbook.

I was able to complete two topics out of the 4 topics I choose. One of the topic already had a short content but just summary. I modified it by adding more content.

  • Finish up writing chapter 1 by next week.
  • Start fact checking from chapter one if completed by next week. I and Bridget are almost done.

I got confused about the difference between "Where Did Programming Languages Come From?" and "How did they Evolve", so I skipped writing the first part till I clarify my concerns. I'm hoping to take that part out or leave it as a summary of the latter part.

Week Ending March 27, 2018


Keep reading/researching on "how programming languages are made" and "where programming languages came from"


Drafted more on How programming languages are made, but yet to complete it.

  • Finish up my draft on the last 2 section assigned to me.
  • Come up with keywords.

The section on Where programming languages came from is giving me a tough time because most of what I can think of on organizing it has been written in History of Programming languages. I might not have much to write in this section.

Week Ending April 3, 2018

  • Finish my last 2 chapters and maybe publish on Mimir.
  • Review the sections we completed with Bridget or fix a date to do that.

Completed writing all sections assigned to me in my draft book.

  • Publish my completed write-ups and move on to other tasks. We also have to fact check other chapters.
  • Ask other teams for sections they completed to fact-check.

None for now.

Week Ending April 10, 2018


Transfer my finalized write up for my MS-Word draft to the text book.


Finished writing the following sections:

  • Where Did Programming Languages Come From?
  • How Programming Languages Are Made: (From a Software Perspective)
  • Implementation
  • Organize my references properly.
  • Break the good and sad news to the team that we might have to re-write/structure the book properly.

Met with Prof. Jonas and he expressed dissatisfaction on the way we were writing the team. The team might not be happy with the news as we have gone a long way in writing the book, but we have to organize it better so it could be an effective reference textbook for students.

Week Ending April 17, 2018


To make the book more like a textbook we formed a new group. I and Bridget decided to work on the structure and outlines for the book. I and Bridget created outlines for Chapter 1 and designed a writing style.


We structured the outline for Chapter to, and added these outlines.

  • Introduction
  • What you should learn in this chapter
  • What is a programming language
  • History of programming languages and paradigms
  • Modern refinements
  • What makes a good programming language
  • How languages are made
  • Benefits of programming languages
  • Why learn a language
  • Who can use programming languages
  • Summary
  • Key terms
  • References

We also added this guideline: "All keywords should be in bold, the quote should be italicized, and all code should be in a snippet. All references should be within the text with a number corresponding to the URL at the bottom. Please try and keep the references in each section and we will organize them in order at the bottom."


Come up with outline for Chapter 2.


No corcern.

Week Ending April 24, 2018

  • Worked on Structure of Chapter 2 and 3 with Bridget.
  • Reviewed write-up on Chapter 1.
  • We told the writing team to remove the Grammar section. It was introduced in Chapter 1 and there is a whole section for it. There was no need introducing it again in Chapter 2.
  • We added data structure concepts to Chapter 2's outline
    • Sequences
    • Arrays
    • Queues
    • Stacks
    • Trees
    • Graphs
    • Hash
    • List

We added the following outlines to Chapter 3

  • Advantages of Imperative programming
  • Understanding Memory Allocations in Imperative programming
    • Static Allocation
    • Stack-based Allocation
    • Heap-based Allocation (Dynamic Memory Allocation)
    • Hybrid Allocation
  • Work on Chapter 4 and review worked done by the writing team in chapter 2.
  • Add my references for the sections in Chapter 1 I wrote that was maintained.

There was no write up on Chapter 3

Week Ending May 1, 2018

  • Add my references and keynotes to sections I wrote and was kept by the new writing team.
  • Come up with outlines for Chapter 4 if the writing team and Arjun/Rag's team can finalize chapter 3.
  • Review Chapter 3 if writing team completes it.
  • Started inputting my references and looked at what chapter 3 is looking like.
  • Started coming up with outlines for Chapter 4
  • Finish and post Chapter 4's outlines.
  • Wrap up references.
  • Busy week, couldn't do much.

Week Ending May 8, 2018

  • Upload written outlines for Chapter 4.
  • Go through textbook and wrap up anything that needs to be wrapped up.
  • Added more outlines from I and Bridget to Chapter 4.
    • What are functions
    • Advantages
      • Clear and clean code
      • Modularity
      • Resuability
      • Low coupling
      • Any other advantage the writing team wishes to write on
    • Types
      • Predefined functions
      • User-defined functions
    • concepts
      • Call by value
      • Call by reference
      • Function overloading
      • Function Overiding
      • Pure functions
  • Also moved contents up and down for better flow.

None, as it's the last week.