Delivery Background
Delivery Background and Project History
Builder ProfileThe long-term mainline is eight years of frontend delivery, with two years of continued reinforcement in Python automation and small full-stack closure. The work is still being advanced in a way one person can maintain, so it is a better fit for projects that turn scripts, data flows, and business pages into governed capabilities.
The backend reinforcement is not limited to Python. Earlier there was one year of self-taught web crawling, in-company script writing, and also one year of Java full-stack work on the Ruoyi framework.
The real value is not one isolated tech label. It is the boundary awareness, release awareness, and reuse awareness accumulated through long-term delivery work.
The direct value of this kind of background is not only that it can build pages or scripts separately. It also knows how to think about data onboarding, execution entry points, permission boundaries, operation confirmation, execution traces, and release handover together. ExecFabric was formed because these issues kept reappearing in real projects and kept accumulating.
8 years frontend delivery2 years closure reinforcementPublic-sector and enterprise digitalizationGIS visualizationVue admin frontendPython automationJava / Ruoyi
EXECFABRIC // FOUNDER PROFILEMAT 05
focus: delivery / governancecore: gis_frontend / automationproduct: execfabric
DELIVERY FIRST, PRODUCT NEXT
Key Points
This page mainly helps judge whether the delivery background fits
It is best used before going deeper in conversation, to quickly see the long-term mainline, project types, and whether there is real closure experience from delivery work.
Who it is forTechnical leads, project owners, and anyone who needs to judge delivery credibility first.
What to focus onThe long-term mainline, representative project types, and whether real project closure has actually been done.
What to read nextIf the direction fits, combine this with Projects and Resume and Kickoff Options to judge whether it is worth continuing.
Track 01
Eight-year frontend delivery mainline
The core experience has long been concentrated in GIS visualization, map business pages, Vue admin systems, large dashboards, and complex business pages. This is not a short-term stitched skill set.
Track 02
Two years of reinforcement in automation and closure
Over the past two years the work has continued to reinforce Python automation, data handling, warehousing, report generation, and small to medium backend support. Earlier there was also one year of Java full-stack work on the Ruoyi framework, plus self-written company scripts, so backend reinforcement is not limited to Python alone.
Track 03
Well suited to a governance platform
Too many projects have had scripts that could run but could not really be delivered, which creates stronger sensitivity to permission boundaries, execution confirmation, audit traces, and release handover.
Project Value
Direct value to a project
- It can start from a real workflow instead of opening with an oversized platform story.
- It has clear awareness of permissions, audit, responsibility boundaries, and execution risk, which suits formal delivery environments.
- It can close script capabilities, page entry points, data movement, and deliverables from one shared perspective.
- It is used to building a smallest runnable, verifiable, handover-ready closure first, then deciding whether to expand into phase two.
Public Links
Public entry points
Related Materials
Related pages
OverviewBackground Overview
Quickly judge the current mainline capability, fitting project types, and present boundary.
ResumeProjects and ResumeView a more standard skill stack, project history, representative work, and public information.
CooperationKickoff Options / Service PackagesSee what kind of project start fits right now, how scope should close, and how service packages are organized.
Experience
Main experience in recent years
| Period | Company / role | Main direction | Key work |
|---|---|---|---|
| 2024.04 - 2026.04 | China Mobile Design Institute / Web Frontend Engineer | GIS, automation, frontend first | Wireless-network quality evaluation, OpenLayers map modules, Python data collection and processing, PostgreSQL / PostGIS, and AI conversation-assistant integration. |
| 2021.09 - 2024.01 | Huanya Digital Economy Research Institute / Web Frontend Engineer | Mapbox, dashboards, admin systems, mini programs | Commercial-cloud traffic brain, shop management, energy control, UniApp mini programs, and Vue3 / Vite / Element Plus admin frontend delivery. |
| 2020.10 - 2021.07 | Beijing Tiantian Smart Power / Web Frontend Engineer | Power back office, cockpit dashboards, data collection | Power-sales management platform, contract approval, complex multi-tab interaction, data cockpits, and data collection and warehousing under legitimate authorization. |
| 2019.10 - 2020.09 | Hangzhou Dehui Information Technology / Web Frontend Engineer / Technical Lead | Cesium, 3D visualization, team delivery | Led frontend frameworks and conventions, and delivered multiple public-sector and enterprise GIS 3D projects covering model loading, monomer modeling, video projection, and IoT data linkage. |
| 2015 - 2019 | Earlier experience | E-commerce, official accounts, mini programs, admin systems, full-stack reinforcement | Continued accumulation of frontend basics, API integration, compatibility handling, official-account and mini-program work, and admin-system delivery. During this period there was also one year of self-taught web crawling, one year of Java full-stack work on the Ruoyi framework, and self-written scripts inside company scenarios. |
Representative Work
Representative project types
- Wireless-network quality-evaluation systems where map visualization, spatial data, business data linkage, and automation processing all landed together.
- OMC server-management platforms with WebSocket log display, large IndexedDB caching, file editing, and upload chains.
- Mapbox / Cesium visualization projects with multi-city switching, point linkage, model display, video projection, and business-side linkage.
- CSV / Excel automation sync with Python calculation, batch warehousing, report generation, and closure of repeated flows.
- Internal company scripting and data-capture flows where scripts were written directly for data capture, cleaning, export, and repeated-process closure.
Current Fit
Cooperation scenarios worth starting first
- GIS visualization, map business pages, and public-sector or enterprise visualization support work.
- Vue admin systems, Ruoyi-style back offices, inherited legacy projects, and frontend joint debugging and maintenance.
- Reports, files, data capture, export, internal company scripts, and Python automation-process closure.
- Frontend-led small full-stack closure, including Ruoyi-style Java backend and automation reinforcement.
- Turning local scripts, page entry points, and execution traces into a more controlled smallest closure.
Why ExecFabric
How this background maps to ExecFabric
- GIS and admin-frontend experience means the platform entry must be visible, operable, and reviewable instead of staying only in a command line or script directory.
- Automation and data-handling experience maps directly to the platform's most mature execution asset today, Python scripts. Experience in Java and Ruoyi-style backend reinforcement also keeps the platform design from being trapped by one language perspective.
- Public-sector and enterprise delivery experience naturally pushes permissions, confirmation, traces, gray release, handover, and responsibility boundaries up in the design priority.
- Long-term project delivery work also makes it clearer that platform capabilities have to be abstracted from real workflows instead of starting from concepts first.
Working Style
How the work moves
- Start with one real workflow to close scope instead of spreading the project boundary too wide in the first round.
- Clarify inputs, outputs, cycle, boundary, and exclusions before pricing and expansion-stage discussion.
- Prioritize things that are deliverable, maintainable, and reusable over stacking presentation-only features.
- If a scenario is not a good fit, say so directly instead of dragging the conversation into ambiguity.
Next Step
Scenarios worth discussing further
The most effective next move is usually to take one real workflow and talk directly about inputs, outputs, boundaries, and phase-one goals. That is faster than staying in abstraction.