Expertise
DevOps, full-stack development, cloud computing, industrial data modeling
About
Erliang / elonzh
Software engineer specializing in DevOps, full-stack development, and cloud computing. Currently leading industrial data modeling R&D.
I'm a software engineer with deep experience in DevOps, full-stack development, and cloud computing. I currently lead the industrial data modeling product R&D team, responsible for the full chain from architecture design to delivery.
Beyond engineering, I'm interested in the intersection of psychology and technology — understanding how users think and how teams collaborate often matters more than understanding the technology itself.
This site is my personal space for documenting technical decisions, project retrospectives, and ongoing thinking. Content grows continuously over time.
Current role
Industrial data modeling product R&D lead
Philosophy
Define structure and constraints first, then choose tools and implementation
Current focus
Build solid products, lead the team well, write down what I learn.
Technically focused on architecture stability and delivery efficiency. Managerially focused on team collaboration and decision quality. In writing, focused on reusable engineering practice.
Advancing architecture evolution and R&D process optimization for industrial data modeling products
Exploring DevOps and cloud computing best practices in industrial software contexts
Continuous writing to turn scattered experience into reusable methodology
Method
Good technical decisions come from understanding the problem, not chasing new tools.
Whether building products, designing architecture, or leading teams, I follow the same principles.
Understand the problem first
Before starting work, clarify constraints, boundaries, and goals. Most rework stems from insufficient upfront understanding.
Design for evolution
Good structure isn't static — it remains stable through change. Modularity, clear interfaces, and defined responsibility boundaries are key.
Manage complexity with engineering
Whether in code, documentation, or team collaboration, complexity must be managed. Automation, standardization, and continuous improvement are fundamental tools.