jwilliams

If you reduce your argument to the merits of each unique individual hire, then you're going to miss what is a very big and complex system.

If your argument is that all 15 of these employees gained employment on their attributes completely independent of gender -- and that gender plays no part -- then it should strike you as statistically improbable that all 15 would be men.

To me that seems outlandish to ignore. Clearly there must be some biases that lead to such a bifurcated outcome.

OR your argument is that men and women are different for some reason, which led to this situation. If that's your argument then you should make that argument.

Big fan of Netlify and use it for several sites. They have had some issues with DDoS attacks lately (and I've seen outages), but the blips seem to be under control.

The other one to consider is Google Firebase Static Hosting. Really excellent performance.

Some of these are probably very personal, but have worked for me.

- I try to arrive in the AM, stay up all day, and walk around as much as possible. Ideally walk in the sun. By the end of the day I'm shattered and usually will sleep well. Often I'm traveling for work, so I'll head direct to the office and work to keep busy. That first day can be tough, but after a couple of dips you can power though. After that you're pretty well set.

- I never nap (or even lie down) during the first day, that's always the thing that throws me off.

- For the flight: I have earplugs, noise cancelling headphones, and a heavy-duty eye mask. On occasion I'll play something calm on the headphones, but often it's just unplugged.

- I have one of these weird neck pillows - https://trtltravel.com/products/trtl-travel-pillow - works well for me as it stabilizes the head. If find the actual "pillows" don't really work.

- I try to eat in (or close to) the target time-zone a day before. On the plane I'll eat for sure, but veer to something light. I find the full meals make me lethargic the next day. Definitely eat at the "right times" when you arrive.

- I drink plenty of water, but I don't go crazy - I used to drink too much and my bladder would wake me up. I'll usually work out how much I want to/should drink (e.g.. two bottles) and then ration over the flight.

- I do have a small wine and sleeping tablets on the plane. Realize that's not for everyone, however (and probably unwise for some). But seems to work for me.

I regularly take long haul flights (12+ hours) and take Melatoin for Jet Lag.

I'll take twice. With the flights I take this usually works out to before sleeping on the plane (which ideally is the same/close to bed-time at the destination). And then the first night at the destination.

In combination with other tricks -- I've found it really effective.

> The chance for exit drops off a pretty steep curve as you go down the “top cities” list.

Exactly.

Which either means you're either: going to get a bad/mixed bag on terms -or- you need to raise in one of those cities as an outsider.

> The only thing required to raise a seed round is to convince people who have money to give you money

One of the huge issues I see is experienced (at least a subset "prestige") investors have the terms best suited to startups succeeding.

I've seen less experienced investors have draconian (almost nonsense) terms -- crazy terms that probably hurt their investments considerably. However, these investors are less accustomed to managing risk in a technology startup.

This is much, much less common in the SFBA ecosystem. However, if you look globally the startup investor maturity can be really poor.

The Squeezebox was my fave too. I owned the v1, v2 and v3. The audio was pretty amazing for the time. In the end I ended up using it as a digital streaming service.

The closest I've seen around now is https://roonlabs.com/ -- it's pricey but does many of the cool the things Slim/Squeeze used to do (and a little more).

Doesn't surprise me too much. It's a very busy route -- with a smaller selection of both airlines and airports. Plus Qantas is the perrenial corporate airline.

Notice that SFO to Newark makes the list further down. If you summed all Bay Area airports to all New York serving airports. Across all airlines... You might see a closer contest.

Having grown up in a hot place (Australia) - we think about ventilation a lot.

You're right - cross ventilation is really important. Generally you want to pull air in as low as possible as it's cooler. And then push out as high as possible. As "cross ventilation" somewhat implies, usually this is across a room or building for the best airflow.

A fan in a regular-height window and an open vent (a higher window, door louver) generally works pretty well. Even if it's the same window, it'll work ok.

The surcharges often are used against miles-based travel. You book the ticket one miles, but still get hit by various taxes and surcharges. Often it's a large chunk of the total fare.

Qantas has a "fuel surcharge" for a long period during high oil prices. This surcharge was literally to bill you for a base cost of their service. Arguably pure marketing.

Phew! I've been hoarding these for years and I'm down to my last two.

Accurate, fast, and ergonomics that makes five buttons work. Plus the corded version is very * light * this makes flicking a mouse around all day so much less of a strain.

In my experience, people have come to use expat to describe someone who is temporarily or provisionally living elsewhere (e.g. Gone to London to work for a few years). Immigrant is often used for people who have moved with a permanent intention.

Plus, the Mac App Store makes this a lot easier this time round. Apple will have a big "optimized for Air" sticker on the App. 99% of common apps will switch in no time.

I liked the model being discussed here. But I put the companies in very different spots, which I found to be a distraction.

Microsoft is one of the key example used. In their heyday they were deeply integrated. They had the whole stack and they sold it enterprise-level and enterprise-wide. Companies where "Microsoft shops" for this reason. This philosophy was one the the reasons Microsoft was late to the Internet party.

I also disagree deeply that "Facebook could lose all of its third party content providers overnight and still be a compelling service." Equally on that spectrum Facebook is right next to Google. Who surely couldn't lose all their third party content overnight?

Assuming all other variables stay the same -- with such a large revenue increase you'd assume some would be changing substantially.

That quote (from Amazon representatives) implies that revenue is non-linear to population -- but that expenses should be linear. I don't buy into that view. Especially in a "boom".

> They want you to use the web client.

I use the web app version exclusively -- based on that I don't agree.

Both the Twitter and Facebook Android/iOS web applications constantly push you to download the native client. They even get demanding sometimes. They want to be able to send you push notifications.

The Path social network did just that. Originally 50. Then 150 and now I believe 500.

A close friend has worked from home for a decade and has four kids. One routine that really works is he gets dressed for work every day. Just by adding a collared shirt, usually. Gets him in (and out of) the headspace and the kids get a clear signal that he's "working."

I'd second this -- and very occasionally I think of spinning off my current code into this.

If find PaaS can be a little too opinionated. You get boxed-in too quickly. Whereas IaaS is too raw. I had a bit of a head scratch when I recently moved to Google Cloud and was a bit flummoxed on where to put my (backend) session state. Similar experience trying to get Blue-Green deployments on GKE (Kubernetes).

I feel GCP/AWS and friends will get there. But for now there are definitely some gaps.

I've owned every single form factor of the MBP. I've loved all of them except for this latest "touchbar" version. Actually kicking myself for not returning it straight away.

Perhaps I'm reading to much into the title - but seems like pointless jobs have been around a very long time. What is the "rise" really referring to here?

International enforcement is a can of worms.

However, a lot of it is covered by:

1- US companies with a physical presence in the EU. They can fine that entity directly.

2- US companies will find they can't sell to EU businesses (B2B), as that means the EU company is carrying the can in terms of non-compliance.

3- The EU Member State could go via the International Courts. Or via some kind of bilateral agreement (e.g. Privacy Shield).

I expect #3 will need to egregious to really make sense.

However, I also expect a significant amount is already hovered up by #1 or #2. Certainly many of the cases that GDPR wants to target.

Additionally, the EU may cut deals with other states to bring in enforcement powers (fines).

On my (and other's) current read, it only applies when you are resident in the EU. Specifically:

> It applies to all companies processing and holding the personal data of data subjects residing in the European Union, regardless of the company’s location.

There is very little to be gained or added from pointing out this was optional -- for some reason the CTO decided to make a point of it.

I think the tone matters. Particularly for matters like this.

To my ear (and many who replied to that Tweet) this reads as "we've decided to do you a favor." Which is very much not the case.

The Tweet from the Twitter CTO on this: https://twitter.com/paraga/status/992135139994943488

"We are sharing this information to help people make an informed decision about their account security. We didn’t have to, but believe it’s the right thing to do."

The "we didn't have to" is a little jarring given the scale of this.

In the case of salts, the article admits "Don’t get me wrong, this does make it significantly harder to attack a leaked database to unmask every user..."

So salts definitely do help. And if you chose your salt well (e.g. global fixed/rotating plus local/temporal) you significantly increase your protection compared to not using a salt at all.

> It's not an issue of social mobility either, since people living in the bay area are some of the most socially mobile workforce there is.

The article focuses on non-tech workers. Who may not be socially mobile.

These areas need non-tech workers just as they need tech-workers. It's tough to have teachers work and live in Sunnyvale, where the median house price is pushing $2M. Many of your Lyft and Uber drivers will be coming in from 90+ minute commutes.

Oddly enough, I'm vaguely in favor of this -- but at the same time I don't think it should be implemented.

I've lived in a Unitary system (UK) through a bunch of different variations of a Federal system (NZ, Australia, Switzerland, USA, and even EU in a way) -- worth noticing Switzerland apparently was the inspiration for the Californian direct democracy.

Each really favors a different set of circumstances. It was shocking in Switzerland to be there for a few votes where people voted to very directly raise taxes. I couldn't imagine that in Australia.

Splitting up California has some appeal as a bar-room hypothetical -- but in some ways aggregating state powers might be better. e.g. Education, policing, infrastructure, is very, very, (very) fragmented. Many of these issues are because they are either directly or indirectly locally administered. I don't see this really reducing that fragmentation.

In fact -- I often wonder if the Bay Area would be better off as a combined municipality. Probably for issues like infrastructure, certainly.

Interested in the counterpoints to all that.

> There's a reason we all use jpegs over zipped bitmaps...

It's because it's an appropriate compression - just like xz can be? Not sure what you're actually suggesting here.