Do you have a source for this? We've always used white noise.
719 karma · joined February 25, 2014
Do you have a source for this? We've always used white noise.
That being said, I've seen cases where the take home assignment is actual company work, in which case I 100% agree you should be paid.
FWIW, I have a close family member who works for Oracle and they claim that they're sincerely trying to be developer/start-up friendly in hopes to gain traction in the cloud space. I get that the default is to assume there is always a hidden agenda with Oracle, but it is possible they're trying to show some good faith here.
Heroku, on the other hand has been a hassle-free solution for my company over the past 7 years, and short of a few outages (which were actually the fault of AWS from what I remember), it has been absolutely reliable.
It is one thing to claim that the your marketplace is doing developers a service by distributing and putting their apps in front of their massive audience. Fine - collect 30% for downloads/subscriptions that come that way. Unfortunately, there is effectively no other way to consume software on these devices. Keep your 30% of downloads/subscriptions that originate from your marketplace, but let me opt-out of your marketplace and still get my product to my customers without your help.
(Note: I still think React is an awesome library! I'm sure there are devs that are super productive with it too. It just wasn't the best fit for me and my company)
That being said, if I was in a new city with no friends or family, I would 100% want to have an office to go to.
There are countless examples of companies large and small who have found massive amounts of success switching to a remote based methodology. Saying that this is objectively wrong and that these folks are not in "their right mind" makes your argument, that could otherwise be valid, look foolish.
It largely depends on what kind of work you're doing. For software development, I could just as easily claim that it is objectively true that asynchronous communication and a freedom from non-technical people tapping you on the shoulder 10 times a day is objectively easier.
> Why aren't there just as many (or more) articles about making WFO (Working From Office)
Because that blog (or more likely book) has already been written and re-written for the past 100 years. WFH is a somewhat new phenomenon in the age of modern internet and broadband.
Hopefully, Apple will publically denounce this act, putting stronger pressure on representatives and increasing public awareness.