Id say every 3rd deployment or so, especially when new features are added, there is a lot of stress around cutting a release and deploying. People on the team become extra scrutinous of people who break the release build or don't have the features completed, or havent submitted enough tickets. Which, as a manager I appreciate the peer pressure, but I doubt the stress is good for moral of the members who are on the receiving end of it and I think the same feedback without the urgency behind it would be pedagogically more valuable.
Second, when a release is made and a bug is found there are branches mad from main (not develop) to fix the bugs, that must then be merged into develop (referred to as a merge-back) which increases surface area for errors as well as more time spend untangling the emerging web of branches. Now, in the hands of a capable engineer this isnt a massive lift, but also there are processes to automate all of this and that capability would be better spent day dreaming about a side project as far as I am concerned.
Ahh, I should have watched the video before I had the knee-jerk reaction to be so charitable. They could have just done what grad students are basically trained to do: use your narrow expertise to bullshit people and tie in some buzzwords that grant funding agencies like to hear. I hope I am just being cynical and that YC knows what they are doing here.
Keep in mind that this article was not written by the founders of Verge Genomics, but by a journalist who "writes about internet culture, social networks, and consumer-facing technology." So they are probably going to use speech that will make the more science/biotech literate person bristle.
I'm going to presume that I don't really understand the company then, because the founders and advisers should certainly know more than I do about drug discovery.
I have a hard time believing that large pharma research labs are limiting themselves to single loci for a given disease phenotype. But if they are, it makes sense why YC would see value in this.
I'm working on a webapp that lets people advertise any arbitrary event going on with google maps integration, and with an eye towards making communication between users easy (commenting, forums, private messaging). I'm not confident that many people would find such an app to be at all useful, but it is simple enough to get my hands dirty in webdev. Will hopefully make my first release by the end of the week.
Could you expand a bit on the intangible benefits of a cs PhD? I have recently been offered admission to a top 10 program and am struggling to decided between it and staying in industry.
Second, when a release is made and a bug is found there are branches mad from main (not develop) to fix the bugs, that must then be merged into develop (referred to as a merge-back) which increases surface area for errors as well as more time spend untangling the emerging web of branches. Now, in the hands of a capable engineer this isnt a massive lift, but also there are processes to automate all of this and that capability would be better spent day dreaming about a side project as far as I am concerned.
Have I persuaded you?