Skip to content
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.

IOP Research Doc #573

Merged
merged 5 commits into from
Jan 5, 2020
Merged

IOP Research Doc #573

merged 5 commits into from
Jan 5, 2020

Conversation

oswinso
Copy link
Contributor

@oswinso oswinso commented Nov 1, 2019

Description

So, to my knowledge we've kind of just ignored the IOP part of the challenge since like forever (I searched through all git history for the words IOP and nothing showed up. Maybe we used to before moving to github, but like that's way too long ago and doesn't count). We decided to evaluate whether or not it would be worth doing IOP, and so here is a research doc that summarizes what I have found about my IOP, and my thoughts on whether I think we should do it or not.

Link to doc (Please don't try and read a markdown file from the diff)

This PR does the following:

  • Adds a research doc for IOP to the repository

Fixes #554

Self Checklist

  • I have formatted my code using make format
  • I have tested that the new behaviour works

@oswinso
Copy link
Contributor Author

oswinso commented Nov 1, 2019

Oh no #130 (TIL this was is a 3 year old issue) comes to bite us back.

@JasonGibson274
Copy link
Contributor

We should not buy an software for this. That's not worth the money at all.

Other notes, as much as I am entertained by the tenor of this document, what level of professionalism should be in these documents? I am generally okay with whatever I just want a consistent standard. This reads a lot like a stream of consciousness is mostly unclear to me at least. I cannot separate out what is your opinion and the actual solution is not clear to me at all. This is not skimmable at all and I think that is a problem, when implementing a system like design documents.

@oswinso
Copy link
Contributor Author

oswinso commented Nov 3, 2019

Yeah I totally agree. I was pretty frustrated and tired when I wrote this, so a lot of my opinions came out, but I'll try and remove a lot of the unnecessary things.

I am very confused by how you are confused by the actual solution though. What do you mean by that?

I think some opinions in the research documents is fine (There needs to be some interpretation / summary / synthesis of the information obtained, otherwise I don't think there is much point in writing these documents if you don't come out having had a more well informed opinion).

Copy link
Contributor

@tangemicioglu tangemicioglu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm, I hope we can get this working.

@oswinso oswinso merged commit 51b8426 into master Jan 5, 2020
@oswinso oswinso deleted the research/iop branch January 5, 2020 22:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type ➤ research Issues related to research
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Try out JausToolset and write a research doc for deciding whether to IOP
3 participants