Celebrate work anniversaries by reflecting on your accomplishments. Then do that once a month rather than once a year. Keep growing an learning, always.
Be prepared vs YAGNI:
Be prepared means you should plan for things and think ahead. Don't be caught off guard.
YAGNI: You Are Not Going To Need It. This means don't build "just in case" features. Fail gracefully and guild what you know is needed.
There is room for both.
Imposter Syndrome is when you may feel like you're an imposter in your position, but you're better than you think. Guru Syndrome is when you've become good enough that you think you're the best, but there's usually more to learn. Watch out for both.
"Turn it off and on again" works for so many things. Remove the node_modules directory, reinstall non-working software, remove and repair a Bluetooth device. There's a reason the phrase is so well known.
When starting a new project (with a team or solo), define your coding standards and document them. Then configure your IDE and/or deploy process to support/nudge/enforce your standards. This leads to a cleaner codebase and faster future work.
Interruptions can be really disruptive. For anything with notifications (including your phone), configure settings to reduce non-urgent interruptions during your dev time.
Ask questions early and often. Getting help save you lots of time and you can re-invest some of that saved time helping others when you know the answer. #learningtips
Step back from your code at least once a day and ask:
Does each function do one thing and is it tested?
Can anything be refactored?
Are we coding with security in mind?
#devtips
Being great developer is more than just code. Invest also in your communication skills and emotional intelligence and you'll bring loads more to your team and project.
If it's important enough for a code quality gate (unit tests, linting, etc), you can automate pre-pipeline checks to save lots of time and frustration.