Dan Bergh Johnsson

@danbjson @KevlinHenney Yes. Quite often when a developer says "I understand the code..." they really mean "I assumed the code..." :-)

Instead of attending #DDDEU, I’m in Sweden, writing a chapter on how to design DDD entities in a secure way. Weird. #SecureByDesign

Why is it so hard to spot bugs? Because most of the code is correct, leading us to confirmation bias, which makes us miss the subtle mistake

Today my eminent colleague @frusunnanbo presents at @konfDataTjej talking about @elmlang. If you're there, don't miss her! #womenintech

We need hands-on ways to make software, like making pottery with your hands - @conways_law #DDDEU

Sad not to be at #dddeu, would have loved to discuss how #DDDesign can promote security together with seasoned DDDers. #SecureByDesign

“DDD should have been called ‘Boundary Aware Design’ but the acronym is pretty bad” — @mathiasverraes #DDDEU

Code amplification in DDD: number of places in codebase you need to touch when introducing or modifying a concept in your domain model.

#alternativefactshttps://twitter.com/tesslundstedt/status/824355185363484672 …

För oss som aldrig blir RT:ade är Twitter en enda lång och fantastisk Memento mori.

Another design mindset is "do I understand it", leads to deep design, and code with TimePeriod, ISBN, Quantity. Much safer #securebydesign

One design mindset is "can I code it", leads to shallow design, and code riddled with ints, floats, Strings. Security risk. #securebydesign