Hacker News new | past | comments | ask | show | jobs | submit | rook166's comments login

> If you ask a gain-of-function proponent, they will say that by creating viruses that might emerge in nature, you get to understand zoonotic jumps from animals to humans better and possibly prevent them. Specifically, you get a head-start on developing vaccines for them. This possibility of curing future diseases might be true in some cases. But Pfizer’s COVID-19 vaccine was developed in a few hours back in January 2020.

I've been wondering about this for the last few months, I feel like this "better prepare for future viruses" argument is substantially weaker now — coronaviruses were a well-known group of viruses, there was already research directed at gain-of-function work for this family of viruses, and yet as far as I'm aware the mRNA vaccines that were developed derived no benefit from any of that research. So whether or not the virus came from a lab, why should we fund this kind of work since it seems not to be very useful?


There's more to GoF research than developing vaccines. Sometimes its trying to understand host virus interaction, virus evolution, zoonotic events. The list goes on. The majority of primary research is not at all interested in vaccine development.

For coronaviruses they're a huge family of viruses. Sometimes it's not transferable between species


The argument the post is presenting seems like it could be a straw man. Gain-of-function research would surely be useful to things other than vaccines, which might even be more important than vaccines? For example, figuring out in what conditions viruses jump hosts and therefore how to reduce the likelihood of new epidemics.


Why wouldn't Gain-of-Function be helpful for research on oncolytic viruses (viruses that target cancer cells)?


I think that's probably at least somewhat true, although from the article it seems like the argument against that selection bias is that a) COVID-19 seems to be substantially more "tuned" than its cousins SARS and MERS, and b) there is as-yet no strong evidence of pre-pandemic strains of a COVID-19 progenitor (either in humans or animals).


As someone who's both gone through a DS bootcamp (not Insight but similar) and also been on the hiring/interviewing side, I've thought a fair bit about this.

First off, have you tried applying for DS jobs yet? What were the results? As others have alluded to, a bootcamp is not a mandatory prerequisite for a DS job, and is no substitute for on-the-job experience. If you're finding that you can generally get callbacks from recruiters/hiring managers based on the strength of your current resume (or have friends in the industry who can give you referrals), then you probably ought to just keep up with that approach. You can refine your resume and interviewing technique based on the parts of the interview process you struggle most with, and eventually the pseudorandom number generator that is interviewing will work out for you.

If you're submitting your resume to lots of companies and never hearing anything back, then a bootcamp might make sense. My general advice for a bootcamp is to look for one that meets your needs and has incentives aligned with yours. In general I think that is probably a better way to choose a bootcamp than trying to figure out which ones employers respect the most. There's no one right answer to that question, and honestly that answer can change over time: you can see in some of the other comments that it looks like the Insight fellowship has changed significantly in response to the pandemic, and I know that the bootcamp I did changed fairly substantially in the years after my cohort. IMO none of the existing bootcamps have the history or pedigree at this point for their name to mean a whole lot on its own.

Generally in my experience bootcamps tend to be split into two groups: 6-8 week project-based ones, mostly focused on polishing candidates that are already close to being ready to get DS jobs; and 3-6 month training-focused ones, designed to upskill people who have a minimum baseline set of skills but are not particularly close to being competitive DS candidates. If you have already been doing some reading on the side and mostly need an introduction to hiring companies (and maybe a project to talk about), shorter fellowships make more sense. If you think you need more training in core DS concepts, then a longer program may be better. Prefer programs that only make money when you get a job (either via as your recruiter or via an income share) versus programs that charge an upfront tuition, although note that the former tend to be harder to get into and may actually exclude you from some jobs immediately after graduation (if they work as your recruiters, large companies with their own recruiting arms may not be willing to pay the extra recruiter fees).

Finally, if you're in a bootcamp, make sure that you're doing something to differentiate you from your peers. The first time I saw a bootcamp candidate talk about their model to find ideal jogging routes based on RunKeeper data hosted in a Flask app using the Google Maps API it was super impressive; the third time I saw a candidate present this same basic project was much less so — it was obvious that to save time all the bootcamp participants had been taught the same basic stack and given a lot of hints for what kinds of projects they could do.


For any Python users, there's a library that automates mutation testing by parsing the AST: https://github.com/EvanKepner/mutatest


And for property-based testing there's Hypothesis too: https://hypothesis.readthedocs.io/en/latest/


There's mutmut (I'm the maintainer), cosmic-ray and mutpy too. In fact those are the established players. I have never heard of mutate st before! I will have to try it.


Oh cool, I'd never heard of those, funny enough. I'll have to look into those myself!


Almost - stars orbit with approximately the same velocity, not period.


You beat me to it while I was looking for references. =)

"The stars and gas in the Milky Way rotate about its center differentially, meaning that the rotation period varies with location. As is typical for spiral galaxies, the orbital speed of most stars in the Milky Way does not depend strongly on their distance from the center. Away from the central bulge or outer rim, the typical stellar orbital speed is between 210 ± 10 km/s (470,000 ± 22,000 mph). Hence the orbital period of the typical star is directly proportional only to the length of the path traveled."

https://en.m.wikipedia.org/wiki/Milky_Way#Galactic_rotation


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: