Tip&Talk01.md

{Tip&Talk} 왜 풀스택인가? (feat. 개발자 커리어 패스)

Publisher

• Design
• HTML
• CSS/SASS
• a little JS

FE Engineer

• a little Design
• HTML, HTTP
• CSS/SASS
• JS/TS
• React & React Native
  (Vue, Angular, Ember etc.)
• a little Native

Mobile App Engineer

• a little Linux, Design
• a little HTML5, HTTP, JS
• Presentation like CSS/SASS
• Java, Kotlin (Android Platform)
• Object C, Swift (iOS Platform)
• Rust, Dart (Flutter), Electron
• React Native, Xamarin, etc...
• a little Database, Cordova

Back-End Engineer

• Linux, Cloud, DevOps, SE
• a little Front-End
• System Design
• DBA (Data Engineering)
• Java (Spring, Spring Boot)
• Node.js (Express, Koa)
• Python (Flask, Django)
• PHP, .NET etc.

Architect, Modeler, System Designer

• System Engineer (SE, Infra)
• S/W Engineering
• a little DevOps
• a little DBA
• a little Back-End
• a little Developing Methodology
• a little Project Management
• Wealth of Dev. Experience

System Engineer

• Computer Architecture
• Linux (for Windows Server)
• Network
• Cloud Platform (Infrastructure)
• Security
• a little DBA, Back-End

DevOps (CI/CD)

• Git (Github, Gitlab, BitBucket)
• Jenkins, Circle CI, Bamboo, etc.
• AWS CodeDeploy, GCP Deploy, Manager, etc.
• Test Platform (TDD)
• a little Back-End, Front-End
• a little DBA, SE

DBA

• a little System Engineer
• Wealth of DBMS
• DataBase Design (Modeling)
• Turning, Backup, Restore
• SQL
• Security
• a little Back-End
• a little Redis, Elastic Search, etc.

Data Scientist, Data Analyst, Data Engineer

• Data Scientist

  • Math, Algorithm
  • Study Domain Knowledge
  • Data Analyze(ML/DL) Modeling
  • Learning Machine
  • a little SQL

• Data Analyst

  • Data Analyzing
  • Data Reporting / Visualization
  • Study Domain Knowledge
  • a litte SQL

• Data Engineer

  • a little Data Scientist / Analyst
  • Back-End Engineer
  • a little Front-End Engineer
  • a little System Engineer
  • and the Other chores

FullStack Engineer

• Front-End Engineer
• Back-End Engineer
• Architect / Modeler / SD

Why Full Stack?

• BE를 아는 FE vs. BE를 모르는 FE
• AI Coding (전문화의 위험성)
• PolyMath (지식의 연결 => 위대함)
• 인문학 등 교양, 기획력
• IT 기술력
• 창업
• 다른 개발자 컨트롤 할 수 있어야 함 (풀스택 개발자 필수)
• 원인 빠르게 찾을 수 있음
• real full stack developer
  • Publisher
  • FE
  • BE
  • Architect / Modeler / SD
  • SE
  • DevOps
  • DBA
  • [Data Engineer + Scientist]

[Note]

• Engineer (coder/programmer) vs. Developer (Architect + ...)
• cross platform; HTML5 -> Native
• graphql; ORM 방식 => DB에 부담을 많이 줌
  (join은 괜찮지만 세부적 쿼리 힘듦)

Reference