Hey! This is 🌠Stardust here. I'm pursuing my Ph.D. in Electrical Engineering at the University of Toronto.
I graduated from the Dual Degree Program at HKUST, majoring in Computer Science and General Business Management (plus a 3rd major in Electronic Engineering).
I usually spend my own time enjoying 💕anime, 🎮video games, 😋food and ☕coffee (not Java).
I am currently interested in stochastic and risk-aware control. I've also been exposed to the following areas:
- Event-Triggered Mechanism
- Phase Theory
| Area | Language | Tech Stack |
|---|---|---|
| Software Engineering / OOP |   |
 + JavaFX (GUI) + SLF4J + Logback + JaCoCo  (and my teammates. They exemplified what it meant to be excellent programmers to me, who was still a beginner back then. Check out their great work here.) |
| Formal Verification | Viper$^{(1)}$ + Alloy$^{(2)}$ |
Apron (Java numerical analysis) + Soot (Java pointer analysis) |
| Functional Programming |  |
|
| Blockchain / DeFi / Smart Contract / Web3 |   |
Blockchains:   + Polygon + Avalanche + Arbitrum Integrated Projects:  + Uniswap (and its forks) + Aave + Venus + Alpaca + Rabbit Libraries / Tools: OpenZeppelin + Hardhat + Ethers.js + Remix + Metamask |
| Backend / Scripting / Testing |  |
   , etc. |
| AI / ML / Data Science |  |
       , etc. |
| Database / Data Engineering | SQL,  |
 |
| Systems Programming / Networks |  |
|
| Documentation / Typesetting / UML |   |
  + PlantUML |
| DevOps |  + YAML |
Version Control:    Build Tools:   Package Manager:   + poetry Container Platform:  |
(1): Verification Infrastructure for Permission-based Reasoning. It is a C-like language for formal verification.
(2): A declarative specification language for model checking. It is based on first-order logic.
| Area | Language | Tech Stack |
|---|---|---|
| Signals / Control |  |
Simulink |
| Robotics / Embedded System |  |
 |
| Web / UI |   (*) (**) |
    |
| Mobile | |
 |
I'll always try my best to open-source my code if possible. Here are a few heuristics:
- Code for courses is "public" (possibly "archive") if:
- all collaborators give consent; AND
- its submission deadline has passed if it is a project; AND
- open-sourcing is NOT explicity forbidden by the instructor; AND
- it is NOT reused as graded work across semesters (let's be fair and don't give spoilers)
- Proprietary code is never forked or made "public". However, I'm happy to discuss implementation details as long as I'm allowed to do so.
Last edited on: 16/10/2024