• 💼 Interested in working together? Reach out to me via email.
• 💬 Got a question or just curious about something? Feel free to ask!

• CCBuddy 🖥️: Native macOS menu bar app for monitoring Claude Code token usage and costs in real time. Supports Pro/Max and API modes with beautiful glass-effect UI, usage charts, and burn rate tracking. Built with SwiftUI, runs 100% locally. ✨

• Job Application Tracker 👨‍💻: Keep all your job applications organized in one place. Built with .NET 7, React, and Tailwind CSS. Track applications, schedule interviews, and never miss a follow-up! 📅

• Zephyr 📝: A clean and intuitive note-taking app for capturing ideas on the fly. Features colorful folders, smart tags, quick search, and bank-level encryption. Simple yet powerful! 🚀

• Seek Spider 🕷️: Python web crawler that scrapes job listings from Seek.com.au. Built with Scrapy and MySQL, smart enough to handle rate limiting. Just run and watch the jobs roll in! ☕

• Curriculum Rules Management System 🎓: Web app for managing university course rules with drag-and-drop interface and auto-generated PDFs. Built with Next.js and NestJS. Live at curriculum-app.fudong.dev 📚

Not many developers like to write documentation, but I do. I believe that a well-documented codebase is as important as the code itself. It’s like a story, telling what the code can do and how it works. I always try to write clear, concise, and useful documentation. My go-to documentation tool is Obsidian.md.

Whenever I write documentation, I try to keep the following steps in mind to ensure the reader gets the most out of it:

1. What is this documentation about?
2. Why is this documentation important?
3. How can the reader use this documentation?
4. When should the reader use this documentation?
5. Who is this documentation for?

I grew up with Windows and it holds a special place in my heart. but I currently use macOS as my primary development environment.