13,477 karma · joined November 27, 2007
@kevinrschultz on Twitter
[ my public key: https://keybase.io/kevinrschultz; my proof: https://keybase.io/kevinrschultz/sigs/k_lxivVNv1dGoldx9bUPJ3nVxNnH-ULgOlVj8L-OX08 ]
The existence of the foundation is orthogonal to FB's internal investment and usage of GraphQL, which was and will continue to be significant.
https://help.twitter.com/en/rules-and-policies/hateful-condu...
The hard path has been to found a company with the business model of money directly off an open source project. That's doesn't seem to work out in most cases, and the gates the companies put up to charge money piss everyone off.
I'm not convinced the politics of subsidizing education get better after that. There's a very high risk that a large and powerful swath of the country reacts to it with "I worked my ass off to pay for my kids to go to college, why should I subsidize yours?" The resulting increase in inequality is bad for society as a whole, but honestly it's a feature for most upper income parents.
It would probably put some pricing pressure on college, but the predictable knock-on effects are really really bad.
Craftsmanship matters and you just won't become an expert building exactly the number that you need for yourself.
It's actually in your best interest as the hiring company to not find out if the person is pregnant or expecting to have a child. Let's say that you decided not to hire someone for a set of reasons unrelated to pregnancy, but along the way you asked the candidate if they were planning to get pregnant. Good luck proving that you didn't make the hiring decision on the basis of knowing they would take leave. Which of course is illegal under the Pregnancy Discrimination Act. This is why most companies make it a policy that you can not ask these kinds of questions so as not to taint the interview (even though technically it's not illegal to ask the questions, it's just illegal to use them as a basis for your decision).
As a candidate you might actually be acting more in the interest of the company to not tell them you are going to be having a child so as not to put them in that position? I honestly haven't thought through it that much so I could be convinced of a different opinion.
If you're planning to continue working after having a child, I think you should go about your career as if the pregnancy wasn't happening and just take the leave as appropriate. If that means you work 6 weeks before leave, so be it. You'll be back after leave to continue on.
What would the company do if instead of getting pregnant you got hit by a bus one day? I had to take 2 months of medical leave on 2 weeks notice when I got deathly ill, that was way less notice than a pregnancy. The startup I was at had only 12 people and they handled it. I'm unconvinced by all these arguments that it's too much of a hardship for companies to deal with their employees having a life.
Man do I have bad news for you, my company gives people bonuses when they have children.
Guess what, in our industry the people that are planning to have kids are also very likely to be senior and experienced. They're hard to recruit. Consider leave as part of the cost of hiring good people.
If you're not doing things like this, you're not actually competing for top talent.
The other pathway is a prestigious college / MBA program or working their way up through one of the big tech companies and then leaving to start their own thing.
I've seen very few "former lead engineer at X startup founded their own company" stories, and that was literally what I was trying to do with my career for probably 5-7 years.
I am familiar with most of the other tools mentioned here (e.g. SonarJava) from my time doing Java development outside of Facebook and never had a collision in my head because this project is not actually a library or tool for Java. It's a standalone Electron app that works on iOS and Android for debugging purposes, the only Java part is incidental in the Android app (and could be Kotlin or C++ or whatever you want).
Using the banks to cut off commerce across borders is an enforcement action for what countries agree are crimes - terrorism, money laundering, fraud, etc. It takes a lot of political willpower and negotiation to use that tool. I sincerely doubt it would be used against American websites that choose to not serve the EU.
Every single blog post had a set of people raging that we were assholes for doing this, but the reality was the cost of compliance just didn't make sense for the MVP. It was high 5 figures in cost which was just too much at the time. If we had achieved product market fit then the obvious move would have been to do that compliance to gain more customers, but we never quite got there.
I doubt GDPR gets to that level of cost, so the ROI looks a bit different. But I still think it's a reasonable decision to say "I simply won't do business in the EU because it costs more than I'll gain". A lot of companies also don't bother to go through the effort of printing the dual language labels required to sell their products in Canada, even though it's a decent sized market close to the US.
Tech, specifically the internet, has grown without regulation for a long time. But that era is over. These kind of decisions are routine in non-internet businesses where distribution, borders, and regulations exist. I suspect we're going to have to think a lot more about this in our work in the future.