Skip to content

Instantly share code, notes, and snippets.

@dkapila
dkapila / slack_export_to_tft_tools.py
Last active October 1, 2021 21:22
Prepare Slack Export for Roam/Logseq/Obsidian
import pandas as pd
import json
import glob
import os
from pathlib import Path
import re
import datetime
from datetime import timezone
import pytz
@adbutterfield
adbutterfield / prettier.config.js
Last active February 21, 2024 05:17
Default prettier config with comments and links to prettier rules
module.exports = {
/**
* Print Width
* https://prettier.io/docs/en/options.html#print-width
*
* Specify the line length that the printer will wrap on.
*
* printWidth: <int>
* default: 80
*/
@joshbuchea
joshbuchea / semantic-commit-messages.md
Last active May 14, 2024 15:11
Semantic Commit Messages

Semantic Commit Messages

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

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

<scope> is optional

Example

@wojteklu
wojteklu / clean_code.md
Last active May 14, 2024 14:27
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.


General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules

@staltz
staltz / introrx.md
Last active May 14, 2024 03:08
The introduction to Reactive Programming you've been missing