Merkur

The title is a reference to http://journal.stuffwithstuff.com/2015/02/01/ what-color-is-your-function/ a joyfull rant about async functions and promises.

I like to request your comment on a similar topic. While coding in go - I often find me asking: is this package go-routine save? Many times I find the answer in the doc's or can ask on the internet, sometimes I need to look at the code.

"go routine safety" is just like the color in the rant of munificent.

On a current project I would like to assert that a user provided callback is a pure function - there we got another color!

those two colors are alike - they represent meta informations about an entity (function, package, struct) and they are about the behavior of the entity.

They also have something to do with boundarys - tho my English skills deny me to elaborate :(

I wounder...

Do you know other kinds of colors?

Is that coloring bothering you? And if not how do you approach it?

Hi,

I could need a pointer, I have the feeling I am one inch away from understanding - but still something is missing. could you provide a hint or a resource or an sample implementation?

it's about creating a dynamic user model for my CMS. I observe the user and record it's interactions with the web page. I also managed to lift those interactions in a business domain - ie. interpret interactions with certain HTML Elements as interaction with a product / article / topic.

I got the data - as stream of filtered interactions - but still the math needed to create an actionable model eludes me. :(

I am looking for ways to aggregate the data into some expressions like "user got strong interest in blue lamps" the CMS could use to make decisions about content placement.

how can I organize the interaction in a way to draw sutch conclusion? what kinds of algorithm should I look into?

thx in advance, Merkur