# 🧠 Contributing to the 300+ Advanced List

Thanks for pitching in. 🤝 This is the **Professionals & Senior Engineers** list, and its whole value is the signal-to-noise ratio. Every entry here should be something you'd actually reach for in production - or defend in a design review.

So the bar is high on purpose. Here's how to clear it.

---

## 🎯 What belongs here

Production-grade, battle-tested, or genuinely category-defining repositories in:

- 🏛️ System design & distributed systems
- 🗄️ Databases, storage engines, data & streaming
- ⚡ LLM serving, agents, RAG, fine-tuning, evals & MLOps
- ☸️ Kubernetes, cloud-native, IaC & platform engineering
- 🔭 Observability & SRE
- 🛡️ AppSec, offensive/defensive security & supply-chain
- 🦀 Systems languages, runtimes & performance tooling

**Not here** (they have better homes): beginner tutorials → [150 Essentials](../awesome-learn-to-code/README.md); broad all-round picks → [280+ Comprehensive](../README.md).

> **The test:** would a staff engineer nod at this in an architecture discussion? If yes, it fits. If it's a "getting started" tutorial, it doesn't.

---

## ✅ Quality bar (non-negotiable)

- [ ] **Real, canonical repo** - correct `owner/repo` slug, verified (repos get renamed; check before you link)
- [ ] **Actively maintained** _or_ an accepted industry reference (dormant-but-canonical is fine; abandoned-and-obscure is not)
- [ ] **Advanced/professional** - not a beginner resource
- [ ] **No duplicates** - search the README first
- [ ] **Right section** - the most specific one that fits

New tools are welcome (this list tracks 2026 breakouts too) - just make sure they've earned real adoption, not just a launch-day spike.

---

## ✍️ Formatting (match exactly)

```markdown
- [Display Name](https://github.com/owner/repo) - One precise sentence: what it is and why pros value it.
```

Be specific and technical. "Fast" is weak; "PagedAttention serving engine with ~24x throughput over naive HF" is signal. End with a period.

---

## 🚀 Pull request process

1. **Fork** and branch from `main`.
2. **Add** your entry to `awesome-senior-engineer-resources/README.md` in the correct section.
3. **Verify** the link resolves (a quick `curl -I` never hurts).
4. **Commit** clearly, e.g. `Add: Pingora to Networking, Proxies & Service Mesh`.
5. **Open a PR** with a one-line rationale - bonus points for a benchmark, adoption stat, or "we run this in prod" note.

---

## 🛡️ Code of Conduct

Direct, technical, and respectful. Debate the tool, not the person. We keep this a professional space where strong opinions are welcome and cheap shots aren't.

---

Sharp additions keep this list worth bookmarking. Thanks for keeping the signal high. ⭐

- _Curated by [md8-habibullah](https://github.com/md8-habibullah)_