Full Stack Engineer - HF - Team Leader

- Frontend's technical growth very fast. Since years ago, We have a old deliver system to deploy frontend projects, But It is too stupid, which only run "build" step in the CICD workflow And it need more complex configuration for the projects.  Final we deliver projects by manual work.

- So I built a "jinkela" ecosystem, including development tools, runtime server, auto deliver product...etc, To standardize developers workflow.

- For no-javascript projects, I researched gitlab cicd and self-host kubernetes to take over different language like go,rust,nodejs...etc.

- For zero config, I designed and developed a scaffold tool. It helps developers to transform projects, including vue, react, node-service, npm-package...etc.

- Which is 80 percent of frontend project by using "jinkela-pipeline" Now "jinkela-pipeline" be come a ecosystem. Reduce 90 per of duplicate work and manual work.

- As everyone knows, Server side renderer has many advantage by Good SEO, fast user interaction, fast internal api request..etc. But also there many disadvantage by need backend experience, Require to deploy nodejs service and CDN assets both, And Could not split backend code from frontend project.

- To solve these problems, So I designed and developed the "jinkela-core"  framework. including standardized webpack configuration and vuejs and mini-server-renderer tool.

- By the way, Recently I redesigned and refactor the new version of "jinkela-core". It be come a stand-along tool, Including vue, react both can be able to develop SSR page.

- Developers no need to deploy nodeJS and CDN assets both now. Backend code has been split from Frontend project. When you visit https://www.bilibili.com/v/channel then open the DevTool, And You will see "jinkela-core" below the BILIBILI logo. There are many pages also use "jinkela-core" to built.