Productivity Tips From Developers to Developers

• You don't get paid by size of commit or number of lines produced (if you do, get out of there). Avoid coding first, most likely what you are solving has already been solved. This forces you to think in abstracts about your problem (in order to find the package you need). Abstraction is at the core of programming.
• Don't modify anything in get
• Caching is a performance optimization and cause of many subtle bugs. Use with care.
• Avoid the golden hammer. There is no one way to do something and learn early on to formulate your options, pros and cons and pick the one that works for that situation. Also avoid cultures that enforce this "one way to do something".
• Code formatting is not something worth spending time on in this day and age. Pick an opiniated formatter, configure it and run with it.
• Bugs will happen. They don't define your self-worth or competence and avoid any company culture that make you feel worse about yourself when you left a bug in your code. Instead: Own the bugs, analyze them (ask help from seniors if you get stuck) and learn.
• And last but not least: commit messages are not about what you did (I can read that in git log -p), but about WHY you did it. About the context of the change. Reference tickets. Summarize your analysis. This will tremendously help your future self, your new team mate or the person fixing a bug to understand the code and what happened to it over time.

1. Know your development environment and tools. Know your editor like the back of your hand. What’s the quickest way to find a class or refactor a method? Take time to learn the shortcuts and use them in your work
2. Take care of yourself. Sleep well, eat well, give enough rest to your head, do hobbies - live a healthy and exciting life outside work
3. Document your code for yourself and your team
4. Track working time. Developers often feel like they are not productive enough. Most of the time, it's not true. Use a free time tracker to record time you've spent on your tasks and document important actions and milestones
5. Practice journaling. I use tables in Notion to record my sleeping, eating, sports and activity habits, track productivity and mood. It might sound like a waste of time but after you have data for a few months, you'll see what gives your energy and life satisfaction and what drains it from you
6. Meditate to stop your mind from wandering and to make it more sharp and focused
7. Practice gratitude. It's a great tool from positive psychology that, if done daily, restructures your mind and teaches you to feel more positive and satisfied, value small things and feel more stable when moving towards your goals
8. Take breaks. When you feel stuck, take a short walk outside to have some fresh air, give your eyes some rest and treat yourself with a cup of Joe

Hope it helps! :)

Never rush to code. Something my seniors taught me, plan first. Like really plan it in your head, writing the final thing down takes very little time. Figuring all of it out, that is what takes skill and patience

• Be a stoic. I'm not a big fan of phylosophy, but stoicism changed my attitude towards life and career. It teaches you to make the most of what you have, be a warrior that is headstrong, learn from mistakes and be mindful of what's going on in your life and career. Here are 10 priciples to help you get started.
• Invest in noise canceling headphones. Whether you work in the office or from home, you need to concetrate to work in the flow.
• Work out to stay fit and healthy and release stress

To my previous self:
"
You will read more code than you will create code.
If you don't understand something, don't be ashamed.
Communicate your problems with your manager.
Take care of your health! That's the most important thing I can say!
Research the company you will be working for and understand that a 50% recommendation is bad.
Understand that many people in a company use MS Excel.
Understand that bureaucracy is an essential part of the job.
You will attend many meetings, so you will learn how to communicate and understand the tools the company offers for communication (Skype, Teams, Zoom, etc.).
IT department is generally slow, learn to be patient.
learn Git.
Understand Scrum.
Learn Confluence.
Learn how to create batch files to make your work easier.
Learn Bitbucket.
Understand tickets.
Your colleagues are not like your friends or family.
Study the organization chart of the company.
Create a code journal.
Document important events.
Take out legal protection insurance.

You did great for doing all of the above!

Sincerely

Me
"

Very important:

• Workout 30 minutes every day
• Drink enough water
• Don't be afraid to ask questions ("There are no stupid questions")
• Listen to others but think with your mind
• Read articles related to what you are working on at the moment. Every day!
• Work Smarter not Harder. Don't code 14 hours in a row!
• Share your knowledge without expecting anything in return.
• Make mistakes
• Be honest with yourself

Important:

• Plan then code
• Do not overcomplicate a simple task
• Reuse existing code
• Make it work then optimize
• Write self explanatory code
• Don't use beta things in production
• Use Cache, but with care
• Document the code
• Estimate !== Deadline

I'm still junior dev so I don't have much productivity tips to give.
But I have to share something is that as a junior dev

1. starting sharing knowledge with others in form of article/short explanatory video in other words "learning and building in public" .
   If you are sharing knowledge in form of article it will help others definitely but it will also make Documentation/writing skills of ourselves better.

2. Try doing open source contribution.
   It will help you get experience by working on real world and widely used software/project. And even help you to learn huge codebase.

3. And yes important thing
   soft skills >> technical skills
   Now a days developer jobs are moving remote so it becomes important having better collaboration and teamwork skills. Public speaking adds advantage .

4. And one more important thing don't just go on drinking coffee to code for a long time instead drink more water that too helps.

5. And as a junior dev use Twitter you will definitely learn a lot from professional devs through there tweets/threads and twitter spaces.

• Be lazy about writing code, not about planning
• Automate yourself above all else
• Only consider the far end of the productivity curve
• Refactor all the time

• Write less code. Once you start writing it - everything slows down / and your perspective gets boxed in. Just write it on paper / or in comments - or draw a picture.

• Talk with people about your idea with someone else and see if you can get another way to look at it and maybe learn something. Learn in public.

• Create small prototypes and show them to humans on real devices. They'll notice things you didn't and then you can incorporate those things.

• Use a time timer to time-box and also to force yourself not to work.

• Stop pretending you can multitask.

• Actually know how to use your computer well. It's your main tool.

• Sleep. Working "hard" is not working smart.

• Have a social life. Otherwise, what's the point?

• If you watch a tutorial, don't code along. Just take notes on the concepts

• Stay out of the CMS for as long as possible, because that's the biggest bottleneck

• Avoid anything that isn't absolutely necessary. Do you need that package, library, buildtool, future-tech-debt-machine? Do you need smartsheets, trello, monday, and more tasks to take up your time? Or would a simple README be even better?