Make things implicit (more) explicit. This is the mantra we often here, but when touching the reality of software development, often forget, because of the magic beauty of technology, tooling, etc. Should we repeat this, when modelling domains as well?
TL;DR When testing, we often use constants to show that a number used in two places has the same meaning, not only value. How can we apply this when writing documentation or giving examples of algorithms you want to use? Meaningless enough Consider the first example 2 - 1 = 1 1 - 0 = … Continue reading You’re using wrong numbers
Is it possible to stick just to aggregates to model your domain? Is it possible to make it any better with services or maybe another tool is needed?
Zapraszam Was serdecznie na konferencję Rzemiosło IT, na której będę miał przyjemność wygłosić prelekcję The Only Thing That Matters. Poza moją prezentacją zobaczycie tam ciekawą mieszankę tematów, od kariery programisty, przez eliksiry miłosne aż po DDD, agile czy wymagania. Będzie ciekawie, będzie działo. Zapraszam i do zobaczenia!
TL;DR Our industry was forgiving, very forgiving. You could not put an index, run a query for 1 minutes and some users of your app would be disappointed. If you were the only one on the market or delivered banking systems, that was just fine as you'd no loose clients because of it. The public … Continue reading Cloudy cost awareness
In this episode, we will revisit this idea by referring to the good old-fashioned Twitter and its timelines. How timelines are created? Is everyone treated equally? Is it only aggregates' identities that should be pivoted or maybe our thinking as well?
It's time to consider what is an aggregate and where an event belongs to. Is it always obvious where one belongs to?