Some key factors I strongly believe in that will lead to quick on-boarding Clear and good architectural design - that will help new engineer understand the blueprint of the software and rules/principle that need to follow Good code - easy to read, easy to understand, easy to maintain Clear Business goal/logics - help engineer understand the goal and direction of the project Mentorship - helpful colleagues, trainings self-driven /self-learning attitude: hire people that is willing to learn , ask questions and explore

Hi everyone, I am Zhongshi Xi, I am a software engineer in Nascent at this moment. I started as DevOps engineer for a year and 4 months where I developed automated deployment solutions using Docker, Ansible, Jenkins. Then I became data engineer where I created ETL using Hadoop, Spark and Scala in 6 months. After that I joined Nascent where I am doing full-stack development. It has been 5 months now and I am still learning a lot related to architectural design, front-end tech (HTML, React, JSX, CSS, etc) and back-end tech (NodeJs, ExpressJs, Redis, MongoDB, etc ), I have a lot to learn and I will keep learning. I am still a Junior developer but I will learn how to learn so I can learn efficiently. I will spend more time to learn & practice so I can know in depth. I do not believe full-stack dev is jack of all trade and master of none. With the right attitude, patience and effort, full-stack dev is jack of all trade and master of more than some. It has been a joyful experience since I joined this community where I ask questions and people answer them with their unique effort. I believe I can learn a lot from the community and I am willing to contribute back to the community.

Hi Jason, I would like to thank you for your detailed response and I do get some inspirations from your words. I asked a principle architect from my current company and he gave the similar answer, and he pointed out a good developer is actually good at everything, because a good developer learns how to learn and thinks how to think, they will learn tools, learn them well and piece them together well to produce solutions far better than basic ones. Thank you again for sharing your stories - that is really really helpful

Culture - being Humble , being Collaborative , always think Can I do it better

The reason that a bug can appear is due to human itself In my past 2 years I have produced bugs which of root causes can be: Bad emotion or being too much stressful which affects your approach to solving problems, in this state, you are likely not to be considerate. Simply did not pay attention to details you think your code is good - but not good enough, this is basically due to that you do not know there is something you do not know. business requirements - too complicated and not well broken down into smaller pieces Can technology help with it? I do believe technology can facilitate people to write less bug. Can technology totally remove bugs? Anything that technology can replace must be specific, repetitive and accurately quantifiable. But since various people produce various types of bugs, personally I do not believe technology can remove bugs ( But I wish I could be wrong ).