kriskuiper / functional-programming

Repo for the Functional Programming course of Information Design TT

Kris Kuiper, Front-end Developer & UX enthousiast
Good at building awesome and accessible stuff for the web.

👔 LinkedIn | 📫 Email me | 💻 Website

functional-programming's Issues

Adhere to material design principles

Acceptance criteria:

• Use a sans-serif font for body and label
• Use serif for headings? Or also sans?
• Use material color palette -> decide on one and stick to it
• Import using @font-face and font-display: swap

Set up wiki & readme

Acceptance criteria:

• Readme has necessary headings
• Wiki has week by week, day by day pages

Refactor `format-length-for-result`

Can be more DRY.

Write SPARQL query

Get sizes from all objects, let objects only have sizes

Dive into D3.js

Read some docs, watch some tutorials, do some aanklooien

Document altered concept

From bubble to network chart because so and so

Add sorted data cleaning pattern to wiki

Changed cleaning pattern, have to add this to wiki

Remove side effects

if (!size) {
    return
}

// Just return the size

Show non-length objects as "no length specified" or something

Because empty data may live too

Finish readme and wiki

I think you'll pass it with ease,

Focus a bit more on your wiki, and readme and finalise your static (but dynamic) D3 visualisation.

And you're ready to roll this friday!

Add info to wiki

Pages are well documented, and good choice of subject pages.

Only remark I have is, that it'd be a good idea to include a short intro on your wiki homepage. Maybe include the same links you have included in your custom sidebar.

• Getting started with d3 page link in sidebar is linking to a wrong page.

Data cleanup

Acceptance criteria:

• Size only returns the length as a number
• Year returns a new Date.getYear()
• Reduce results categorized on year?

Make Netlify build great again

Has to do with imports of data/results.json, doen't exist on master so can't build it from src and therefore can't import it in scripts.js in build.

Don't worry now, worry later 🆘

When to connect objects in network graph?

How to?

Alter concept

Should it really be a bubble chart? Network chart would also be cool if you could see the relationships between each object, like if bigger objects look more chique we can see that bigger objects belong to richer people

Write some about the second week

Draft already on laptop (finished?)

Make piping functions more functional

Acceptance criteria:

• Code is more DRY
• Can add multiple params through pipe
• Code still works

Add links in wiki or readme to corresponding file or snippet

Code is of really high quallity, probably to high for my level. But i do have some praise to give here.

• Good and well chosen naming conventions.
• Good use of importing different pieces of functional programming.
• Nice to see the use of Async.

The only tip I would give is:

• Maybe include the links in your readme to direct to the corresponding file of a described feature?

Set up rollup

Minify, put in dist directory

Remove duplicates from query

Acceptance criteria:

• Has no duplicate images

Set up rest of development environment

Acceptance criteria:

• Need a server.js?
• Set up CD at Netlify
• Install dependencies
  • d3.js
  • other

Query real data

Acceptance criteria:

• Real data gets queried
• Real data gets parsed through format functions
• Real data gets filtered => doesn't have a size? throw it away

Alter query based on new concept

Also get the category and categorylabel from object

Day one deliverables

Acceptance criteria:

• Sketch out the concept
• Has exact explanation of used data (can be with SPARQL query)
• Repo has functional-programming as exact name
• Fill wiki with concept sketch and description

Alter data cleaning pattern again

Have to clean the categories?

Sort results based on century?

This makes it even more explorative since there can be like 800 results per century but only 50 per year

Acceptance criteria:

• Results are like:

[
  "10e-eeuw" {
      [resultaten]
  }
]

Write some more about FP

Acceptance criteria:

• Has explanation from my own code

Add some 'bout D3

Very big fat mind f*ck

Missing features in the readme

Good start on your readme, clear and well written. Altough some key features are missing. Please check out the checklist.

• Try to include a description of the project to help people understand what it is that you're builing here.
• Missing list of added features, such as data cleaning, Rollup.js bundeler, etc etc
• Concept and image of concept, you've made a brief start on this in your wiki, either write a short summary in your readme and include a screenshot, and link to your wiki page about your concept.
• It'd be a good idea to give a short introduction to the data you've used.
• Last but not least, (im not sure if you want to give acknowledgements, because you've probably didnt have a lot of help, you're mostly giving help) but if you had include them :)

Write something about FP

Acceptance criteria:

• What is functional programming (own words)
• My reflection on using functional programming

Alter concept again