I don't mind having (software-)architectural discussions, but I do feel they're most valuable when people discuss concrete challenges and use cases, rather than vague intuitions about what's "cleanest". For example:

Follow

@vinnl I agree completely, or like the sticker I have on my laptop says: "Show me the code or shut the #@!* up!" xD

I know that's a bit rude, but when programming/architecture discussions get too long without a concrete use-case, you're just talking about a silver bullet that doesn't exist. A solution may be great for one context and bad for another.

Sign in to participate in the conversation
Noel's Mastodon

This is an instance-of-one managed by Noel De Martin.