This is a weekly roundup of awesome DEV comments that you may have missed. You are welcome and encouraged to boost posts and comments yourself using the #bestofdev tag.
Some wins :)
Learned some more about Gatsby and Gatsby cloud. Looking forward to taking a full course on these services and doing a project using them!
My portfolio post got a React badge and lovely feedback from the DEV community. Putting my work "out there" was kind of scary, but everyone is really kind and constructive in their feedback. Can't wait to start implementing some of the advice/suggestion shared on it.
Nice 😄, Very important for all IT Professionals in the World. Taking home below points:
- Don't try to learn ALL new technologies or Master Everything, Learn only what is necessary. Example: If you know
Reactskill then its not necessary that you should know
Svelte. Be Focused in your field,
full stack developer, do research on Job market and focus on set of tools necessary for the Job.
- Don't compare yourself with other engineers career progress and get demotivated INSTEAD be good at your skills which helps you to get the Job done.
- After 8 hours of work, avoid using tech gadgets again to check mails etc, INSTEAD give relax to you mind, take rest for sometime.
- Work is work, your health is important than work. Programming is not everything, give importance to other parts of life like friends, family, spend time with them.
- Taking rest can help you think sharp and be focused in the Job. Every 1 hour go for 5 min walk to avoid health issues. Every 20 min look away from screen to keep your eyes healthy.
- Avoid imposter syndrome by saying: am i good developer ?, can i learn that new skill ? , can i make it in this field ? Avoid these questions instead take this as motivation to learn necessary skills for the Job.
- No one can become the best developer in the world, but all can become decent developer by contributing to workplace . Becoming better developer is a journey but NOT a 3 months crash course.
this advice should added in Welcome mail when user joins
DEV and promotional mails.
I agree with your points, Abdul. With our industry, it's easy to get distracted by the next big thing and it becomes too easy to abandon what you're currently studying in pursuit of that hotter fresher thing. Mastery comes with depth, and having depth means investing a good amount of time in it.
Be careful though, always go refactor with baby steps. Verify after every small change that the code is still working as it should. Automated tests are incredibly useful for this.
If you try to make multiple changes at once, it's easier to lose sight of what could be affected. Also, the combination of multiple changes will result in an exponential number of issues that can be caused.
One of the best and easiest way to refactor is to rename and move things. Learn the hotkey of your IDE to rename variables, classes, functions and files. It will make the code much more understandable for the next developer (or yourself after a few weeks)
See you next week for more great comments ✌