DEV Community

Daniil Kornilov
Daniil Kornilov

Posted on Edited on

Five linked database structures for project and work records

Disclosure: This article was created or edited with AI assistance. Revised on 13 October 2026 to remove promotional links and unsupported outcome claims. It is educational guidance, not a verified personal case study or a measured result. Examples are illustrative; use only your own documented experience and measurements.

The sections below present options and illustrative examples. Adapt them to the requirements of your project or role; they do not establish a universal rule or promise a result.

System 1: Project Tracker

The structure:

Property Type Why
Name Title Obviously
Status Select Not Started / In Progress / Review / Done / Archived
Priority Select P0 (urgent) / P1 (this week) / P2 (this month) / P3 (someday)
Type Select iOS App / Web / Freelance / Side Project
Deadline Date When it's due
GitHub URL Link to repo
Tasks Relation Links to task sub-database

System 2: Bug Tracker

The structure:

System 3: Interview Prep

The structure:

Three linked databases:

Company Database:

  • Company name
  • Position
  • Interview stages (phone screen, technical, system design, behavioral)
  • Salary range
  • Notes from each round
  • Status: Researching / Applied / Interview / Offer / Rejected

STAR Stories:

  • 10 prepared stories using Situation/Task/Action/Result format
  • Tagged by theme: leadership, conflict, failure, achievement, teamwork

System 4: Content Calendar

The structure:

Property Type Why
Title Title Content piece name
Platform Multi-select Dev.to / Telegram / Twitter / Threads
Status Select Idea / Draft / Ready / Published
Publish Date Date Scheduled date
Topic Select iOS / Career / Productivity / Tools
Link URL Published URL
Performance Number Views/likes after 7 days

The workflow:

System 5: Finance OS

The structure:

Three views of one database:

Income Tracker:

  • Source (Freelance / Boosty / App Sales / Salary)
  • Amount
  • Date received
  • Status (Invoiced / Paid / Overdue)
  • Client name

Expense Tracker:

  • Category (Tools / Hosting / Education / Hardware / Living)
  • Amount
  • Date
  • Recurring? (Yes/No)
  • Notes

Monthly Summary:

  • Total income
  • Total expenses
  • Net profit
  • Savings rate

How These Systems Connect

The real power is in the relations between databases.

That's not productivity for productivity's sake. That's a system that gives me real answers to real questions.

Start with one maintained record

Tools don't make you productive. Systems do.

You can use the fanciest project management app in the world. If you don't have a habit of updating it, it's useless. A text file you actually maintain beats a Notion database you ignore.

Start with one system. The one that solves your biggest pain point. For me, it was the finance tracker (because losing money hurts). For you, it might be the project tracker or the interview prep system.

Build it. Use it for a week. Adjust. Repeat.

That's the goal.

Top comments (1)

Collapse
 
harsh2644 profile image
Harsh •

19 and already running your entire dev life on Notion? That's impressive 🔥 I'm 19 too and just starting to build my own systems. The part about forgetting a $200 invoice hit hard — learned that lesson myself. Would love to know how you structure your project tracker specifically. Any templates you'd recommend for beginners?"

Some comments may only be visible to logged-in visitors. Sign in to view all comments.