Current

These decision posts reflect the decisions we currently adhere to. All our decisions adhere to our values and principles.

Why Copier

Configuration drift is a major problem when managing multiple repositories. This post describes why we chose Copier as our tool for managing configurations in existing…

Aug 5, 2025
Why CC0 for data

Given that we work with and manage data, having a license for the data can be helpful. This post discusses why we recommend (and use) the CC0 license for data.

Aug 1, 2025
Why Parquet

The format of the file for storing data directly impacts how it is used later. Parquet is a format that has very good compressed file sizes, is very fast to process and…

Mar 10, 2025
Why Markdown

This post describes our reasons for using the markup language Markdown for documentation.

Feb 28, 2025
Why Polars

The key to useful and meaningful data is data that is good quality and tidy. Getting data to be tidy and higher quality is an often undervalued and underestimated activity…

Dec 4, 2024
Why Commitizen for changelog generation

Our reasons for using Commitizen to auto-generate changelogs.

Nov 22, 2024
Why Pandera

A key functionality of Sprout is checking whether user-supplied data match the metadata that describe them. This post explains why we chose to use pandera for automating…

Nov 8, 2024
Why Commitizen for semantic release

The reasons we use Commitizen for automated versioning and releasing of our software.

Nov 8, 2024
Why jsonschema

As we follow the Data Package standard for structuring metadata, we have to make sure that our metadata files conform to this standard. This post explains why we chose…

Nov 7, 2024
Why FigJam for retrospectives

Our reasons for using FigJam for our retrospectives.

Oct 25, 2024
Why lint with commitizen

Reasons to use commitizen to lint our commit messages to follow the Conventional Commits standard.

Oct 25, 2024
Why quartodocs

Our reasons for using quartodocs to build Python function and class documentation from docstrings into a website.

Oct 24, 2024
Why Pytest

Testing software is a requirement for ensuring it works as intended and because we use a test-driven development workflow. This post explains why we choose to use pytest…

Jul 17, 2024
Why Frictionless Data

Why we choose to use the Frictionless Data standard for structuring metadata and data.

Jul 15, 2024
Conventional branches

Our reasons for using conventional branch names.

Jun 8, 2024
Why choose Semantic Versioning (SemVer) for software

Our reasons for using SemVer for versioning the releases of our software projects.

May 24, 2024
Why atomic commits

Our reasons for using atomic commits in our projects instead of squashing commits and …? rebase?

May 14, 2024
Why conventional commits (with optional emojis)

Our reasons for using conventional commits (with optional emojis following the Gitmoji convention) across Seedcase repositories.

May 14, 2024
No matching items