Statistics is a field of Mathematics primarily concerned with Probability, it's definition and interpretation as well as figuring out a whole lot of things about how probabilities behave.

I just read a piece on the veil of ignorance, what it is and what effects it has on people. In short, when designing something, the designer is encouraged to view the thing they have built through the veil of ignorance. From the point of view of another entirely different human, with an entirely different background and experience. What would they see, what could they want form it and how would you go about helping them in getting what they are using the thing / came here for.

It has come as it had to, I will try to move all of my note-taking online. I have had a Website for about two years now and I have been contiguously fiddling with it and trying to make it the place where I put every bit of writing that I deem good enough to publish. By now I know that I learn best by formulating what I know in a "proper" manner, that is by writing a coherent text or a series of related pieces of information down on a piece of paper. And from now on, so I hope, I want to replace writing it onto paper with putting it here.

The first thing that you need to do after maybe understanding the basics of micro controller is to set up a tool chain. The tool chain is the set of programs that help you get the code you have written onto the chip that is supposed to execute it.

I like to understand what I am doing. As such I don't like abstractions that I don't understand even if I have (black box) model of what happens when I invoke which function. Most tutorials, that I have encountered have however relied on exactly that acceptance of black box abstractions when they introduce concepts. This is especially true for software development where many things that are done commonly are in reality teribly complicated but also sufficiently abstracted over to make it simple to use, yet not so simple to understand of course. This is where I want to differ.