[system2]

We don't know what the SaaS products were, what he is describing, how much they were, who was the target...

I am just fascinated by these type of posts which people can sit down and write longer than I can tolerate to read. I still don't know what the author tried to convey. Impressive this got 99 votes here.

[Hnrobert42]

I actually like that the author didn’t describe the products. That’s beside the point. The point was about the evolution of their goals, definition of success, and ways of failing.

[fauigerzigerk]

It would be useful to at least know a little bit about the type of customer the products were for.

There was a story a while ago from someone who had built software for physicians to pick the best drugs for a particular diagnosis. They described the problem and how it was currently solved. They described how they talked to doctors and what response they got. They described what they had to do to create a useful and credible product. I found that post very enlightening.

With this post I feel like I have absolutely no way to judge whether the author's conclusions are relevant to my own projects.

[lloydatkinson]

No it isn’t besides the point.

[that_guy_iain]

Sometimes you get lost and you have lots of information to give to explain your position. I was writing a blog post aimed at non techincal people and 1/3 of the way through I was at 1200 words. Nope. That needs to be cut down to 600 words.

Once I wrote a blog post that I knew most people would just disagree with, so I wrote out a full length explaination. I posted it on Reddit, hardly anyone read actually read it and every single one of their comments againist my point was commented on in my post. Lots of people upvote and downvote based on title. Which kind of makes sense since you normally have to go to the page and read it before making a decision but the upvote and downvote buttons are right next to the link. One of the reasons I don't upvote often is I just forget. I've clicked the link read it and I'm off to my next post.