📝 Developer Journal

Welcome to my developer journal!
This repo is my dedicated space to track daily progress, reflect weekly, and build long-term growth as a software engineer.

---

📂 Folder Structure

engineering-diary/
│
├── logs/        # Daily logs (one file per coding day)
│   └── YYYY-MM-DD.md
│
├── reviews/     # Weekly reviews (every Sunday)
│   └── week-XX.md
│
├── projects/    # Project plans & progress trackers
│   └── project-name.md
│
└── README.md    # This guide

---

📅 Daily Logs (logs/)

Purpose: Capture what you did, what you learned, and what blocked you — so progress is always visible.

• File format: logs/YYYY-MM-DD.md
• When to write: Every day I code (minimum 5 minutes)
• Template Sections:
  • 🌅 Morning Plan & Priorities → today’s main goals
  • 🔋 Energy & Mood → track consistency & habits
  • 🛠️ What I Built Today → code, experiments, or milestones
  • 📚 Learnings → key takeaways, with resources if possible
  • 🐛 Bugs / Blockers → issues and plan to fix
  • 📝 General Notes/Day Summary → General notes throughout the day or a space to summarise how the day went
  • 🔮 Next Steps / Tomorrow → checklist for the next session

✅ Aim: Show consistent daily growth and spot patterns in learning.

---

🌅 Morning Plan & Priorities

This section helps me set clear intentions every day before I start coding.
I don’t need to fill every category daily — just the ones relevant to that session.

• 🔴 HIGH PRIORITY:
  The most important task of the day. If I only accomplish one thing, it should be this.
• 📘 LEARNING:
  Topics, tutorials, or concepts I’m actively studying.
• 🤝 MENTORSHIP:
  Any mentoring sessions, study groups, or discussions with peers.
• 💻 PROJECT:
  Progress on current projects or building new features.
• 🚀 DEPLOYMENT:
  Anything related to shipping code, testing, or setting up environments.
• 📖 READING:
  Articles, books, or docs I want to get through today.
• 🌀 STRETCH:
  Bonus tasks — nice to do if I have extra time and energy.

✅ Pro Tip: Keep HIGH PRIORITY to one task only.
It prevents overwhelm and ensures consistent daily wins.

---

📆 Weekly Reviews (reviews/)

Purpose: Step back to reflect on the big picture, celebrate wins, and adjust course.

• File format: reviews/week-XX.md
• When to write: Every Sunday night
• Template Sections:
  • ✅ Wins → things I’m proud of this week
  • 😅 Struggles → what challenged me
  • 📘 Learnings → key lessons or breakthroughs
  • 🍒 Next Week Goals → 3–4 actionable items

✅ Aim: Turn small daily logs into a clear weekly growth story.

---

💻 Project Plans (projects/)

Purpose: Track each project’s scope, progress, and lessons learned.

• File format: projects/project-name.md
• When to write/update: Whenever I start or make progress on a project
• Template Sections:
  • 🎯 Goal → why I’m building this project
  • 🧩 Features Roadmap → checklist of features
  • 📅 Timeline → milestones & deadlines
  • 🛠️ Tech Stack → tools & frameworks used
  • 📚 Lessons Learned → new insights from building
  • 📝 Notes → anything worth recording

✅ Aim: Build a portfolio of thoughtful, documented projects.

---

🔁 Habit Rules

• 🕒 Daily: Write a log after each coding session (no skipping, even if short).
• 📆 Weekly: Reflect every Sunday night before bed.
• 💡 Projects: Update files as soon as new progress is made — don’t wait until the end.

💬 “The best way to learn is to build, reflect, and repeat.”

---

🌟 Why This Matters

• Keeps me accountable and consistent
• Builds a ready-made knowledge base for future reference
• Helps me prepare for interviews with real examples of growth
• Shows a visible timeline of my journey to becoming a professional web developer