6,080 karma · joined January 5, 2017
Socials: - bsky.app/profile/benjaminschneider.ch - linkedin.com/in/schneiderbenjamin - benjaminschneider.ch - x.com/bschne
---
Because you can have a core set up for each branch and just pass to that vs. “context-switching” your core to execute the branch that ends up being taken?
What about them do you like as a design decision? (genuinely curious, as again, I don't understand it)
Are you saying proximity here more than offsets this vs. e.g. each core having its own cache as I think they do in a "normal" CPU? And if so, is this more true of ML inference workloads than other workloads, for some reason?
1. https://docs.tenstorrent.com/tenstorrent/v/tt-buda/hardware
This is the first time I read that big layoffs are "disastrous" for companies vs. some other approach in these situations (other maybe than the rather obvious fact that companies who are conducting mass layoffs are often in dire straits to begin with). I'm assuming "for companies" is implied here, because the way I read the sentence, the author is saying doing mass layoffs is misguided from the point of view of company management, not someone altruistically trying to maximize welfare in society overall or something like that. Does anyone have a good source for this?
If you do a trial of four-day workweeks, you're probably always going to have issues with the latter for any feasible setup. As you allude to, the companies that self-select into participating in such a trial are probably not a good representation of the wider economy, even if you randomize among them.
Now if you randomize rollout of four-day weeks at least among those willing to participate, and you didn't lose about 50% of participants between the start of your trial and the follow-up survey, you would at least get an unbiased estimate of what the policy did for those companies. But alas, they don't even do that part.
- They don't randomize pilots, so any effect you see is likely to be confounded
- In this publication, it appears there was ~50% attrition between the initial pilot and the follow-up study — again, a huge source of potential confounding
- As another example, in another publication, they showed a plot of GDP per capita against average working hours, and insinuated from the negative relationship that less working hours somehow made workers (causally) more productive, without even hinting at the obvious alternative explanation that people work less as they get more productive because they don't have to work as much to maintain standard of living.
I like that things like this are being tried, but I wish the research conducted on it were more intellectually honest and less obviously geared towards pursuing an agenda. The level of analysis here is more like a company marketing whitepaper than anything bordering on scientific.
Don't get me wrong, personally I think companies where it's feasible should just define minimum presence where the business needs it and leave it to employees where and when to do the work within those constraints depending on preferences and their situation. I don't have an axe to grind against working less (and in my circles it seems like many people are making this decision by reducing their workload to e.g. 80%, albeit at a corresponding salary cut). But the whole thing just seems a big disingenuous.
https://www.pv-magazine.com/2021/07/02/exploring-the-depths-...
1. People mention accuracy issues with longer contexts 2. People mention processing time issues with longer contexts 3. Something people haven't mentioned in this thread is cost -- even thought prompt tokens are usually cheaper than generated tokens, and Gemini seems to be cheaper than GPT-4, putting a whole knowledge base or 80-page document in the context is going to make every time you run that prompt quite expensive
I get the temptation, I got very curios too and my first impulse would be asking the same, but maybe it might be better to just sit down and make one's own list instead.