How to be a good developer and stay in touch with changes that happens so fast?
summary
Claims that predictable estimates and reliability beat frantic chasing of every new library, with business preferring someone who promises and delivers on time. Recommends becoming T-shaped: deep in one stack and shallow across related tools, and boosting English fluency because it measurably enlarges salary and vacancy chances. Practical tactics: subscribe only to a couple of curated feeds or RSS, practice daily time estimates by comparing past tasks, and always ask PM/business who uses a feature — three team‑weeks once go to a file manager nobody used.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:52Developer salary factors
- 13:30English as key skill
- 16:17Task estimation
- 22:12Tracking tech updates
- 29:29Handling manager conflicts
related talks
33mHOW TO BE A GOOD DEVELOPER?
38mGrowing as a developer
33mWhat it takes to become a great developer!
50mThe Effective Developer - Work Smarter, Not Harder
13mKeep your skills sharp! Developer career in rapidly changing technology world.
18mThe Art and Science of Thriving Developers: 7 Key Strategies
33mHow to Enhance the Skills of Experienced Developers
47mGROWING AS A DEVELOPER
