7 ms·
Even as someone who uses CQRS/ES on a daily basis, I don't expect most engineers to know them, just like I wouldn't expect a lot of engineers to know "currying"
by vorpalhex 8y ago
Even as someone who uses CQRS/ES on a daily basis, I don't expect most engineers to know them, just like I wouldn't expect a lot of engineers to know "currying".
Tech is a big field, it has a ridiculous amount of vocab. Unlike Doctors, we didn't standardize heavily.
- manigandham 8y agoThe medical field is big too. The point is that it's your responsibility to learn things, not expect every piece of jargon to be explained to you.
- vorpalhex 8y agoI think you missed op's point. They weren't seeking an explanation, they were pointing out the initial sales pitch was too jargon dense as to be meaningless. The initial sales pitch might as well be in ancient Greek for your average engineer.
- manigandham 8y agoThat doesn't make sense. Of course it's meaningless if you don't know the jargon. The op says the product devs should "put in effort" otherwise the op will "skip over it and move on". This is backwards because it's up to you to learn things you don't know.