Hey. I'd like to re-iterate that I think you're doing a great job, something which I and many others don't have the skills or the talent for. But yeah, it sure

Hey. I'd like to re-iterate that I think you're doing a great job, something which I and many others don't have the skills or the talent for. But yeah, it sure looks like you are selling something. Not in the "act now, buy this" sense, but still. Please understand that I'm not putting you down, on the contrary. With all the specifics you provided, this is still a very non-specific article. It's a beautifully written description of a technique that provides a lot of detail and yet gives very little away that could actually be used to learn something off you. And again, that's perfectly OK. I absolutely agree with you about engineer types, and I'll be the first to admit I'm a prime example of that group. In between those two extremes, there is a spectrum of course. > My goal was to try to make a case for building a very simple product for a very specific pain point, get customers who have this pain and want it solved as quickly as possible, and then (possibly) add complexity and scope from there. I'm not sure I agree about the pain point being the most important thing in that strategy, but that may be because after reading the article I still lack the information to judge what it actually is you solved. I ended up building a WordPress plugin, but what I built and how I built it is immaterial here.