DigitalOcean’s quarterly report on developer trends in the cloud
digitalocean.com
DigitalOcean’s quarterly report on developer trends in the cloud
1–10 of 94 posts
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#2Interesting to see the disconnect between hiring managers and what people say they care about most when considering a job offer (salary). Hiring managers claim there is a shortage of talent and that they do not care about offering a higher salary. Perhaps that talent shortage would mysteriously disappear if they increased their salary offers.
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#3> Serverless computing is in a much earlier stage of adoption, with nearly half of developers failing to clearly understand what it is.
I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue because 1) it clearly communicates what it is 2) there's not actually such thing as serverless since the functions are still running on servers. It's a made up term that isn't grounded in reality. It's not serverless any more than a Heroku Dyno is Serverless.
The first time I heard "serverless" I assumed it was a totally in-browser application.
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#4Interesting to see the disconnect between hiring managers and what people say they care about most when considering a job offer (salary). Hiring managers claim there is a shortage of talent and that they do not care about offering a higher salary. Perhaps that talent shortage would mysteriously disappear if they increased their salary offers.
Of course it would. It's just standard industry propaganda to suppress wages and "encourage" imported labor.
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#5> Serverless computing is in a much earlier stage of adoption, with nearly half of developers failing to clearly understand what it is. I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue because 1) it clearly communicates what it is 2) there's not actually such thing as serverless since the functions are still running on serv…
Also it fits in nicely with the other naming conventions such as the following:
- Software as a Service (SaaS) - a product such as GitHub or Slack
- Infrastructure as a Service (IaaS) - VM or LB as you find in Azure or AWS or Digital Ocean
- Platform as a Service (PaaS) - sometimes called Container as a Service as you find in Heroku or Zeit Now
- Function as as Service (FaaS) - a single function as you find in Lambda
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#6Here's the interesting learning for me:
While Kubernetes was most popular overall, the smallest companies (1-5 employees) use Docker Swarm more often (41 percent use Swarm vs. 31 percent that use Kubernetes).
Did not know Swarm was this popular. Even overall Swarm is 35% to K8s 42%
However, there is a huge proliferation of hosted K8s services - AWS, GCP, Azure, Digitalocean, tons of others. Nobody seems to be making a hosted Docker Swarm solution though. I wonder why - is it because the market doesnt exist because of the simplicity of Swarm itself ? Would be interesting to find out.
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#7Interesting to see the disconnect between hiring managers and what people say they care about most when considering a job offer (salary). Hiring managers claim there is a shortage of talent and that they do not care about offering a higher salary. Perhaps that talent shortage would mysteriously disappear if they increased their salary offers.
The number one thing on that list is "limited pool with relevant skills" and not an actual talent shortage.
IMO this is more from asking for specific combinations of skills used at a company than anything else. You need these two programming languages, this database, this frontend framework, these devops tools and these other skills would also be beneficial.
Generally, you're better off hiring as "if you are competent with one of these and willing to learn the others, you should apply". The broader the stack the more learning curve should be assumed with the hiring process.
But it's not in a lot of cases. This also goes hand in hand with the professional development opportunities cited at the beginning of for retention sake.
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#8I find it interesting (and perhaps predictable) that while only 11% of people had a top consideration when taking a job of "Quality of manager or management", 47% of people cited "Leadership / management was bad" as a reason for leaving a job.
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#9Has anyone chosen digital ocean over aws/gcp/aZure when building a scalable setup (for pricing reasons). Eg setting up your own load balancers/ private master slave dB machines / bunch of ansible to organize it all.
Re: DigitalOcean’s quarterly report on developer trends in the cloud
#10Has anyone chosen digital ocean over aws/gcp/aZure when building a scalable setup (for pricing reasons). Eg setting up your own load balancers/ private master slave dB machines / bunch of ansible to organize it all.
Fwiw, Digital Ocean keeps adding more and more options on the service front. Several storage options, load balancers w/ Let's Encrypt built in, etc.
Keeps growing. IMO the biggest gap for them is lack of a database service like RDS. There are providers of that service that can be deployed to DO...but the cost of those providers is high enough to disincentivize the price appeal of DO in the first place.
It would be really interesting to see them partner with a known player like Citus.