Tullio Facchinetti
Tag cloud
Picture wall
Daily
RSS Feed
  • RSS Feed
  • ATOM Feed
  • Daily Feed
Filters

Links per page

  • 20 links
  • 50 links
  • 100 links

Display

Filter untagged links
5 results tagged style  ✕
Novelist Cormac McCarthy’s tips on how to write a great science paper https://www.nature.com/articles/d41586-019-02918-5
Sat 28 Sep 2019 08:51:34 PM CEST
QRCode

The Pulitzer prizewinner shares his advice for pleasing readers, editors and yourself.

guidelines research style writing
black: The uncompromising Python code formatter https://github.com/python/black
Sat 18 May 2019 12:43:59 AM CEST
QRCode

image

Black is the uncompromising Python code formatter. By using it, you agree to cede control over minutiae of hand-formatting. In return, Black gives you speed, determinism, and freedom from pycodestyle nagging about formatting. You will save time and mental energy for more important matters.

Blackened code looks the same regardless of the project you're reading. Formatting becomes transparent after a while and you can focus on the content instead.

Black makes code review faster by producing the smallest diffs possible.

formatting python software source_code style
Where should citations be placed relative to punctuation (e.g., full stops and commas)? https://academia.stackexchange.com/questions/85477/where-should-citations-be-placed-relative-to-punctuation-e-g-full-stops-and-c
Wed 30 Jan 2019 10:23:32 PM CET
QRCode

Which options are preferable:

  1. More coffee is always better. [XY]
  2. More coffee is always better [XY].
  3. More coffee is always better[XY].
  4. More coffee is always better.[XY]
  5. According to [XY], more coffee is always better.
  6. According to XY[XY], more coffee is always better.
  7. According to XY [XY], more coffee is always better.
  8. According to XY, [XY] more coffee is always better.
  9. According to XY,[XY] more coffee is always better.
  10. According to XY, more coffee is always better [XY].
  11. According to XY, more coffee is always better. [XY]
guidelines style writing
Semantic Commit Messages https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716
Sat 06 Oct 2018 05:59:56 PM CEST
QRCode

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

where <scope> is optional.

Example
feat: add hat wobble
^--^  ^------------^
|     |
|     +-> Summary in present tense.
|
+-------> Type: chore, docs, feat, fix, refactor, style, or test.

More Examples:

  • feat: new feature for the user, not a new feature for build script
  • fix: bug fix for the user, not a fix to a build script
  • docs: changes to the documentation
  • style: formatting, missing semi colons, etc; no production code change
  • refactor: refactoring production code, eg. renaming a variable
  • test: adding missing tests, refactoring tests; no production code change
  • chore: updating grunt tasks etc; no production code change
article programming style versioning
C Coding Standard https://users.ece.cmu.edu/~eno/coding/CCodingStandard.html
Sat 06 Oct 2018 05:58:11 PM CEST
QRCode

Adapted from http://www.possibility.com/Cpp/CppCodingStandard.html and NetBSD's style guidelines.

5_stars article c guidelines programming style
3660 links
Shaarli - The personal, minimalist, super-fast, database free, bookmarking service by the Shaarli community - Theme by kalvn