A cartoon illustration of a person with their arms outstretched looking uncertain, with a green arrow and black arrow pointing in opposite directions, symbolising a choice or decision.

Archive of Decision Records

Decision records inspired by Architectural Decision Records.

Illustration by Storyset

We write structured decision records (or “posts”) describing the reasons for why we choose certain tools, technologies, or processes for our software, our collaboration workflow, and our websites. All our decisions adhere to our Values and principles.

Conventional branches
Our reasons for using conventional branch names.
Jun 8, 2024
Why Discord
Our reasons for using Discord as our communication platform.
Jun 25, 2023
Why Django
Web frameworks are designed to support building both web front ends and API layers. Django is a popular full-stack framework with solutions for most web development tasks…
Mar 22, 2023
Why Fly.io

Showcasing a demo of Seedcase software helps make things more tangible. This post describes our reasons for using Fly.io as a deployment host for showcasing our demo.

Dec 8, 2023
Why Frictionless Data
Why we choose to use the Frictionless Data standard for structuring metadata and data.
Jul 15, 2024
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 GitHub flow
Our reasons for using the GitHub flow as our branching and development strategy.
Feb 15, 2024
Why Material Design
We aim to utilise existing CSS or UI frameworks instead of building from scratch so Seedcase software products will look good with minimal effort. Since Material Design…
Dec 15, 2023
Why Poetry
Our reasons for using Poetry for managing Python package dependencies when building Django and Python projects.
Jan 29, 2024
Why Postgres
SQL is the backbone of any database system. However there are many variants of SQL. This decision post contains the reasons for using PostgreSQL, which is a powerful and…
Jan 5, 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 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
Why Quarto
Our reasons for using Quarto to build the website and write the general documentation.
Jun 25, 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 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 sharing intellectual ideas with…
Apr 1, 2023
Why atomic commits
Our reasons for using atomic commits in our projects instead of squashing commits and …? rebase?
May 14, 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 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 lint with commitizen
Reasons to use commitizen to lint our commit messages to follow the Conventional Commits standard.
Oct 25, 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 quartodocs
Our reasons for using quartodocs to build Python function and class documentation from docstrings into a website.
Oct 24, 2024
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
No matching items