Back to articles
6 min

How I Collect and Manage 100+ Development Resources

My complete workflow for collecting, organizing, reviewing, and maintaining a useful personal resource library.

ProductivityToolsResource Management

How I Collect and Manage 100+ Development Resources

The problem

Developers encounter useful tools, articles, and tutorials every day. Over time, browser bookmarks become messy and Notion pages multiply, yet the right item is still difficult to find when it is actually needed.

The problems I wanted to solve:

  • I saved too much and rarely returned to it
  • Search was slow when I needed something
  • Categories were inconsistent
  • Dead links accumulated without maintenance

My system

1. Build a category structure

I organize resources into six broad groups:

Tools
├── Development (GitHub, VS Code...)
├── Design (Figma, Sketch...)
├── Productivity (Notion, Raycast...)
└── Deployment (Vercel, Railway...)

Communities
├── Technical communities (V2EX, Stack Overflow...)
├── Indie communities (Indie Hackers...)
└── Social platforms (Twitter, LinkedIn...)

Learning
├── Documentation and technical blogs
├── Video tutorials
└── Online courses

Products
├── Product discovery
├── Product rankings
└── Case studies

Inspiration
├── Interface inspiration
├── Creative references
└── Interaction examples

Content
├── Technical weeklies
├── Email newsletters
└── News aggregators

2. Use a consistent collection flow

Browser extension

Discover → Save → Extract metadata → Add tags

Website submission form

{
  name: "Resource name",
  url: "https://...",
  category: "Tools",
  tags: ["Development", "Productivity"],
  description: "Why this resource is useful",
  priority: "High / Medium / Low"
}

3. Keep structured data

Each resource uses the same fields:

{
  "id": "res-001",
  "name": "Resource name",
  "url": "https://...",
  "category": "tools",
  "tags": ["development", "productivity"],
  "summary": "A short description",
  "priority": 1,
  "status": "published",
  "createdAt": "2024-11-01",
  "lastVisited": "2024-11-05",
  "notes": "Personal notes"
}

4. Maintain it regularly

Weekly checklist:

  • [ ] Review 10–20 newly saved resources
  • [ ] Improve categories and tags
  • [ ] Test ten random links
  • [ ] Remove resources I no longer use

Monthly review:

  • [ ] Find the most frequently used resources
  • [ ] Adjust category priorities
  • [ ] Add missing categories
  • [ ] Share a short monthly selection

Recommended tools

Collection

  • Raindrop.io — cross-platform bookmark management
  • Notion — flexible notes and databases
  • Pocket — a simple read-later queue

Organization

  • Airtable — structured database management
  • Notion Database — flexible views and properties
  • A custom system — the most control, which is the direction of this website

Sharing

  • A personal website — full ownership and long-term control
  • GitHub Gist — fast, simple technical sharing
  • A newsletter — a useful format for regular selections

Results after three months

| Metric | Before | After | |---|---|---| | Saved items | 500+ unorganized | 150 selected resources | | Time to find something | 5–10 minutes | Under one minute | | Usage | Almost never | 5–10 times per day | | Sharing | Never | Weekly recommendations |

Core principles

  1. Less is more — save fewer things, but make each one useful
  2. Review regularly — schedule weekly and monthly maintenance
  3. Keep updating — remove outdated items and add better replacements
  4. Share actively — explaining a resource is one of the best ways to remember it

Next steps

I plan to build a browser extension for one-click collection, add a contribution workflow, and publish a curated monthly resource list.

The goal is not to own the largest bookmark collection. It is to maintain a small system that I can trust and actually use.