Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create a list of blog topics... #4

Open
crmackay opened this issue Feb 27, 2015 · 1 comment
Open

create a list of blog topics... #4

crmackay opened this issue Feb 27, 2015 · 1 comment
Assignees
Labels

Comments

@crmackay
Copy link
Member

I'm just going to leave this here for now so I can remember to do this...

@crmackay crmackay added the todo label Feb 27, 2015
@crmackay crmackay self-assigned this Feb 27, 2015
@crmackay
Copy link
Member Author

Here is my list:

Ideas for blog posts on new website:

Categories:

  • python
  • unix
  • R
  • biotools
  • stats/data analysis
  • C/C++(golang?)
  • julia?

note: you can have multiple “tags” and categories per article

Python 2

  • topics we didn’t get to:
    • useful python modules:
    • pysam, biopython, etc.
    • better explanation on packages and modules
    • using a RDB instead of a dictionary(map)
    • the conundrum of parallel processing with python (you can do it...but should you?)
    • matplotlib - with ggplot flair, but easier syntax (depending on who you ask)
    • virtualenv's and dependency management
    • gzip’ed files
    • pandas!

Biotools

  • bioinformatics in general
    • ??? people interested in diving into how these programs work…??
      • alignment algorithms, burrows wheeler transform, etc.
    • stats models:
      • hidden markov, dynamic bayesian networks, expectation maximization (a la RSEM), etc.
  • running scripts on the cluster

best practices

  • source control (git and github)
  • electronic lab notebook
  • coding environment (eg “Hi I’m Jill/Arjen/Mike/Nick, and this is how I work”)
  • getting a DOI for your code
  • properly documenting code
  • writing and using effective unit tests
  • documenting pipelines and scripts --> facilitating the repeatability/reproducibility of your work...saying "in house scripts were used" in a manuscript and leaving it there is not okay (although apparently it is)
  • continuous integration (Travis CI or others)

Other

  • using public databases/datasets
  • LaTeX tutorial and template walkthrough

feel free to add more in the comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant