portfolio/README.md

90 lines
1.6 KiB
Markdown
Raw Normal View History

### 1. Home / Landing
2025-10-17 20:22:21 +02:00
**Goal:** instant context
2025-10-17 20:22:21 +02:00
* Name + role
*“Software Developer focused on X”*
* 1-line value statement
*“I build reliable backend systems and clean UIs.”*
* Primary CTA: **View Projects** or **GitHub**
2025-10-17 20:22:21 +02:00
---
2025-10-17 20:22:21 +02:00
### 2. Projects (most important page)
2025-10-17 20:22:21 +02:00
**This is where hiring decisions start.**
2025-10-17 20:22:21 +02:00
For each project:
2025-10-17 20:22:21 +02:00
* **What it is** (1 sentence)
* **Tech stack**
* **Your role** (solo / team / size)
* **Key challenges & decisions**
* **What you’d improve next**
2025-10-17 20:22:21 +02:00
Examples:
2025-10-17 20:22:21 +02:00
* “Self-hosted document management system (Docker, Python, PostgreSQL)”
* “Matrix server setup & federation experiments”
* “WPF app solving UI threading issues”
2025-10-17 20:22:21 +02:00
👉 3–5 *good* projects beat 10 shallow ones.
2025-10-17 20:22:21 +02:00
---
2025-10-17 20:22:21 +02:00
### 3. About (technical, not fluffy)
2025-10-17 20:22:21 +02:00
Think “senior dev intro”, not life story.
Include:
* What kind of problems you enjoy solving
* How you approach learning & debugging
* What environments you work best in
Keep it to ~2 short paragraphs.
---
### 4. Skills / Tech Stack
**Grouped, not buzzword soup.**
Example:
* **Languages:** …
* **Frameworks:** …
* **Infrastructure / DevOps:** Docker, Linux, CI/CD
* **Databases:** …
* **Concepts:** REST, async, threading, security basics
Bonus points:
* “Comfortable with” vs “Familiar with”
---
### 5. Experience
* Jobs, freelance, serious hobby projects
* Focus on **impact**, not duties
Example:
> “Maintained and extended internal tooling used by X users”
---
### 6. Resume (PDF)
* One click download
* Matches the portfolio (no contradictions)
---
### 7. Contact
* Email
* GitHub
* LinkedIn
* (Optional) location / timezone