invisiblea

Freelance means more control over when you work and what you work on, but it also means more effort to find work, keep your finances in order, and ensure that you are meeting the demands of your clients (who maybe sympathetic to your situation to start with, but that might change if you fail to meet deadlines).

Existing in a team environment, with hopefully support and compassion, may be better for you while your recover, and you'll gain professional insights you don't get when working by yourself.

That's an entirely fair point, but frustrating that the connection limits are not clearer in the docs.

I'm _really_ disappointed with the managed DB service. The "75 simultaneous connections per gigabyte of usable memory" limitation means cost wise it's cheaper just to spin up a 'real' database droplet.

We (a small 5-7 person digital agency juggling multiple active projects) have been using Clubhouse for the last couple of years after outgrowing Trello and finding Jira too complex.

It's flexible, fast, good app integration and has a responsive support team. We recommend it.

Future wish list would be: - Per Project User access, so we could invite clients into just their project. - Harvest (or similar) time tracking integration, so we can see how long we spent on "stories"

That list is very out of date. One of my clients appears on there and when we took over in 2012 we encrypted all their user credentials.

It's Geekbench 4

I use DO for several one or two box production sites (LEMP and RoR stacks), and have minimal complaints. I'm a big fan of scaling up the CPU without having to also increase HD size (which is a Linode requirement).

The biggest issue we've faced was their use of Google DNS. A couple of months back, Google DNS had an outage, and all our calls to external services semi-silently failed. Because this wasn't technically a DO service outage, it wasn't reported by them, and because we didn't know they used Google DNS we didn't trace the issue to the outage. We could have done more, but they could have also been more transparent.

Overall, we are starting to move more projects to DO from Linode, because I feel Linode's previously excellent support has slipped dramatically (customer for at least eight years). We also leverage a lot of AWS services (particularly S3 and SES).