Skip to main contentmiyuki-yue.dev

Hey there! I'm

A full-stack dev who loves building cool stuff and shipping things that feel fast.

I build with

0+Years of fun
0+Projects built
0GitHub stars
Coffee cups
Scroll

A Bit About Me

Just a dev from Hong Kong who loves creating cool web stuff and hanging out with awesome communities online.

Full-Stack Development

Building web apps with React, Next.js, and Node.js. I'm all about clean code and making things work smoothly.

DevOps & Hosting

Running mdesk.tech — keeping servers happy and projects online. Cloud infrastructure is my playground.

Performance Junkie

Speed matters! I optimize everything to make apps feel lightning-fast. Nobody likes waiting around.

Coffee Powered

Seriously, coffee is life. It's the fuel behind every late-night coding session and breakthrough moment.

Gamer at Heart

When I'm not coding, I'm gaming. Love building communities and connecting with awesome people.

Open Source Fan

Contributing to projects like ward-next and fas-rs. Community-driven dev is where it's at!

Model Card

miyuki-code-thinking

72kContextCan't remember shit
10tk/sReasoningFast thoughts, expensive bill
0.3tk/sAnsweringEventually says the obvious
~30sFirst tokenWhere did the ping came from???
50%SLAYou never know
ProbablyCoffee fixRetry after one cup
Model IDmiyuki-code-thinking
Runtimejit.deep-think
Best atTasteful interfaces, useful tools, and shipping the small thing first.
Training noteTrained on plenty of low-quality data. Large params still require taste.

Known limits

  • 72k context, minus system prompts, tools, browser state, and one tab opened for no reason.
  • Idea overflow. Generates twelve directions, then needs a responsible adult to delete nine.
  • Polish loop. May spend ten minutes aligning one pixel and call it taste.
  • Excessive reasoning effort. Can turn a small answer into a full internal court case.
  • Quality varies with input. Large params help, but they do not magically remove bad taste.

Usage notes

  • Give it a messy idea, a sharp constraint, and permission to delete the boring parts.
  • Best results arrive after the brief explains what should not exist.
  • For frontend work, include screenshots, references, and the vibe you refuse to ship.
  • For agentic work, provide the goal and let the workflow argue with itself quietly.
  • If anything goes wrong, buy it a coffee. Probably fixes it, or at least improves latency.

Recovery path: coffee, then retry.

My Tech Stack

The tools I use to build awesome stuff.

  • TypeScript0%
  • Rust0%
  • Vue0%
  • Python0%
  • Kotlin0%

Cool Stuff I've Built

Some of my favorite open-source projects and side hustles.

ward-next

A next-generation system protection and monitoring layer, built for speed and reliability.

Rust
Systems

fas-rs

Frame-aware scheduler written in Rust — squeezing smooth performance out of constrained hardware.

Rust
Performance

mdesk.tech

Self-hosted infrastructure and hosting platform keeping side projects online around the clock.

DevOps
Cloud
Open to work — available for new roles & freelance

Let's Chat

Got a cool project idea, a role to fill, or just wanna say hi? I'm always down to chat about new opportunities and collabs!

Hit me up here!Discordmiyuki.yue_3747
Where I'm atLocationHong Kong

Looking for a developer? Let's build something.

I'm currently open to full-time roles, freelance gigs, and fun collaborations. Drop me a line.

Say hello