Dominick Baier's talk is a great introduction to the often confusing world of OAuth. There are many good resources about details of a given flow, but the challenging thing is which flow to use for what.

Listening to Dan North (@tastapod@mastodon.social) is always fun. I recommend his JAX 2021 keynote. I enjoy revisiting the basics, because it's never about memorizing and blindly following some principles

In case something goes wrong with programming.dev infrastructure, it would be good to have a Mastodon account (preferably not hosted on the same infrastructure) to inform the public about the status.

Which difftool do you use and why? I develop on Windows and I use KDiff3. It has worked flawlessly all these years. And just because of that I haven't really followed what else is out there. I suspect I'm in the minority?

cross-posted from: https://programming.dev/post/140226

This is a fun way to explain how technical debt accumulates in our systems. Not having good understanding of the domain results in low code quality and difficult to maintain code bases.

After the talk, one of the contributors says "you are preaching to the converted." But we, engineers, need to learn how to communicate these concerns with the rest of the organization.

This is a fun way to explain how technical debt accumulates in our systems. Not having good understanding of the domain results in low code quality and difficult to maintain code bases.

After the talk, one of the contributors says "you are preaching to the converted." But we, engineers, need to learn how to communicate these concerns with the rest of the organization.

Tools are critical for all professions. In programming, Git is central. Almost everything we do touches Git. We all need to master it at least to a level that it doesn't get in our way. But when you start getting hold of the basic concepts, it's also a powerful tool that is fun to work with. Hopefully this community will be a place to share our knowledge and help each other.

A good, short summary/definition of DDD.

We are considering using C4 for our architecture diagrams. Many diagramming tools (including Structurizr which was developed specifically for it) support C4. I wonder if there are others that use it and I would like to hear your experiences.

My initial assessment is as follows:

Pros

• Diagram as code is a great way to keep things open to change.
• It allows for better versioning
• It enforces semantics into the diagrams. Instead of just thinking in terms of boxes and arrows, one need to dig deeper

Cons

• It has a relative steep learning curve (one needs to study the DSL even though the end result is just boxes and arrows)
• The tooling is not perfect. One needs to run a docker container to be able to navigate within the diagram (solution: there is also a SaaS offering)
• Its view of architecture is somewhat limiting. It doesn't seem to be catered for augmenting the diagrams with other forms of diagrams (flowcharts, etc.) or text.