Introduction to Genomics for Engineers
learngenomics.dev
Introduction to Genomics for Engineers
1–10 of 84 posts
Re: Introduction to Genomics for Engineers
#2Really glad to see this, but it reminds me of the earlier HN post that said engineers don't go into genomics because it doesn't pay and requires a lot of investment in learning biology.
Re: Introduction to Genomics for Engineers
#3Really glad to see this, but it reminds me of the earlier HN post that said engineers don't go into genomics because it doesn't pay and requires a lot of investment in learning biology.
https://news.ycombinator.com/item?id=33671264
^Most recent discussion I’ve seen.
I worked in genomics, left this year because you’re underpaid and often disregarded “IT-help” that assists wildly over-educated and underpaid people driving the actual research in 95% of cases.
Re: Introduction to Genomics for Engineers
#4Nicee, but I feel like really the only thing you need to know as an eng is DNA -> RNA -> Protein. Sometimes RNA -> DNA via reverse transcriptase.
Everything else is just normal Python scripting.
Re: Introduction to Genomics for Engineers
#5Really glad to see this, but it reminds me of the earlier HN post that said engineers don't go into genomics because it doesn't pay and requires a lot of investment in learning biology.
https://news.ycombinator.com/item?id=33671264 ^Most recent discussion I’ve seen. I worked in genomics, left this year because you’re underpaid and often disregarded “IT-help” that assists wildly over-educated and underpaid people driving the actual research in 95% of cases.
Thats why you stay though, the people are interesting and the work is meaningful and you directly see the fruits of your labors whilst contributing to a codebase that is by default open source.
Re: Introduction to Genomics for Engineers
#6Earlier quoted context omitted.
https://news.ycombinator.com/item?id=33671264 ^Most recent discussion I’ve seen. I worked in genomics, left this year because you’re underpaid and often disregarded “IT-help” that assists wildly over-educated and underpaid people driving the actual research in 95% of cases.
Thats why you stay though, the people are interesting and the work is meaningful and you directly see the fruits of your labors whilst contributing to a codebase that is by default open source.
[deleted]
Re: Introduction to Genomics for Engineers
#7Earlier quoted context omitted.
https://news.ycombinator.com/item?id=33671264 ^Most recent discussion I’ve seen. I worked in genomics, left this year because you’re underpaid and often disregarded “IT-help” that assists wildly over-educated and underpaid people driving the actual research in 95% of cases.
Thats why you stay though, the people are interesting and the work is meaningful and you directly see the fruits of your labors whilst contributing to a codebase that is by default open source.
No post body was provided.
Re: Introduction to Genomics for Engineers
#8Earlier quoted context omitted.
https://news.ycombinator.com/item?id=33671264 ^Most recent discussion I’ve seen. I worked in genomics, left this year because you’re underpaid and often disregarded “IT-help” that assists wildly over-educated and underpaid people driving the actual research in 95% of cases.
Thats why you stay though, the people are interesting and the work is meaningful and you directly see the fruits of your labors whilst contributing to a codebase that is by default open source.
People aren’t anymore interesting than anywhere else.
Work is no more meaningful than anywhere else. It’s a big “selling point” for the industry, but it’s just a way to get people to get paid less (yay you’re making the world better than all those garbage people serving coffee or healing sick people or keeping your lights on or optimizing the routes of the goods you have delivered). If you want sustainable systems, trying to be a martyr and work for less only screws this up long term.
Code-base is not open-source. It’s biotech R&D, there is zero culture of sharing outside your organization within industry. You can present high-level things at conferences and such, but you’ll have to rip the raw data out of their dead hands…not happening.
I’ve been in too many conversations about building software to serve larger groups in this industry. It can happen, but it can’t currently and nobody wants it. Confident someone will find a solution, but everyone wants their own home-grown solutions in their own walled-gardens that no one has access to.
Data and the things it can/can’t tell you are held tightly in these companies. I was at a pharma a couple years ago where researchers were explicitly told they COULD NOT test certain compounds in a certain way because they did not want a trace of this data to exist while they were trying to push compounds through the FDA.
Re: Introduction to Genomics for Engineers
#9Nicee, but I feel like really the only thing you need to know as an eng is DNA -> RNA -> Protein. Sometimes RNA -> DNA via reverse transcriptase. Everything else is just normal Python scripting.
...no. There is more to genomics than python scripting. This is widely incorrect assumption.
A new generation of bioinformaticians and computational biologists are using rust, go, and the web to create, share and deliver.
Checkout nextclade.org
Re: Introduction to Genomics for Engineers
#10Nicee, but I feel like really the only thing you need to know as an eng is DNA -> RNA -> Protein. Sometimes RNA -> DNA via reverse transcriptase. Everything else is just normal Python scripting.
You do know that there are things like epigenetics, DNA repair (using specialized proteins), RNAi, post-translational modifications, metabolites (just to name a few)?