Skip to content

Instantly share code, notes, and snippets.

@benkoshy

benkoshy/Assumptions to consider when creating an algorithm.md

Last active February 13, 2017 22:25
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save benkoshy/69f624f959e80a7842a2a319d797f120 to your computer and use it in GitHub Desktop.
Save benkoshy/69f624f959e80a7842a2a319d797f120 to your computer and use it in GitHub Desktop.
Download ZIP
Assumptions to consider when formulating algorithms
Raw
Assumptions to consider when creating an algorithm.md

Assumptions to consider when formulating algorithms

  1. What are the range of inputs and outputs?

    (a) Characteristics of input/output values? (i.e. duplicated records, redundant records, uncleaned data etc)

    (b) data structure of inputs/outputs: can you think of a structure that will make everyone's life easier.

  2. What are the costs of inaccuracy? Can they be latter fixed?

  3. Time limitations?

  4. Computational power limitations?

And designing the actual algorithm:

  1. Can you understand it by looking at it?

  2. What parts do you think will change?

All the above factors and more will influence how you solve a particular problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment