You may not be fully aware of how incredibly afraid they are of what they perceive and expect. Like me, you’re also probably not yet personally affected.
I wrote “growing signs”, you seem to have read “already there”. If you think everything’s fine with the Trump administration, and there’s nothing to worry about, especially not with regards to nationalism and racism, we’ll just have to disagree.
1
So you do not observe growing support for right-wing, populist parties? And no increase in authoritarian governing styles in Hungary, Poland, Turkey, and the US?
1
3
I find this position incredibly ignorant. I have no idea what kind of filter one needs to apply to reality to not see the growing signs of fascism all around.
The comparison to Nazism displays, in my estimation, an ignorance of the true evil of the holocaust. The mere attempt to compare that evil with the awful situation of the last few weeks diminishes the significance of the holocaust to the level of — politics.
10
16
2
93
Damn, I’ve got something in my eye hollywoodlife.com/2018/06/22…
2
4
7
Completely agreed. So here’s my take: upstream/downstream refer to the actual, organization power dynamics among teams/context. These may or may not align with technical dependencies (runtime or development time).
1
2
7
While I agree with Eric (as per his authority, as he defined the terms), I still think you said the same thing I did and criticized me for saying it :) But we can take this offline.
Perfect, that’s the kind of definitive answer I was looking for. I would have used the terms differently, but there’s no point in confusing people.
1
1
Not 100% sure I have an answer to my question now. Are upstream/downstream technical restrictions (e.g. because of the downstream system technically depending on the upstream model) or the organizational results (e.g. by applying a customer/supplier relationship)?
2
Don’t introduce the term “model flow” again, I carefully tried to avoid it ;)
Of course run time and development time dependencies don’t have to map 1:1. Let’s just assume they do for this discussion.
1
1
That would be my take as well: Conformist and Customer/Supplier are organizational ways to deal with a technical dependency. It would be interesting to see whether @ericevans0 and @VaughnVernon agree.
1
1
(Note that I’m actually asking about the agreed-upon, “canonical” DDD usage, in case such a thing exists)
Quick DDD terminology question: Say Context B depends on A (e.g. because B uses one of A’s services). Is A always “upstream”, or does this change depending on whether one applies “Conformist” or “Customer/Supplier”?
6
1
1
12
This is very well done. Even when you don’t object to the tone of the original mail, I can’t see how anyone could argue it’s better than Gary’s version.
Being a jerk might amuse some of your fans, but it doesn’t help the issue and alienates lots of people for no reason at all.
Posted: "A Case Study in Not Being A Jerk in Open Source", wherein I rewrite a Linus Torvalds email to be half as long, still clear and forceful, with none of the insults. destroyallsoftware.com/blog/…
1
8