Tech
Technical work across web systems, cross-platform applications, automation tooling, interface implementation, and engineering delivery workflows. The emphasis is on architecture, usability, maintainability, and production-minded execution.
With Jensen Huang at HKUST — I am the person behind him.
Standing before him, I felt no divide — just two people in different chapters of the same story. He may be the most important man in the world, but my time bank holds more wealth than his.
Technical Focus
This section highlights the technical side of my work: system structure, implementation quality, automation capability, and cross-platform delivery. It is intended to show how I think about building products, not just listing repositories.
Web & Growth Tools
Static sites, landing pages, portfolio sites, internal tools, browser-side scripts, and web assets that support positioning, lead capture, and operations.
- HTML / CSS / JavaScript delivery
- GitHub Pages / Cloudflare Pages deployment
- SEO-ready structure and multilingual setup
Apps & Automation
Cross-platform application thinking across Flutter, Python desktop tooling, Windows automation, and workflow helpers for repetitive business tasks.
- Android / Windows / Web-oriented builds
- AutoApply series (v3->v5, Selenium->Playwright)
- UnifiedSearch multi-platform search aggregator
- feng-auto-fill browser form filler + Chrome extension
- cc-connect-docker remote compute via Docker
- 7zEvery / CopyEvery batch file tools
Data & Integration Work
I often connect APIs, reshape local files, automate repetitive steps, and build practical scripts that remove manual work from real operating processes.
- JSON / CSV / Excel processing
- HTTP API calls and glue-code integration
- Prompt-assisted content and workflow systems
- web-app-template full-stack TypeScript project template
- Personal CRM system (full-featured, pure frontend)
- Automated financial data scraping and analysis
Delivery Mindset
I do not treat software as isolated code. I think about user need, operating constraints, deployment path, maintainability, and how a tool fits the workflow around it.
- Product + operations perspective
- Debugging and iteration discipline
- Documentation and handoff awareness
Representative technical directions
This page is intentionally category-based, because some repositories are public, some are private, and some are better shown in context. The main technical lanes I can present or build around include:
- Portfolio or business websites with structured SEO, multilingual routing, and polished release metadata.
- Cross-platform tools spanning Flutter, Android, Windows utilities, and browser-side helpers.
- Automation scripts for file processing, repetitive office workflows, and operational efficiency.
- Data handling workflows that combine APIs, local files, prompt engineering, and reporting outputs.
My technical principles
- Use PDCA: plan first, build with checkpoints, verify the result, then iterate instead of shipping chaos.
- Open source first: if a suitable open-source project exists, I study it before reinventing anything.
- AI after research, not before thinking: if no open-source reference exists, I research structure first and then use AI as an execution accelerator.
- Structure before code: I care about architecture, decoupling, and not mixing everything into one messy block.
- Reuse aggressively: anything reusable should be extracted, shared, and kept maintainable across pages or modules.
- Function matters more than code style: code is not the final goal; correct functionality, adaptability, and usability matter more.
- Modern UI still matters: I value responsive layouts, portrait and landscape adaptability, rounded corners, clean shadows, and polished contemporary interfaces.
How I usually work on software projects
- Clarify the real problem: what must be solved, who uses it, and what counts as done.
- Choose the practical stack: simplest toolchain that matches deployment and maintenance needs.
- Build in layers: structure first, workflow second, polish after the system proves useful.
- Ship with context: docs, naming, navigation, and release details should support real use, not just code completion.
Repository review & collaboration
If you want a repository walkthrough, architecture explanation, or a hiring-focused technical selection, I can present the most relevant code samples by context: growth tooling, internal software, automation utilities, or multi-platform builds.