575 karma · joined September 11, 2014
I think there's a mistake in the article, her website goes into more detail:
https://soutien-a-emilie0.webnode.fr/lhistoire/ (gtranslate)
> Emilie is therefore working that day on samples of mice infected with strains of human prions. It is important to stress here that these were human strains and not animal strains, the species barrier no longer protecting, the infectivity of the pathogens handled by Emilie was therefore total.
the very hungry caterpillar is somewhat unique in that she absolutely loves the illustrations, like no other book. she really sits still and gazes agog at them, especially that picture of the sun at the beginning.
Anyone know why this is? seems fairly arbitrary...why not have 1,2,3,4,5?
I'm struggling to picture this, do you have any links I could read?
Is for example, the atmosphere seeming different a real physical phenomenon that could be detected by ML?
eg: https://news.ycombinator.com/item?id=26567842
https://news.ycombinator.com/item?id=26557175
That phase wipes off >99% of the total energy required to get to 0 m/s, which is pretty remarkable because Mars' atmosphere is ~1% of Earth's.
It seems to be about the right level of abstraction for "semi-structured" data, it feels balanced between block and WYSIWYG editing, and that's a hard balance to strike.
I also definitely sympathise with those that use the classic editor because it's what they know, and that's fine. We should celebrate any architecture that supports choice.
yes but it's incredibly complicated, radiation comes from multiple sources. See https://en.wikipedia.org/wiki/South_Atlantic_Anomaly and https://en.wikipedia.org/wiki/Van_Allen_radiation_belt
That said the way he generates a table is in no way idiomatic react, where you take an array of objects and map the data on to the table.
In terms of code generation, is it actually any better than using an emmet expression? `table>tr*10>td` (I've probably mangled that). What's interesting with the table example is probably the combination of "knowledge" and knowing enough about a DSL to generate a coherent output.
I agree re cherry picking, though the initial fine tuning set is extraordinarily small, just 2 items. Generating a much larger dataset shouldn't actually be that tricky, though perhaps getting agreement on how to actually describe a layout in plain English might be more of a challenge. Would a plethora of descriptions for the same layout be a bad thing?
Lastly, I've been using TabNine (https://www.tabnine.com/) for the past few months, and I'm convinced that some kind of language model text generation is going to change how we write code, it's already changed it for me. If I signal my intent pretty clearly up front, I would say most of my coding is now tabbing and occasionally pressing the down arrow. Even writing comments becomes an exercise writing an initial three of four words and tabbing out the rest. Ditto tests.
And i watch a lot of simracing with multiple streamers streaming the same race.