I was told that in Paris you indicated that this needed clarification. The pattern as my red book describes it is evidently not correct in according to your clarification, but nothing changes about my explanation except where I point when I say "port," which actually I avoid.
1
There is still no place to read your (Alistair) thoroughly correct(ed) pattern description. When your post disappeared for a while I wondered if you were writing something fresh. Anyway, thanks for helping us think more clearly about this even if saying/writing it is unclear.
2
did you try
alistair.cockburn.us/hexagon…
2
2
Yes, that is what I referred three tweets prior. Your pattern opens stating as I explained it.
Re: Bounded Contexts Both the outside and inside are part of the Bounded Context as I describe it.
Outside-in: adapter->app->model
Inside-out: app->adapter
I used this statement in your pattern description to form my understanding: "As events arrive from the outside world at a port, a technology-specific adapter converts it into a usable procedure call or message and passes it to the application."
2
1
1
I don't know how you read hostility into anything I have written. I apologize if I made you feel that way. My statements are my perspective, which was labeled as "wrong" and my explanation ignored. If anyone should feel hostility I am pretty sure I could rightly make that claim.
5
2
So... I don't think that the definitive final ultimate meaning of any sw design or architectural pattern should be claimed by an author as immutable. Patterns will transcend their initial writers' perceptions as people fit them into their own design context.
3
3
7
I've been wrestling w ways to hook up patterns I've seen&written (for ex. 1 called Wipe Your Feet at the Door which is relevant to implementing an Adapter) In hindsight it could've been named better. As I co-wrote it w Big Ball of Mud co-author Joe Yoder that influenced its name
1
1
This is just one example. As people try to hook up their knowledge and mesh it w pattern wisdom penned by others I hope we recognize this as a messy imperfect process. I like that you Alistair want to be party to conversations. Not all authors do
1
4
Hooking up knowledge on Twitter is really hard. What I wrote in reply to @TotherAlistair a few minutes ago is likely already lost in a twisted vine.
A while back @stilkov @UdiDahan @bitboss @ewolff and I started discussions on "service patterns." We had two meetings and poof.
2
I’m sorry about that and take the blame. I still think it’s worth pursuing.
Dec 1, 2020 · 8:03 PM UTC
1



