Jonathan Edwards’ Post

A short overview of the application I'm currently working on.

It is just as essential to know what not to do as it is to know what to do.

I strongly believe that “the system as working” is the most important thing. Being able to observe and describe the system IS the job—otherwise you’ll never be able to operate or change it. Diagrams are one way to describe the system. They should *not* be treated as “documentation for how the system works”. It’s a map. Not the territory. Only the system tells you how it is actually working (or not), not the diagram. Draw maps often, be practiced enough to be able to do it quickly. And delete them, often. Because maps are always wrong.

My slide in the group Presentation which is about specialized receivers and some examples that we use in our daily life.

pay attention to what kind of information you get.

Comprehensive list of what you're entitled to...

A brief overview of what we do.

Pay attention to what kind of information you see.

pay attention to what kind of information you see.

Just a quick summary of the most recent work I have done.