Skip to content

made it bold #13

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.

Sign up for GitHub

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

Open
mikemhenry wants to merge 1 commit into
base: master
Choose a base branch
from
Open

made it bold #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

#FOMMS Workshop Topics

In computational chemistry, we spend a *lot* of time working with computers. However, very few of us have formal training in computer programming. There is little short-term incentive for us to fix this, which has led us to adopt some inefficient programming practices. Some interesting reads on this include [*Nobody ever gets credit for fixing problems that never happened*](http://web.mit.edu/nelsonr/www/Repenning=Sterman_CMR_su01_.pdf), [*Why do many talented scientists write horrible software?*](http://academia.stackexchange.com/questions/17781/why-do-many-talented-scientists-write-horrible-software), and [*Why learning to code is so damn hard*](http://www.vikingcodeschool.com/posts/why-learning-to-code-is-so-damn-hard).
In computational chemistry, we spend a **lot** of time working with computers. However, very few of us have formal training in computer programming. There is little short-term incentive for us to fix this, which has led us to adopt some inefficient programming practices. Some interesting reads on this include [*Nobody ever gets credit for fixing problems that never happened*](http://web.mit.edu/nelsonr/www/Repenning=Sterman_CMR_su01_.pdf), [*Why do many talented scientists write horrible software?*](http://academia.stackexchange.com/questions/17781/why-do-many-talented-scientists-write-horrible-software), and [*Why learning to code is so damn hard*](http://www.vikingcodeschool.com/posts/why-learning-to-code-is-so-damn-hard).

This workshop is designed around the "low-hanging fruit" of best practices - simple fixes that will result in big improvements to your productivity. The topics are admittedly boring, but doing things right will save you from having to think about them again.

Expand Down