caseydm

"Hey I got some great news. Got 20 minutes for a call later today?"

Oh really? Logging into the portal or logging into with the CLI to push code? The CLI login is down for me.

Our startup uses managed elasticsearch through elastic. We're a very small team so support/consulting advice is important to us and they are good at that.

Ha! I always laugh when I hear those. Guess we will find out!

I was a naysayer but find copilot makes me more productive. Especially at writing tests. It's very good at recognizing patterns in your own work, and completing an entire test based on the function name.

Anybody using Cloudflare to cache an API that serves JSON? Thinking about setting that up.

No I never used any of that. I would have moved on to another job if someone insisted on it.

I sound like a shill for Upwork (promise I'm not!). But the fees for long-term clients (>$10k in earnings) is 5%. If you go on your own and bill through a system you will likely pay 3%. So it's not that different.

I would give it another shot. Since your history is older you likely need to keep your rate at $60 for a while and complete a few jobs. But UpWork has the biggest market and there are plenty of people out there willing to pay for developers with a solid history.

People say it's underpaid or terrible, but part of that reputation comes from people doing one or two jobs and quitting. Plus, I've hired developers on UpWork and a lot of people suck at writing proposals. I have a lot of advice on that too.

I was very successful on UpWork. However, it is not something you can jump into with no work history on the site, like "I have 16 years experience so my rate is $125/hr." People don't believe you when you say that. They want to see proof from a third party. So you need to start lower ($30 to $50/hr), stay in a niche, and successfully complete jobs while gradually raising your rates.

When someone sees glowing reviews and completed jobs, you become the "easy button" and they will pay more to decrease their risk. When they see 10 completed jobs with 5 star reviews, all mentioning the exact type of work they need, they can be pretty sure the 11th will be successful. It's possible to charge $125 or more an hour on UpWork and have to keep your settings updated so that you are not spammed with invites.

I agree that a small team of engineers can do big things. But 15 engineers to run Uber ride share in maintenance mode? That's insane. I would love to see a breakdown of each engineer's responsibilities in that scenario.

Heroku is my tried and true. I've likely done thousands of deploys over the years and have never had one go bad or leave my app in a bad state. I have rolled back an app a few times due to bad configs and it was always quick and left me with a huge sigh of relief.

That being said, they are very stagnant on features. A dyno has operated the same way, at the same size, at the same price for like 10 years now? The main features I would like to see are auto-scaling for all dynos and IPs that allow you to restrict database traffic. Render looks promising in that department and could likely get business from me if Heroku doesn't change in the next couple years.