If we are doing a meeting to discuss a problem and the solution, a good alternative would be to share a document. The document should clearly explain: What we are doing? (To understand the problem and context) Why we are doing? (Context around why this is important and use cases) How are we solving it? (Propose a clear and concise solution) Once the document is shared we can have the following scenarios: Accept the solution : Next step - No meeting required Reject the solution : Next step - Propose a new solution. Run the same process or have a meeting to discuss the two solutions. Suggestions : Next step - The owner can decide to accept/reject suggestions. Doubts/questions : Next step - Depending upon the question, answer it in the doc or continue with the meeting. This is actually not a complete replacement for meetings but adding this step may help reduce the number of meetings.

Great question! I also have asked myself the same question many times! And it is true that work experience has a major impact on building up your skills. E.g. if I want to be a back-end developer and at the beginning of my career and I get to work in a new project. The team is great, feedback is constructive, I get to see and understand various trade-offs in the design of the architecture & choosing different frameworks/technologies, seniors developers act as mentors, etc. Working in such an environment no doubt accelerates your growth. But what if that is not the experience you are getting at your workplace. I think in such cases the important thing is to identify where you want to focus. Do you want to be a back-end, front-end, UI designer, UI Developer, etc? If you want to be a front-end dev, what does is it mean to be a front-end dev? For me, I wasn't clear which path I wanted to take at the beginning of my career. I kept learning whatever came in my path and whichever tech was popular. It was really haphazard. Personally, if I had to do that all over again I would choose the area I want to grow in and focus on getting my basics right. E.g. for back-end it could be algorithms, OS basics, etc and for front-end, it could be getting the fundamentals of JavaScript right, CSS basics like box-model, etc. Once you have the direction then understand the concepts and make sure you implement it in a side-project or at work. Also, I cannot emphasize the importance of participating in tech discussions or events (online or physically) enough. I hope it helps! Thank you for asking!

A book on similar topic is "Barking up the wrong tree" by Eric Barker. I think you will find it engaging.

Thanks for the answer Tapas! Long answers are good :) That's a very interesting point of view. Not stressing about long-term goals and focusing on short-term goals with plan looks like a great approach. Especially the flexibility that you get with it. It's very helpful. Definitely something that got me thinking in the right direction. Thanks!

Thanks Victoria! It definitely helps. The book recommendation ("Mastery" by Robert Greene) does look interesting. I have added it to my reading list. Planning your day with daily goals and asking yourself the reason for doing them does ensure you are doing what is really important to you. Maybe making everyday a little more focused is what makes a difference. I do some of these things and no doubt I need to get better at them. Thanks for the answer!

q1w2e3 Yes, that's possible.

I think the problem here could be that you haven't separated the development changes from the validation changes. Maybe what you could do is to have a workflow like dev > validate > master . When you have the required changes ready you merge dev into validate . Test everything on validate branch and then sync the changes to master . While you are validating if there are any new changes they can be merged to dev branch without affecting your validation process.

Yes that's possible. Basically: Create a GitHub account (if not already done) Create a new repository Add the required files to it git commit and git push Check this out: https://docs.github.com/en/github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line