Data Engineer: Appendix
용어집
저희는 명확한 언어를 사용하기 위해 노력하고 있지만, 몇 가지 단어에 대해서는 해석을 설명하는 것이 도움이 될 수 있습니다.
기술 책임 정의
The responsibilities defined below make up the foundation of the Data Engineer craft:
- Code fluency: 유창하고 능숙하게 코드를 읽고 쓸 수 있는 능력. Code for a data engineer is both software (Python, etc) and SQL
- Data and Software design: The ability to design software components with reasonable APIs and interaction patterns (writing good classes, modules, etc - building out a box in your architecture diagram) as well as intuitive data models which abstract the complexity of upstream data sources at an appropriate level of optimization for data user needs
- Architecture design: The ability to design systems of interacting components - e.g. a collection of interacting features or the architecture of a product, binary or significant service (what are the boxes in your architecture diagram, how do they interact). This is inclusive of the architecture of a data model and the data pipelines required to produce that data model
- Technical strategy: Ensuring the right long-term technical and data decisions are being made by the organization - knowing what systems and data models to build; making technical choices when there are not clear solutions. What standards apply to all the boxes in the organizations architecture diagrams?