Is that still true or has the gap narrowed? Or have GPUs always been similar across the board and it’s CPUs that have more disparity?

We're building an end-to-end portfolio construction system to support FTIS, a $100bn multi-asset investment manager within FT. This is a front office role that will help guide our quantitative staff as we build out this new system. This project is a strategic objective for FTIS, highly visible, and frankly one of the most fun jobs in the industry.

We're looking for mid to senior level researchers or developers with strong buy-side backgrounds who can help translate our investment process into a robust, scalable, and approachable design.

Reach out with any questions - dan.nadler (at) franklintempleton (dot) com

Apply here: https://franklintempleton.wd5.myworkdayjobs.com/Primary-Exte...

Ideally, the number is one time. As in one conversation where the person walks away understanding the answer. If I have to have that conversation more than once it’s a problem.

Obviously there’s nuance - it can take time to get your head around a new concept or hard problem. But in any case, I like that as one dimension when thinking about a person’s skill/level/potential.

Some quick back of the envelope says that it would take around 35 MWh to get to 40 years old (2000 kcal per day)

Rescue and abort options are also much harder. The moon is close enough to easily resupply or rescue people on the surface, mars is much harder.

The first time I published a site, I was surprised by how much traffic came from mobile devices, even though my page was intended for desktop users. I really shouldn’t have been surprised, but fortunately I had some basic analytics and saw fairly quickly how bad my bounce rate was on mobile and was able to work on it a bit.

I was reading mostly neuroscience papers when I was taught this method as an undergrad (though the details are a bit fuzzy these days).

I’d bet it also varies quite a bit with expertise/familiarity with the material. A newcomer will have a hard time understanding the methodology of a niche paper in neuroscience, for example, but the concepts communicated in the abstract and other summary sections are quite valuable.

I would read it start to finish. Later on, I learned to read the abstract, then jump to either the conclusion or some specific part of the motivation or results that was interesting. To be fair, I’m still not great at reading these kinds of things, but from what I understand, reading it start to finish is usually not the best approach.

So, I think I agree that this is not really common with code, but maybe this can be generalized a bit.

Driving in and around the suburbs is what I was talking about.

Cycling simply isn’t viable to large swaths of the US. There isn’t an easy answer to this either, given that you’d probably need to tear down entire neighborhoods and rebuild a more dense town

Also, hi James! :)