Current

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

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
Why GitHub flow
Our reasons for using the GitHub flow as our branching and development strategy.
Feb 15, 2024
Why Poetry
Our reasons for using Poetry for managing Python package dependencies when building Django and Python projects.
Jan 29, 2024
Why poly-repo
Our reasons for structuring projects (both software and websites) in a poly-repo rather than mono-repo style.
Dec 5, 2023
Why Ruff
Enforcing style of code with automatic linters and formatters is important for code reviews to focus on content, not style. This post covers the reasons why we decided on…
Nov 27, 2023
Why GitHub Projects
As a project grows, it becomes both more important and more difficult to keep track of where the project is at. This can be helped by using visualisation and project…
Nov 23, 2023
Why standardized snippets
The larger a project is, the more important it becomes to have a joint set of standards when writing documentation. We decided to set up shortcuts that are shared across…
Nov 23, 2023
Why Discord
Our reasons for using Discord as our communication platform.
Jun 25, 2023
Why Quarto
Our reasons for using Quarto to build the website and write the general documentation.
Jun 25, 2023
Why an MIT License
Open and permissive licensing of copyrighted content is a way to increase use of a software product, ease collaboration and re-use, and share intellectual ideas with others.…
Apr 1, 2023
Why Python
Python is one of the most common and widely used programming languages. As it is used across multiple domains and industries, it is likely to be familiar to a wider…
Mar 22, 2023
No matching items