This is my Personal User Manual — a short guide to how I work, learn, and collaborate.
It’s not a CV, not a manifesto, and definitely not a finished product.
Think of it as documentation for a system that’s still evolving.
I’m learning web development because it sits at a crossroads I care about:
- logic and creativity
- structure and expression
- people and technology
Websites can be simple tools, or they can become meaningful spaces for sharing ideas and connecting people.
That’s the direction I’m exploring.
- I like clear problem statements and concrete examples
- I learn fastest by building small things end-to-end
- I prefer steady progress over rushed results
- Writing things down (READMEs, notes, comments) helps me think
If something feels vague, I’ll probably ask questions — that’s a feature, not a bug 🙂
- JavaScript, HTML, CSS (actively improving)
- GitHub as a learning log and workspace
- Basic Docker usage for local development
- Curiosity-driven experiments (sometimes messy, usually educational)
My repositories show thinking in progress, not just polished outcomes.
- Time estimation is still stabilizing on new tasks
- I process feedback best when it’s specific and actionable
- I sometimes explore too many options before narrowing down
I treat these as signals to improve, not as fixed traits.
- I reduce scope and restate the problem
- I ask for clarification instead of guessing
- I document what broke and why
- I iterate
Most issues become manageable once they’re explicit.
- Stronger foundations in web development
- Building small, useful, human-centered websites
- Learning to collaborate better through feedback and shared work
- Exploring how AI tools will reshape how we build and experience the web
No shortcuts — just steady iteration.
If you:
- enjoy learning by building
- value clarity over hype
- don’t mind systems in beta
…we’ll probably get along.
Feel free to reach out or explore the code.