Skip to content

Home

Jump to bottom
givecoffee edited this page Jun 14, 2026 · 34 revisions

FirstFrost MVP

GitHub Pages website:

Week-by-week tracking of issues, pull requests, branches, and notes for the MVP of garden-tracking app FirstFrost hosted at givecoffee/firstfrostmvp.

For expanded week-by-week journey updates, see the included Devlog page for each section.

Topics

  • Focus - the main thing the week was about, in one line
  • Devlog link - goes to an expanded, more comprehensive breakdown of that week's phase in development
  • GitHub Issues - every issue opened or worked on that week
  • Pull Requests - every PR opened, merged, or reviewed
  • Branches - branches created for the week's work
  • Notes - anything worth remembering (decisions made, things that broke, what carried over to the next week)
  • Devlog link - goes to an expanded, more comprehensive breakdown of that week's phase in development
  • Demos - Walkthroughs of changes and demonstrations of features

Links go to GitHub directly. If a link 404s, the branch was probably deleted after merge.

Week 1 - Breaking Ground

Focus: Stand up the Postgres instance on Supabase and confirm the local dev environment matches the assignment requirements. What FirstFrost is and why it's being built. Setting up the repo, the project brief, and the DEVLOG before a single line of SQL gets written.

Week 1 Devlog: https://github.com/givecoffee/firstfrostmvp/wiki/Week-01-%E2%80%90-Devlog

GitHub Issues

Pull Requests

Branches

Notes

  • Provisioned the Supabase Postgres instance and confirmed connection from local tooling.
  • Locked in version check workflow so later weeks don't drift on Postgres or psql versions.

Time Spent: 2 Hours

Week 2 - First Seeds

Focus: Defining the shape of the data - ENUMs, tables, constraints, and the decisions behind them. The schema is the foundation everything else depends on.

Week 2 Devlog: https://github.com/givecoffee/firstfrostmvp/wiki/Week-02-%E2%80%90-Devlog

GitHub Issues

Pull Requests

Branches

Notes

  • TRUNCATE cleared the data, DROP removed the table entirely.
  • The error code 42P01 is PostgreSQL saying there is a missing relation.

Time Spent: 3 hours

Week 3 - Taking Root

Focus: Foreign keys, triggers, and the logic that lives in the database instead of the app. This is where the system starts enforcing rules on its own.

Week 3 Devlog: https://github.com/givecoffee/firstfrostmvp/wiki/Week-03-%E2%80%90-Devlog

GitHub Issues

Pull Requests

Branches

Notes

  • All six verified in information_schema.triggers, four updated_at triggers, one on_auth_user_created, and one set_task_completed_at

Time Spent: 2 hours

Week 4 - Building the Fence

Focus: Row-level security - the most important work in the project. Every user owns their own rows, and the database enforces it, not the client.

Week 4 Devlog:

GitHub Issues

Pull Requests

Branches

Notes

  • RLS enabled on all five tables with 15 policies.
  • rowsecurity = true confirms the policies are enforced on every request.

Time Spent: 2 hours

Week 5 - Thinning the Rows

Focus: Indexes and query planning. Making sure the database finds data efficiently instead of scanning everything every time.

Week 5 Devlog:

GitHub Issues

Pull Requests

Branches

Notes

Time Spent:

Week 6 - Reading the Weather

Focus: JSONB and flexible metadata - how to store information that doesn't fit neatly into fixed columns, and why that matters for future integrations.

Week 6 Devlog:

GitHub Issues

Pull Requests

Branches

Notes

Time Spent:

Week 7 - Cross-Pollination

Focus: JOINs and filtering - writing queries that pull related data across tables and return exactly what's needed, nothing more.

Week 7 Devlog:

GitHub Issues

Pull Requests

Branches

Notes

Time Spent:

Week 8 - First Harvest

Focus: Building the Postman suite and testing every endpoint. This is where the schema gets proven, not assumed.

Week 8 Devlog:

GitHub Issues

Pull Requests

Branches

Notes

Time Spent:

Week 9 - Checking the Fences

Focus: Adversarial RLS verification and aggregation queries. Trying to break the security controls with a second account, then confirming they held.

Week 9 Devlog:

GitHub Issues

Pull Requests

Branches

Notes

Time Spent:

Week 10 - Reflection

Focus: Looking back at the full "season" or developmental cycle - what worked, what surprised, and what this project is worth explaining to someone hiring.

Week 10 Devlog:

GitHub Issues

Pull Requests

Branches

Notes

Time Spent:

Conventions

Issue titles follow the format used in Week 1: a verb-led description that maps cleanly onto a branch name. Example: Provision Supabase PostgreSQL instance → branch 1-provision-supabase-postgresql-instance.

Branch naming uses one of two patterns depending on the work:

  • <issue-number>-<short-description> for issue-driven work (e.g., 1-provision-supabase-postgresql-instance)
  • <type>/<week>-<short-description> for setup or recurring work (e.g., setup/week1-version-check, feature/jsonb-movie-details)

Pull requests reference the issue they close with Closes #N in the description so the issue auto-closes on merge.

Wiki updates happen at the end of each week as part of the dev update. If a week's section is still showing placeholder text, that week hasn't been wrapped up yet.

Clone this wiki locally