I read one to two hours a day keeping up with the latest jargon and best practice. I'm pretty sure every programmer knows what a user interface is. I'll guess t

I read one to two hours a day keeping up with the latest jargon and best practice. I'm pretty sure every programmer knows what a user interface is. I'll guess that most programmers don't know what CQRS is. And with how busy we all are as devs I think my point is still valid: tell my how it benefits me and I might read further. Others here have already done a really good job of improving on the jargon-filled original description. So I'm not wrong in saying there was room for improvement. > It’s like you’re expressing frustration about not knowing something I'm not. I'm trying to help startups and small projects do a better job of communicating what value they add so that potential customers and users don't skip over their project.