The key takeaway, for both physical and digital spaces is that we need to be disciplined and make deleting and organizing code a regular priority. Ignoring clutter only compounds it and makes a seemingly intractable problem even worse. Armed with a simple set of rules and making an effort is worth it. When you KonMari your code, you can transform frustration into joy.

In this valuable talk, Marcus will describe exactly what immutable classes are. He'll tell you about their advantages and disadvantages, and show you how to…

In a shiny, new world made by a programmer, one might see their creation and go, ‘yeah, that’s probably good,’ but bugs may lie just below the surface…

Rich Hickey explained the design choices behind Clojure and made many statements about static typing along the way:
solving a real-world problem => must use non-elegant models
running all the time => must deal with state and time
interacting with the world => must have effects and be affected
everything is changing => must change in ways you can't predict
.
Share an interesting perspective and some stories from my time as a Haskell programmer. I conclude with a design challenge for the statically typed world.

In this talk, Uncle Bob describes the three laws of Test Driven Development, and demonstrates the discipline using the Kotlin language.

Professional Developer Learning is Broken. Let’s Fix it.