๐ช๐ฟ๐ถ๐๐ถ๐ป๐ด ๐๐ผ๐ฑ๐ฒ ๐๐ ๐ข๐ป๐น๐ ๐ฎ๐ฌ% ๐ข๐ณ ๐ง๐ต๐ฒ ๐๐ผ๐ฏ
I started my first dev job thinking I would code all day. I was wrong. I spent more time in Slack and Figma than in my editor.
School teaches you algorithms. Real jobs require more. You spend time asking why a button exists. You argue about API returns. You explain timelines to managers. Coding is the last step.
I once added a date filter. The final code was 15 lines. It took 8 hours.
- 1 hour for product alignment.
- 2 hours for a Safari bug.
- 1 hour for tests.
- 30 minutes for notes.
- 1 hour for code review.
- The rest for coding.
These skills save time:
- Find context in chat threads.
- Translate tech talk for managers.
- Fix bugs which only happen in production.
- Say no by explaining the cost.
Trade-offs exist. More meetings mean less coding but less rework. Better docs mean fewer features but fewer questions.
Senior devs write less code. They solve problems before they reach the keyboard.
Try these tips:
- Set deep work hours.
- Take technical tasks like refactoring.
- Start side projects for pure coding.
Software work is 20% code. It is 80% communication.
Source: https://dev.to/taina_costa_f/spoiler-escrever-codigo-e-so-20-do-trabalho-3ak