Chris F. Carroll @chrisfcarroll@qoto.org

“Query logic in SQL, Command logic in whatever you use for processing the command”

Mulling over e.g. https://wiki.c2.com/?DontUseExceptionsForFlowControl it seems to me that “Don't Use Exceptions for Unexceptional Flow Control” would be a better motto.

The main argument is just readability — can the reader understand code?

Nearly the last word on the page — “I use exceptions when the preconditions are met, but I can't meet the postconditions” seems like a good motto for when to use exceptions.

Diagrams for software architecture is so passé, the future is moving gifs

There is no bug that cannot be made more difficult to debug by adding another layer of indirection

Small steps
https://www.wired.com/2001/10/slugbot-enemy-of-slugs/

TIL that the HTML spec has a section about forgiving base64.

https://infra.spec.whatwg.org/#forgiving-base64

Probably the funniest thing I've seen on microservices.

https://www.slideshare.net/jeppec/event-driven-architecture-integration-tech-event-2019#3

Are cosmic ray bit-flips common enough to make voting machines unfit for purpose? The smaller the electronics, the less energy a bit flip takes. Nice discussion of bitflip examples:
https://radiolab.org/podcast/bit-flip/transcript

Was the real value of OO that it was/is a good vehicle for Responsibility Driven Design?

It is easy to code Roles, Responsibilities, Collaboration and Contracts in OO languages.