Hi there, thanks for the feedback. I appreciate it. I don't mean to suggest that money == spend like crazy. All I'm suggesting here is there is merit to "embra

Hi there, thanks for the feedback. I appreciate it. I don't mean to suggest that money == spend like crazy. All I'm suggesting here is there is merit to "embracing constraints". When you don't have money, you can't spend it. When you do have money, you may spend it. There is a difference between the two statements. This is especially important for people who think throwing more money at something is a solution. Some managers tend to think if a project is behind, simply throw more developers at it. We developers obviously know that isn't a viable solution in some cases. In fact, more people means more communication, training, procedural overheads etc which could actually slow down the rest of the team. Being money constrained, helps us focus on what's truly important so we deliver the best bang for the buck. We're small so we can't afford to spend 2 weeks on a feature nobody needs. The lack of money here helps us see that. Also thanks for the comment wrt marketing. I'm not marketing god by any means (and this blog post isn't about marketing anyway). I certainly do not know all the channels available to me to market my product. But that's part of the learning experience which is one part of why I'm doing this. Thanks again for the comment.