I’ll often link to this on my posts. It’s just 3 caveat’s regarding my posts and where I’m coming from. The intent here is to ask that you consider your comments and replies and reactions in light of these three items:

Caveat 1

I haven’t taken the time to try a lot of the patterns and processes I critique in my posts. I think my imagination is powerful enough to not need to pour time into thrashing each approach in real code/life. This is why we have strong communities (or at least need them), communities help you and I see past our assumptions. So by all means comment, just realise that “your way” and “my way”, while one possibly better than the other, might be just too much work to test in a real application. This doesn’t mean I won’t try, it’s just that while something looks great in a “Order Pizza Online” app, it doesn’t necessarily translate to “I’m coding for someone else’s real world requirements”

Hopefully, by posting about it, I can help you with your “imaginings” and you can help me with mine.

Caveat 2

I purposefully ignore pleas to “Git’r’done”. It’s true, there are plenty of situations where you can do no better, but I’m not interested in it.

My assumption in writing about software architecture and development practices is that you and I are both on the “Clean code, Crafted Code, Best Practices, Code by convention” page.

Caveat 3

I have never claimed to know what I’m talking about ;)