2. In some perl script I found this
 . . . . . .
 . . . . . .
# It works for me, only God understood how it is working
while (/(<\/[^>]+>)|(<[^>]+>)|(<[^>]+>)$|([^><]+)/go) {
            $startGene=$1;
            $beginChromosome=$2;
    
. . . . . .
 .. . . . . .
}

3. One more interesting message in Perl found …. It will must tickle you bone :)
open(my $fh, "<", "gene.txt")    or kill " Me if you think this is a mistake :$!";

4. From the Perl

  while () {  # "The Mothership Connection is here!"
    print “$_\n”; # Printing the offspring :)

5. Perl message
if ($1) { print “Just found a the error in chromosome !!!, yahoo…”; else { “That is not error, but mutation you moron!”;

6. One genome database curator walk in wine bar asked the bartender:
CREATE TABLE gene IF NOT EXISTS SexOnTheBeach;

1. Update new things continuously
As per my personal experience, it’s not always easy to work as a bioinformatician!  There are couple of reasons to say that; First computational part of biology make our life’s a little harder compared to other professional categories. The fact - for instance - that the technology cycle in the bioinformatics world is very short, the actual knowledge becomes outdated in a few months or years. Therefore, we need to learn continuously - new things get important. Second, to stay on top of things we really need the strong will to be good at our job. That's probably the most important characteristic to bioinformatician. They are usually an excellent knowledge worker with great technical abilities, and have the will to be that over decades!

2. Avoid the sentence "I did not know what to do!"
In our computational biology lab, we generally face lots of technical problems. But as you know, it's impossible to know everything to do the computational biology jobs ( Yup.. because you need diverse and multidisciplinary knowledge to understand biological problems and resolve their respective solutions), therefore it's absolutely necessary that a bioinformatician finds its way through a new topic. How I typically do that is I use google and I talk to other experts in our laboratory or online biostar community to find out what they think. "I did not know what to do!" should not be an argument for us.

3. To make oneself useful
Several time it does happen, you finished our task earlier than expected; in such cases if you have some time left then: Take a coffee and play chess; reversi, etc. In my case I take a rest. Afterwards I think about what I could do that helps the team to achieve its targets, 'cause some of my team mates probably didn't finish! (at least if I didn't met them at coffee bar !!)

4. Care for all
During my rigorous research duration; I attended several workshop organized by my University departments. I had a discussion with other research fellow, professors; I generally ask … what it really takes to make a team successful or to be a successful research leader. They always said: "Well, you need some caring people!" I think there is a lot truth in that statement. If we do not care about quality, timelines, good team culture, respectful communication (!!), clean code, if all this doesn’t matter to us, then I believe the probability is higher that we fail in research and analysis.

5. Be good with people
Because bioinformatician and computational biologist jobs typically involves to work in a (most wanted J cross-departmental!) team, therefore it's important that we're (more or less) good in dealing with other individuals. Everyone have their own strengths and weaknesses, just like us. It's important to treat all the research team mates with respect, regardless of their technical competence or contributions. Of course, sometimes people deserve a clear statement (!!!), but try to do these things one-on-one. Make sure nobody loses his face. Attend the meetings at the coffee bar; be good at table top soccer and go out once in a while to have a beer with your team. You know what I'm talking about.

At the end of a week I look back and I ask myself what I have produced. This could be paperwork, community days or (best!!) programming code. Always remember there is always a solution to a problem. Most of the times there are at least three solutions. So, don’t just blame, suggest a solution.

That's it. I am looking forward to your thoughts and comments!

the evolutionary history of genes and species, building phylogenetic trees of life
the contrasting roles of horizontal gene transfer and introgression in shaping evolution
the biology of symbioses, especially symbioses between eukaryotes and bacteria, and between parasites and their hosts
the processes that drive the evolution of pattern in the structure of chromosomes
the diversity of meiofauna, particularly tardigrades, nematodes and other Ecdysozoa
the genomics of extremophilia

More at https://www.sanger.ac.uk/group/blaxter-group/

Master's degree in bioinformatics, computer science, molecular biology, or related field
One year of experience in analyzing RNA-Seq data
In lieu of a degree, consideration will be given to an equivalent combination of related education and required work experience.
Understanding of molecular biology, biochemistry, and genetics
Proficiency in writing scripts using Perl, Python, Java, or equivalent languages
Proficiency in R and UNIX/LINUX
Knowledge of genomics, alignment, annotation, bioinformatics, concepts of sequence assembly
Highly motivated and detail-oriented
Ability, interest, and curiosity to learn new skills
Must possess strong communication skills to work effectively with users across disciplines
Ability to work independently and as part of a multi-disciplinary team
Strong visual, verbal, and written communication skills
Excellent time organizational skills
Preferred:

Experience writing software or building software pipelines
Experience with oncology-specific public databases including TCGA
Experience with deploying and/or running software on high-performance computational systems
Statistical and experimental design knowledge
Additional Information:

This position is contingent on the availability of funding
Purdue will not sponsor employment authorization for this position
A background check will be required for employment in this position
FLSA: Exempt (Not Eligible For Overtime)
Retirement Eligibility: Defined Contribution Waiting Period
Purdue University is an EOE/AA employer. All individuals, including minorities, women, individuals with disabilities, and veterans are encouraged to apply

More at https://careers.purdue.edu/job/West-Lafayette-Bioinformatician-Purdue-Cancer-Center-IN-47906/686617600/

1. Make friends with local bioinformatics groups
2. Talk to your computing group
3. Obtain clear expectations
4. Rewrite your job description
5. Papers
6. Attend bioinformatics meetings
7. Try first, ask later

Address of the bookmark: http://biomickwatson.wordpress.com/2013/04/23/a-guide-for-the-lonely-bioinformatician/