Ten simple rules for training scientists to make better software - doi.org/10.1371/journal.pcbi.1

Simon Tournier

@zimoun@sciences.re

@danielskatz @pierrepo Well, every programming session should start with “python -c 'import this'“ and reading the Zen of Python, then end with reading it again in order to reflect on the produced code. For example:

«

Flat is better than nested.
Sparse is better than dense.
Readability counts.

Now is better than never.
Although never is often better than right now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
»

September 19, 2024 at 10:13:07 AM

Elk Logo

Welcome to Elk!

Elk is a nimble Mastodon web client. You can login to your Mastodon account and use it to interact with the fediverse.

Expect some bugs and missing features here and there. Elk is Open Source and we're actively improving it as a community project. Join us and let's build it together!

If you'd like to report a bug, help us testing, give feedback, or contribute, reach out to us on GitHub and get involved.

To boost development, you can sponsor the Team through GitHub Sponsors. We hope you enjoy Elk!

三咲智子 Kevin DengDaniel RoePatakTAKAHASHI ShuujiJoaquín SánchezAnthony Fu

The Elk Team