Repeatable Execution

Room 2

11:40 - 12:40

(UTC+02)

Talk (60 min)

Thursday

What should applications log? Much enterprise code has logging code liberally sprinkled over it. Often, too much. Programmers log lots of things out of fear of not being able to troubleshoot problems that might occur in production. Even if you log a lot, however, how do you know that you haven’t missed a piece of crucial information?

In this talk, I’ll discuss a formal method for deciding what to log, and what you don’t need to log. Learning from functional programming, distinguishing between pure and impure code holds the key to such decisions. Examples will be mainly in C#, with some Haskell as well. No knowledge of Haskell is necessary.

Mark Seemann

Mark Seemann helps programmers make code easier to maintain. His professional interests include functional programming, object–oriented development, software architecture, as well as software development in general. Apart from writing books about Code That Fits in Your Head and Dependency Injection he has also created several Pluralsight courses, Clean Coders videos, and written numerous articles and blog posts about programming.

Originally poised to become a rock star or (failing that) graphic novelist (in the European tradition) he one day found himself with insufficient talent for either, a master’s degree in Economics, and a desire for working with computers. He has been doing the latter intermittently since 1995. When not working with software or spending time with his family, Mark enjoys reading, listening to and playing music, as well as preparing or consuming gourmet food and wine.