1) Your team built an app using a simple database and no caching.People love the idea, but performance collapses with 200 users. Your boss wants “quick fixes only”. How do you respond? 2) A teammate proposes a very expensive redesign. The idea is good, but the company has no budget now. How do you give honest, respectful feedback? 3) A junior dev insists on using a complex tool “because it’s cool”. It slows down the whole project. How do you communicate the need for simplicity? 4) You propose an automated solution and the client refuses: “We’ve always done it manually.” How do you persuade them without creating conflict? 5) Your team creates a feature after 3 weeks of work and users simply don’t care. What do you say as a suggestion? 6) You bring an idea to your manager. They say: “This is not viable now.” How do you respond professionally? 7) You ask for help, but your senior dev always says “I don’t have time now.” What do you do? 8) Your sprint plan looked great, until everything broke. How do you communicate the issues during stand-up? 9) A coworker tells you: “Your code works, but it's very hard to read.” How do you react, and what actions do you take? 10) You fail repeatedly at work and feel like quitting. How do you reset your mindset?
0%
Hard feedback
공유
공유
공유
만든이
U12874069
콘텐츠 편집
인쇄
퍼가기
더보기
할당
순위표
더 보기
접기
이 순위표는 현재 비공개입니다.
공유
를 클릭하여 공개할 수 있습니다.
자료 소유자가 이 순위표를 비활성화했습니다.
옵션이 자료 소유자와 다르기 때문에 이 순위표가 비활성화됩니다.
옵션 되돌리기
랜덤휠
(은)는 개방형 템플릿입니다. 순위표에 올라가는 점수를 산출하지 않습니다.
로그인이 필요합니다
비주얼 스타일
글꼴
구독 필요
옵션
템플릿 전환하기
모두 표시
액티비티를 플레이할 때 더 많은 포맷이 나타납니다.
결과 열기
링크 복사
QR 코드
삭제
자동 저장된
게임을 복구할까요?