Frank de Jonge

I’m probably too jaded for this, but I don’t see how next time won’t be different.

What makes it the best? I see this as a point of weakness in the PHP community, not something to be celebrated TBH

Oh wow, that’s a while back!

Hi :) it’s in the gh-pages branch of the repo (old school, I know 🙇

Frank de Jonge @frankdejonge.bsky.social on Event-Driven Architecture and solving problems with programming languages. Host: @rawkode.dev
🎧 Listen: https://buff.ly/3X8tnn9
#CloudNativeCompass podcast 🎙️

Just write the damn SQL

Certainty is the enemy of growth.

If I did, I didn’t find out 🤣

I was in a band and we needed a website; figured it wouldn’t be so hard. Got hacked and then wanted to make sure I never was hacked again, so dough into everything I could find on the internet.

I did hear of them already a while back, but also the having to pay to run containers aspect seems pretty odd to me.

I haven’t, oddly enough I’ve never hit performance issues that were not caused by developers themselves.

In case you're stuck becasue MacOS thinks Docker for Mac is "malware": github.com/docker/for-m...

With well over a decade of open source maintenance experience, one of the best tips I can give you is: you don't have to accept people being rude to you.

Winning is being better today than you were yesterday.

A new [missing word?] that…

Another big part of this is DMARC and DKIM setup, which is a lot more important since last year. Having that setup if you're emailing yourself programatically is essential: www.cloudflare.com/en-gb/learni... big spam penalty if it's not correct. And "dkim alignment": mxtoolbox.com/dmarc/dkim/d...

Mailpit* whoops! haha

Mailput seems to use an API provided by SpamAssassin (github.com/axllent/mail...) but also has things like HTML checks. All of these are exposed over an API as well as viewable in a dashboard. Not sure if such an approach fits your use-case, but looks pretty helpful :)

I use mailpit which has a scoring mechanism which it partially uses a spamassassin api for. Can look up the specifics in a bit, on mobile right now

Wasm maybe?

I’m not super by the book on my event storming sessions, so I wouldn’t know which method I use. I kind of mix in event sourcing terminology so it maps to code easier. In that scheme I miss a way to express when a command can not result into an event, or when it is conditional which events are raised

Btw, what you describe as policies in event storming is different from how I use them. For me, policies are behind commands and they guard internal consistency. I use process managers for what you describe as policies.

The corners in Google Calendar have a new border radius, which means somebody in engineering just got their promo-package in order.

For me, these models are tasked with enforcing conceptual/model consistency, they embed the policy. In evenstorming those would be policies behind commands, in code though they’re not as isolated as eventstorming has them.

You’ve guessed it!

I see where you're coming from haha

I wish I didn't have to post this again, but here we are:

The common language in people who are familiar helps, but I’ve seen the tactical nature of the names leave a lot of room for varying interpretations and dogmatic viewpoints. Both which hurt innovation and progress.

Not nearly as often as I have to explain the terms Aggregate and the finer intricacies of read/write models. When people move from a crud-centric worldview, the separation needs to be explained but in my experience that’s easier done using decision/presentation framing.

Not sure if these new found terms will ever be common ground across engineers at large, but so far they have helped in my own conversations talking about various models with specific responsibilities.