We all have the same 24 hours in a day - The difference is that some are able to get far more out of it than others. Here's what they're doing that others aren't.
And not only equates story points to hours but is constantly looking at your story points and tries to lower them in an effort to push more work to you. I feel like I'm an assembly line worker instead of a software engineer that solves problems. Have any of you experienced anything similar?
How do you keep up with everything that is happening on the team with different projects, doc designs and code reviews?
Even being a Taro premium user, I'm unable to participate in all the events, though I heavily need mentorship, seems like a roadblock for me because on LinkedIn I see so many posts, it's very difficult to catch up.
I have been repeatedly told that I have a tendency to drop things when doing context switch between multiple tasks. How to manage my tasks effectively so that I can minimize this pattern?
I am getting overwhelmed with my work, in this team for about 1 year. How should I optimize to squeeze time to help others?
Helping others gives me more joy than doing my own work :) . that is not my core work though.
These days, I hear a lots of news about the new AI tools like Chat GPT, Bard and so on. Will we see a decline in requirements for software engineers in the foreseeable future? Will companies begin to prioritize AI-domain engineers over software engineering?
Should I check it first thing in the morning to see if I have any urgent things to work on or should I try and continue working on whatever project I was working on the previous day and try and crank out that couple hours of productive work above all else?
I watched the video I am particularly interested in the point: "Great TLs sequence their project in such a way that all the highest risk things get knocked out first". Can you please give examples of doing that in a real life? What are some examples of activities that you found higher risk than others and therefore you decided to do them first to minimize the risk?
In one of the videos Alex mentioned that some devs get a culture shock when joining a Big Tech company from a smaller company. What kind of culture shock would that be? Do you have examples and methods how to prepare oneself for those?
Alex and Rahul and the other senior people on Taro have consistently emphasized how important good software engineering fundamentals are to long-term career success as a software engineer. This is in contrast to learning the latest popular framework or area of development. Can people define what those fundamentals are and how one should go about acquiring/improving them?
Thanks!
I get a lot of JIRA tickets for bugs where it's not clear what the fix should be. How can I find the problem area and relevant code faster with these issues?
I work overtime a lot, and it's pretty stressful. I'm also worried that amidst all this effort working for Meta, I'll lose track of who I am overall and what I can do for other companies. What can I do to strike a better balance here?
I think most people will default to how many hours you put into work. But at what point do we say someone is working hard? Is it working 40hours/week? 50hours/week? or 80-100hours/week?
And how do these hours vary by geography?
I'm mainly working remotely due to covid and a team distributed across time zones, but I feel like earlier-in-career engineers like myself should have more in-person work. How can I overcome the barriers of remote work?
I'm a self-taught, aspiring Android engineer, looking to land my 1st full-time role. I have around 4 hours a day to learn software development, and I'm wondering how I can spend my time the most efficiently. Here are the 2 core things I want to understand how to balance my time between: