Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DigitalOcean S-1

sec.gov

Post reply on HN
Print view View original

411–420 of 442 posts

Re: DigitalOcean S-1

#411

Post by Beefin »

Ansil849 wrote: post #305
kevinoconnor7 wrote: post #228

Earlier quoted context omitted.

I remember interviewing with DO back in late 2014 and it was nuts! The entire interview process took ~3 months and it was clear that they were defining the process as they went. The entire process was basically: 1. initial call with recruiter 2. homework project 3. call with engineer to discuss said homework project 4. two phone screens with engineers 5. onsite interview with 6 engineers Finally I had was at the fina…

Not to hijack this sub-thread, but just a general question: how does one deal with unethical 'homework projects'? I've had a case during an application where I was given a 'homework project' that seemed to me very much not like a theoretical scenario, but more like the company wanting me to do free work for an actual real-world issue they had. Have people had situations where you suspected the same? How do you deal w…

I will only ever commit to a homework assignment if the employers' commitment level is on par. For example, if they want me to do a homework assignment before meeting the hiring manager, no way. In other words, the assignment CANNOT be the first gate otherwise companies will just spray and pray then find the most desperate candidates.

Re: DigitalOcean S-1

#412

Post by johannes1234321 »

dotBen wrote: post #351
jeffparsons wrote: post #321

Earlier quoted context omitted.

My employer deals with this by compensating candidates for their time. Y'know... with money. We also don't give them our actual problems as homework tasks. We'll occasionally talk about our real problems with candidates in interviews, but we're very clear about it when we do. It's not a perfect system. Some candidates will choose to spend longer on the task so that in the follow-up interview they'll have the opportun…

Doesn't this discriminates against people who are on visas who can't accept remuneration from anyone other than their current employers..? They then either have to do the same project for free or decline to continue the interview process.

Not only visa, but also while employed one often can't simply be paid by a "competitor" for similar work, that would break the loyality to the current employer which is mandated by contract law and general low.

Re: DigitalOcean S-1

#414

Post by jtdev »

timdev2 wrote: post #373
jtdev wrote: post #370

Earlier quoted context omitted.

Yes, I have considered that. But, no, that’s not my “problem”; I understand that this is not covered by the constitution. I believe that Section 230 should be updated and the clearly vague “otherwise objectionable” language should be removed in favor of specific language regarding where, when, and why content can be taken down, i.e., only when that content is unlawful. I understand that some are still basking in elec…

Imagine a world where Section 230 doesn't exist. A mean corporation takes down your post, or bans you. What cause of action do you imagine you'd have that wouldn't be barred by 1A? By and large, 230 acts merely as a procedural fast-last to dismiss suits earlier than they'd otherwise be. But they'd ultimately be decided the same way on first amendment grounds.

You’re presenting a false dichotomy...

230 needs to be updated, not thrown out; 230 clearly has important aspects that must remain, and other aspects that are clearly being abused by big tech.

Re: DigitalOcean S-1

#415

Post by jtdev »

Sebguer wrote: post #395
jtdev wrote: post #105

I was really considering moving from AWS to DO until I noticed this: https://www.digitalocean.com/company/contact/#abuse So anyone who's offended by content you might host on DO can report your site and some identity politics obsessed bureauocrat decides if you're cancelled or not...? The public cloud has turned into an Orwellian nightmare.

Are you mad about abuse@ emails on Whois lookups, too?

Those haven’t been used by the cancel culture mobs, so no. It seems that the WHOIS abuse process is unbiased and not rife with conflicts of interest.

Re: DigitalOcean S-1

#416

Post by addicted »

lloeki wrote: post #159
jiofih wrote: post #93

Earlier quoted context omitted.

> it was a product that looked remarkably similar to ours As a developer, DO never looked anything like it. Linode was expensive and on the same playfield as Rackspace and a ton of other cloud hosts, very different from the instantly-spin-up-a-tiny-vm-for-five-bucks model. Their web UI also has always been miles ahead. The competition also didn’t have SSD as an option until much later, and that was a HUGE selling poi…

> As a developer, DO never looked anything like it. The UI, the simplicity, SSDs, additional block storage... but also the API and its doc, as well as IPv6, regions, snapshots/backups, and availability. Later on, load balancers, object storage and k8s. All of that much simpler than AWS and both better thought out and more featureful than Linode or OVH. DO truly deserved their success.

Before I ever paid DO a cent, I made significant use of a lot of their incredible documentation on setting up various servers, setting up your confide correctly, etc.

Re: DigitalOcean S-1

#417

Post by cashewchoo »

RKearney wrote: post #160
cashewchoo wrote: post #56

Earlier quoted context omitted.

Their VPS pricing is competitive but pretty much everything else isn't. Specifically, I'm looking at EKS vs DO managed k8s, block storage for VPS's, and so on.

DO charges $0.10/GB per month for block storage, the same as AWS Lightsail charges for block storage. AWS also has Lightsail Containers which are far cheaper than EKS and is their DO/Linode/etc equivalent. Lightsail also offers load balancers for $18/mo compared to DO's $10, $30, or $60 per month. DO $15/mo managed DB 1G 1vCPU 10G SSD AWS $15/mo managed DB 1G 1vCPU 40G SSD I'm really not seeing how "pretty much every…

Huh, you're right. I guess the main place DO beats AWS is in their managed k8s pricing, which is funnily enough one of the main thing I use. Is lightsail containers more like docker or more like k8s? It reads to me that it's more like docker.

Re: DigitalOcean S-1

#418

Post by HappyDreamer »

kentonv wrote: post #386
chrisweekly wrote: post #383

Earlier quoted context omitted.

^ beyond annoyed w myself for writing "Cloudfront EdgeWorkers" (not even a thing) when I meant CloudFlare Workers.

We were going to call it that, bought the domain names and everything, but a competitor registered a trademark on the name the week before we launched. Oops. Remember kids, always register your trademarks.

What were you going to call it?

The competitor, was it DigitalOcean? (Or am I misunderstanding :-) )

Re: DigitalOcean S-1

#419

Post by kentonv »

HappyDreamer wrote: post #418
kentonv wrote: post #386

Earlier quoted context omitted.

We were going to call it that, bought the domain names and everything, but a competitor registered a trademark on the name the week before we launched. Oops. Remember kids, always register your trademarks.

What were you going to call it? The competitor, was it DigitalOcean? (Or am I misunderstanding :-) )

EdgeWorkers

(I work on Cloudflare Workers.)

(But in my previous comment I totally missed that chrisweekly said "Cloudfront" and not "Cloudflare", lol.)

Re: DigitalOcean S-1

#420

Post by creeble »

addicted wrote: post #416
lloeki wrote: post #159

Earlier quoted context omitted.

> As a developer, DO never looked anything like it. The UI, the simplicity, SSDs, additional block storage... but also the API and its doc, as well as IPv6, regions, snapshots/backups, and availability. Later on, load balancers, object storage and k8s. All of that much simpler than AWS and both better thought out and more featureful than Linode or OVH. DO truly deserved their success.

Before I ever paid DO a cent, I made significant use of a lot of their incredible documentation on setting up various servers, setting up your confide correctly, etc.

Gotta +1 that. Whenever I'm looking for a howto, I pray that there's a DO one already done. The quality (and brevity) is usually the best.
Post reply on HN