Civil engineering background, 13-year software veteran. From full-stack engineer to leading a 60+ person R&D team. The reverence for life that bridge cracks taught me carries into every line of code and every management system.
Born in 1992, civil engineering major, worked in the construction industry after graduation. Bridge cracks mean lives at stake — that reverence for consequences carried into software. Most software engineers reference only the software industry when discussing "engineering management." Civil engineering's standardization, supervision systems, change management, and cost control offer a completely different perspective.
Switched to coding in 2014 — Android, iOS, backend, web, all of it. Led my first project in 2017 and experienced project collapse and team chaos. Took over the entire R&D department in 2019, growing from 0 to 60+ people, and became VP of Engineering in 2025. Every pitfall I fell into eventually became judgment.
Nearly eight years in management, still coding at high frequency. Built microservice architectures, delivered YOLO image recognition end-to-end. Technical judgment comes from writing code, not from hearing about it.
Started pushing team-wide AI transformation in late 2025, redesigning requirements, development, design, and testing departments. Built the SpecCoding skill system covering the full chain from requirement clarification to code review. The team runs it every day.
Projects have collapsed on me, teams have spun out of control, and the transition to management was brutally uncomfortable. Eventually figured out quality systems, performance-based promotion, and pulled profit margins from single digits to nearly 30%.
I prefer retrospecting on failures. These are real failure stories, not success porn.
AI transformation isn't patching old systems with AI — it's rebuilding organizational DNA. The core is human-AI symbiosis, small-team warfare, value chain compression, platform capabilities, and new management models. Miss any one and you're dead.