[furyofantares]

I really appreciate this list. It's cool to see how people work, and I'm sure the folks building the services you're using appreciate the kind words.

I also had kind of a strange reaction to it, which I tried to figure out, and I'll explain it in case it's at all representative of other reactions being posted here.

I think it's just kind of intimidating to read a list of SaaS someone else uses. After reading the whole list, in the back of my head I'm imagining the burden of learning all of these all at once, of managing a dozen new passwords and payments I'm not currently managing, etc, and I'm not imagining an improvement to my own workflow because my work doesn't match yours.

It's easy to imagine getting zero or negative value out of any SaaS if it's not solving a problem I personally have.

But on the other hand it's hard to imagine getting less than 12/mo for any service that is doing something for me. And it's hard to imagine that a 3 person team mistakenly believes they like some service they're using.

So I'll skip the judgment about how you're spending money on improving your work environment and say thanks for the post.

[oliv__]

The more I read your comment, the less I understood it.

[abalashov]

I understand it very well, and relate closely to the author's mixture of feelings. It's overwhelming and intimidating to be reminded that there's a bunch of stuff you ostensibly should be using, or at least researching and evaluating and deciding not to use.

[tonyedgecombe]

I'm not sure you should be researching this stuff unless you have a real problem to solve.

[furyofantares]

I think that's what I was trying to say. I don't have any of these problems to solve, so when I read a list of someone else's SaaS it causes a low level anxiety that results in a weird, almost certainly incorrect, gut reaction that this 3 person company probably doesn't need all this.

[kyawzazaw]

Same