How should I set time apart for learning new things?
I am a new grad Software Engineer who has completed 6 months ago. There's a lot of internal tech stack and plenty of codelabs. Lately, I have realised that I am not prioritising learning about the stack my team uses (but I do not currently use directly).
I understand it would be helpful in one-off occasions when I have to interact with a new part of the codebase or during on-call, which I am expected to begin soon. However, I always end up prioritising my current work that I have in hand. (It is also because of the fact that I find the codelabs pretty slow and boring)
How should I prioritise learning new things? I remember Rachel's video where she said she spends 20% of her time learning new things and that seemed like a good strategy to me.
![Entry-Level Software Engineer [SDE 1] at Amazon company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Famazon_logo.jpg%3Falt%3Dmedia%26token%3Dff5f2302-08be-43bc-b7b1-d381ba508d99&w=48&q=75){kind=logo}
Discussion
(4 comments)
5 months agoMistplayIt’s great to get your own work done before doing extra learning that is tangential. Having a goal to finish your sprint early though, and then using the time to crank out some study time seems like a strategy that could work.
Another option is talking to your manager about your desire/need for the study time and seeing if you can build 20% time for that into sprint planning. Something to try would be asking for those one-off tasks that you need the knowledge so you are practicing what you learn and demonstrating the study time is allowing you to increase your scope.
4 Likes- 5 months agoComstock Software, Inc
Set aside Monday afternoons and Friday mornings. They are usually slower times of the week.
0 Likes - 5 months agoComstock Software, Inc
Love the idea from MistPlay to build 20% learn time into your estimates. Genius!
0 Likes - 5 months agoComstock Software, Inc
If you're a young person working in tech, right out of college, without work experience... you need real war stories. Here are 3 ideas to get you started:
• Manage to get yourself fired at a side job (wait tables, work a cash register, stock shelves). There now that you know what that's like, it's not that bad; you know what it takes; let's not do that again.
• Manage to get yourself promoted to lead, supervisor, or manager at another side job. Now you know what it's like leading people. It's not easy. Now that you know what it's like to be the boss, you know how to help your boss, she's your customer, and now you know what she needs.
• Go shopping for something expensive you want that you know nothing about. Shop around in person and over the phone, and see what it's like to be a potential customer. You'll have people try to tell you every product or solution is good for you; it's not helpful, and now you know what not to do. Eventually, you'll run into a salesperson who recommends something out of all the options. This option will be the best for you based on price, value, features, and other considerations. Now you know what it feels like to be served well. If you're unsure where to go... go to Nordstrom's for business clothes.
With this newfound experience, you're going to be better suited to serve real people in the tech industry.1 Like
