Unconditional Code • Michael Feathers • GOTO 2018

I was watching this the other day: ▶ this video Unconditional Code by Michael Feathers One solution to this problem is discussed toward the middle: giving data instead of asking for data avoids error conditions. Doing so pushes use of the data farther down the call tree and pulls acquisition up near the top, where we are closer to the user and thus able to more clearly decide what if anything to do about these corner cases.

Blockchains Are a Bad Idea (James Mickens) link I find almost all from GOTO 2018 very insightful. link esp ones listed below. GOTO 2018 • The Do's and Don'ts of Error Handling • Joe Armstrong link GOTO 2018 • Pragmatic Event-Driven Microservices • Allard Buijze link GOTO 2018 • Why Business Cases are Toxic • Chris Matts link GOTO 2018 • Unconditional Code • Michael Feathers ▶ this video

Please no on the Universal nil. Meaningful zero values for types are essential. It may be confusing to some that nil is a valid zero value for some types and not others, in which case that needs to be refined, but having a type that can either be a value, a zero value, or a nil introduces complexity where there should be simplicity. Having a zero value enables, for example, Unconditional Programming: ▶ this video