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

381–390 of 442 posts

Re: DigitalOcean S-1

#381

Post by frakkingcylons »

ivraatiems wrote: post #255
oliverjudge wrote: post #129

Earlier quoted context omitted.

Out of curiosity where did you move to?

I moved to BuyVM, https://buyvm.net/ . I had already been using their services for a few years, I just expanded on what I already had. They are not as large an enterprise as DigitalOcean, by a long shot, but the upside of that is you can speak with the owner and his small staff personally and get personal service. They made me a very good deal. I also know from their Discord that they have some conservative political…

It blows my mind that people will hang out in a Discord for a VPS provider and express their political opinions. Communities form around anything nowadays.

Re: DigitalOcean S-1

#382

Post by chrisweekly »

ksec wrote: post #345
chrisweekly wrote: post #337

Earlier quoted context omitted.

I'm a fan of DO too. In terms of "what's missing?", how about the equivalent of AWS Lambda@Edge or Cloudfront EdgeWorkers? ie, a NodeJS runtime as close to the end user as the nearest CDN edge.

The problem with Runtime at Edge is that they are extremely engineering intensive, given it isn't just hosting but the whole software stack involved. ( See CloudFlare Workers for Example ) Which is sort of outside the sweet spot that DO is currently enjoying or operating in. I am not sure if it is a sound strategic decision to persuade. Although I would certainly love to see competition in that area.

Well yeah, if you care enough about performance that it matters whether the "server" runtime is at the data center or the edge, it's kind of a given it won't all be completely automagic. But it is, thankfully, becoming an increasingly straightforward path to tread.

Re: DigitalOcean S-1

#383

Post by chrisweekly »

chrisweekly wrote: post #337
ksec wrote: post #324

Congrats to DO. Really like the direction DO is going. Which is something in between millions of small VPS firm and giant like AWS. It also forced Linode to React. And proved the space in Cloud Hosting exist, which company like Vultr and UpCloud are now joining. And I think their features are finally close to hitting the perfect spot. With all the essential like DBaS, Object Storage and K8s. They have also ( finally…

I'm a fan of DO too. In terms of "what's missing?", how about the equivalent of AWS Lambda@Edge or Cloudfront EdgeWorkers? ie, a NodeJS runtime as close to the end user as the nearest CDN edge.

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

Re: DigitalOcean S-1

#384

Post by crazygringo »

toast0 wrote: post #275
pqdbr wrote: post #265

If someone from DigitalOcean is reading this, PLEASE, we need a datacenter in Brazil.

Brazil is really expensive to operate in. A DC in Miami would reduce latency noticably, but should be reasonable costwise.

Curious why? Is it because of the insane taxes (100+%) on imported electronics? Employment taxes? Or some other reason?

Re: DigitalOcean S-1

#385

Post by nocman »

kasey_junk wrote: post #371
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…

Nearly every worker in the US is covered by an employment agreement that says they have to get pre-approval for moonlighting. It may or may not be legal in their jurisdiction but by paying people to do your interview process you potentially open them up to bad liabilities. That said it is completely unethical to make people do real work as part of an interview process. We collectively should name and shame any firm t…

"Nearly every worker in the US is covered by an employment agreement that says they have to get pre-approval for moonlighting."

This is not true.

I've can think of one employer my entire career that had conditions regarding work outside of my normal work hours.

Granted, if you worked for your competetors and they found out about it you could be fired due to trade secrets or conflicts of interest. I only remember one employer I had where I signed something with binding agreements related to other work (and, as it happens, that was perhaps the worst employer I ever had).

I know some employers in some regions do this, but it is a far cry from affecting "nearly every worker in the US". In fact, I am not aware of any of my friends in tech positions currently being under such an agreement (that is, an agreement requiring pre-approval for outside work). In fact I believe it is illegal under many circumstances in some states for an employer to require it (but don't rely on me for that, conditions/laws change, and I have had no reason to look into it recently). I do remember discussions about it in the not too distant past, however.

Re: DigitalOcean S-1

#386

Post by kentonv »

chrisweekly wrote: post #383
chrisweekly wrote: post #337

Earlier quoted context omitted.

I'm a fan of DO too. In terms of "what's missing?", how about the equivalent of AWS Lambda@Edge or Cloudfront EdgeWorkers? ie, a NodeJS runtime as close to the end user as the nearest CDN edge.

^ 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.

Re: DigitalOcean S-1

#387

Post by jldugger »

nocman wrote: post #385
kasey_junk wrote: post #371

Earlier quoted context omitted.

Nearly every worker in the US is covered by an employment agreement that says they have to get pre-approval for moonlighting. It may or may not be legal in their jurisdiction but by paying people to do your interview process you potentially open them up to bad liabilities. That said it is completely unethical to make people do real work as part of an interview process. We collectively should name and shame any firm t…

"Nearly every worker in the US is covered by an employment agreement that says they have to get pre-approval for moonlighting." This is not true. I've can think of one employer my entire career that had conditions regarding work outside of my normal work hours. Granted, if you worked for your competetors and they found out about it you could be fired due to trade secrets or conflicts of interest. I only remember one…

It was definitely part of the agreement when I worked in Univerisity IT, and part of the agreement when I accepted an offer from a FAANG company.

The language you're looking for in the contract is 'preponderance of time'.

Re: DigitalOcean S-1

#388

Post by teeray »

jeffparsons wrote: post #321
Ansil849 wrote: post #305

Earlier quoted context omitted.

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…

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…

One downside is that to do this properly, you probably should be sending out 1099s for all of those candidates. Depending on the number of open reqs out there, your payroll department may be less than thrilled with this idea. I’ve seen some teams that have tried to sidestep this by paying in gift cards, but that sure does seem to be playing with fire.

Re: DigitalOcean S-1

#389

Post by SMAAART »

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…

It's pretty simple: the interviewing process goes both ways. The company interviews the candidate, the candidate interviews the company.

If you feel that a request is unethical and it's not what you want in a company, well... you - as a candidate - can terminate the interviewing process.

Re: DigitalOcean S-1

#390

Post by dannyw »

ivraatiems wrote: post #255
oliverjudge wrote: post #129

Earlier quoted context omitted.

Out of curiosity where did you move to?

I moved to BuyVM, https://buyvm.net/ . I had already been using their services for a few years, I just expanded on what I already had. They are not as large an enterprise as DigitalOcean, by a long shot, but the upside of that is you can speak with the owner and his small staff personally and get personal service. They made me a very good deal. I also know from their Discord that they have some conservative political…

+1 to BuyVM. Happy customer for multiple years.

They are really the perfect size for me: big enough for multiple locations, R&D, and support coverage; but small enough so that you personally interact with the team, and you have trust that a random DMCA isn't going to end up with your site nuked.

The privacy-first stance (including allowing Tor exit nodes! sorely needed on independent infra!), and general willingness to help you ad-hoc (e.g. you wanna announce your own IP range? they'll do it, charge you a fair price for the work).

On the other hand, I woke up one day with my DigitalOcean droplet suspended and account banned, and support absolutely refuses to tell me why. My only suspicion is perhaps because I used the GitHub Student Pack even after I was no longer a student.

Post reply on HN