FAQ

Frequently asked questions about this site, my technical focus and practice.

What is this website for?

This is my personal technical blog and open experiment station. I document content related to backend development, platform R&D, AI engineering implementation, real-time voice pipelines, automation tools, and long-term technical practice.

What are your main technical focus areas?

I mainly focus on the following areas:

  • Java backend development and microservices architecture
  • Spring Boot / Spring Cloud Alibaba
  • Kubernetes deployment and stability optimization
  • LLM application engineering and model implementation
  • ASR / TTS / Digital Human voice pipelines
  • Automation tools and personal productivity systems
Do you focus more on Java backend or AI engineering?

I have both, but my strength is combining the two. One side is backend and platform R&D capabilities, the other is AI system integration, serviceability, implementation, and pipeline integration capabilities. What I care more about is how to make technology into a runnable, maintainable, and deliverable system.

Who is this blog for?

Suitable for:

  • Java backend developers
  • People working on microservices and platform R&D
  • Engineers transitioning from traditional development to AI Engineering
  • People interested in ASR / TTS / real-time voice pipelines
  • People who want to build personal technical brand websites and long-term content accumulation
Is your content more theoretical or practical?

More practical. I usually write around real projects, specific problems, engineering tradeoffs and implementation processes, rather than just staying at concept introductions.

Why do you focus on AI engineering?

Because I care not just about the model itself, but how the model integrates into real systems. From interface encapsulation, service governance, pipeline design, to latency, stability, deployment and scaling, AI implementation encounters many engineering problems worth long-term research and documentation.

Why do you write about real-time voice pipelines?

Real-time voice systems are a very typical set of engineering problems. It involves audio processing, network transmission, model inference, system architecture and user experience simultaneously. It's not just about "can the model run", but "can the entire pipeline be stable, low-latency, and available".

What types of articles will you write on this site?

Currently mainly includes:

  • Backend development and system design
  • Microservices and Kubernetes
  • AI engineering and model implementation
  • ASR / TTS / Digital Human / Real-time voice systems
  • Automation tools and personal projects
  • Technical growth, writing and long-term practice thinking
What types of projects have you worked on?

Projects and practice I have done usually focus on:

  • Backend business systems
  • Platform R&D and infrastructure building
  • AI integration and engineering implementation
  • Digital Human / Voice interaction pipelines
  • Automation tools and personal experiment projects
Is the focus of this site to showcase resume or accumulate content?

More biased towards long-term content accumulation. Resume and project showcase are only part of the site, but the core value is continuously outputting articles, experiences, experiments and problem-solving processes, making this site a sustainable personal brand asset.

Why do you use "Lab" (实验室) expression on this site?

Because this website is not just a simple portfolio page. It's more like a continuously evolving personal experiment field: building projects while writing articles, while verifying my thoughts and directions.

If I'm visiting this site for the first time, where should I start?

Recommended to start with:

  • About page - learn who I am and what I focus on
  • Blog page - quickly determine if content direction matches
  • Projects page - see what I've built
  • FAQ page - quickly build overall understanding
Will you keep updating?

Yes. This website is a long-term project. I will continuously add articles, projects, experiments and structural optimizations, gradually growing from a personal showcase page to a more complete technical brand site.