eskimobloood

I wonder why the whole topic of system thinking comes (self-enforcing/balancing feedback loops etc.) only come up in older literature from the 80s til late 90s. Why did it become out of fashion with the start up culture.

My team at Signvaio|SAP is looking for a Senior Frontend Developer. Our stack: React, GraphQL (apollo client/server)

Office is Berlin, but you could work remote from at least most European countries. We also provide an relocation allowance.

Interview Steps: inhouse recruiter call -> 1h interview with people lead -> coding challenge (~3h), ->1h functional interview -> offer

Domain: Business Process Intelligence, our teams is focused on data visualisations

https://grnh.se/0c93e4323us

Yes, stands for plotter twitter postcard exchange. I think there is no real info online. It was organized by Paul Butler[1] on twitter. In the end you but your info into an google sheet and he organized sending out emails with the addresses for your postcards to send to.

[1]https://twitter.com/paulgb

This a is a really wide field. Basically its starts with one of the standard algorithms, like and l-system, a voronoi diagram, or simple combination of sin and cos to draw shapes. Have a look at thi-ng[1], just as example for a library that has implemented a lot of this kind of algorithms. The next step in my process is to think about how to destroy this forms as most of them are used a lot in this field and become boring. Using perlin noise as input to arguments of the algorithms is one way to do this. The other part is to make most all of the input variables easily changeable as most of the time the whole process is like writing the program and then spend a lot of time adapt the parameters until you get some interesting output. So in the end I have a small Svelte app, using Svelte only cause the data binding for the inputs so simple, which has tons of sliders that renders an SVG that can be saved in the end.

[1]https://github.com/thi-ng/umbrella

Sure. The plotter I've bought is the AxiDraw SE/A3[1]. There is an Inkscape plugin so you can easily plot SVG graphics. I generate the SVG graphics using small JavaScript programs. Thats already it. Here[2] is a more detailed resource list to dig into the topic

[1]https://shop.evilmadscientist.com/productsmenu/908 [2]https://project-awesome.org/beardicus/awesome-plotters

Buying a pen plotter last summer was one of the best decision for a while. As I start my journey into programming with generative art, using macromedia director and processing, I always wanted to be able to create my on physical prints. So for the last months I got back to have fun writing code in my spare time. Some examples: https://twitter.com/eskimobloood/status/1366300689652187140 https://twitter.com/eskimobloood/status/1285159611599933441 https://twitter.com/eskimobloood/status/1373317198119370753

Here is a nice write up on different examples that either work or fail: https://medium.com/@herbcaudill/lessons-from-6-software-rewr...

Would be interesting to see the result trained on images from this book[1] about mutation on insects in the chernobyl area.

[1]https://www.amazon.com/Heteroptera-Beautiful-Other-Images-Mu... [2]https://atomicphotographers.com/cornelia-hesse-honegger/

I'm only 45 and use Abendbrot, so does my daughter.

At least there are a bunch of example: https://docs.rs/crate/nannou/0.9.0/source/examples/

Doesn't the map show the trend? So it's not about how green it is but how mucher greener it's become over the last decade.

As someone growing up in the east german (I was 15 in 1989), I can tell for sure that we've learnt in school that the GDR is an socialist country on its way to the communism.

From the article:

Mr. Schmidt had been a Volkswagen employee since 1997 and was named general manager of the company’s engineering and environmental office in Auburn Hills, Mich., in 2013

Paper

Quiver[1]: suports markdown and syncs via Dropbox

Mindful[2]: chrome extension

[1]http://happenapps.com/#quiver [2]https://chrome.google.com/webstore/detail/mindful-beta/cieek...

Depends on what is "public" history. Is a branch where you working on alone public, or does it become public after merging in back to master. Squashing a branch before merging back depends a lot of the discipline of the commiter. So for a branch with commits like "add FeatureX", "arg forgot this edge case", "ups another fix", "finally it works" it makes a lot of sense to squash it. While for "add FeatureX", "fix some linter errors during development" it makes then to leave the history as it is.

I think he means to make a list of all member of the type and then iterate over it. Then you have the options method that get a union type and can render the correct output

Bartosz Milewski on Haskell and Category Theory : https://www.youtube.com/channel/UC8BtBl8PNgd3vWKtm2yJ7aA

Unfortunately its totally broken. It crashes after every merge or commit on my Mac.

Mhmm, all it does is to highlight every DOM element that has a reactid. So it does not only highlight the components but every DOM element that was created by react, so for me this is not very helpful.

You can at least try decorators with babel using[1]

  $ babel --optional es7.decorators

or

  babel.transform("code", { optional: ["es7.decorators"] });

Here[2] is an article that describes how to use it for mixins

[1] https://babeljs.io/docs/usage/experimental

[2] http://raganwald.com/2015/06/26/decorators-in-es7.html

I wrote this some month ago [1]. All the properties of the lines can be distorted with perlin noise. Especially when working with color this gives much better results then randomly setting the values.

[1]http://eskimoblood.github.io/gerstnerizer/

I wonder if there is a way to split the build in more then just one big file but in several smaller files then can be loaded on runtime.

Maybe this CCC: http://en.wikipedia.org/wiki/Color_Climax_Corporation

Whats about facebooks open graph?

Who is behind this?

According to the bower file [1] they only use jquery

[1] https://github.com/quasado/gravit/blob/master/bower.json

Seems the app is a test to verify that people don't read the README.

The point is that the icons come in 3 sizes, so a small icon has less details, then a large one, this is a feature missing in the most icons sets: http://blog.useiconic.com/designing-iconic-across-different-...