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.

The world would instantly halt if we stopped sending emails. Everything from meet ups to US senate investigations rely on Email, it's strengths and it's weaknesses. I have been battling with Email for quite some time now.

E-Mail is one of the very few truly aincient computer protocols that has survived into the current day. Even though every one uses it nearly every day, there are supprisingly few people who actually understand how it works under the hood. To use anything effectively, one needs to understand how it works and what it does. This is my attempt to unravel E-mail.

I have a strong set of views when it comes to how to work with computers. I try not to impose my way onto others and I can recognize many circumstances where my way of doing things would definitely not be optimal, but when I see how much time is spent in the long run fiddling with badly integrated tools that produce all kinds of headaches down the way I do start to wonder why others don't do it my way. So here are my general Ideas on how I try to use my computer and how I pick tools and make them interoperate with each other.