This is the right answer. I taught at a programming bootcamp for a few years. When we got to React, we taught it in a single 2-day sprint — but that was possible because by then (most) students had proficiency with HTML, CSS, and vanilla JS. Spend your time on that stuff if you don’t have front end experience. When you get to React, you can just learn from the documentation — it’s very well written and the part explaining the main concepts is not long (I also like what I’ve seen of the Odin project, though I haven’t seen the React part specifically). Aside from that, you’re an intern, nobody expects you to know anything. You want to impress people as an intern? Be organized and proactive. I don’t care that you know nothing so long as you’re coachable, you’re learning, and you’re moving the ball forward without me having to do literally everything for you. Here’s some actionable advice. Keep a “todo list” and order it by priority at the end of every day. Keep a “my questions” list so that you’re not asking for help every 10 minutes, but when someone actually does take time to help you, you can quickly get all your questions answered. When you get a challenging task to work on, consider writing out an “investigation doc” as you work on it. It’s almost like a journal of what you’ve done. This is a place where you track what you’re trying to do, what your hypotheses are for how to accomplish that thing, what you’ve tried while investigating each hypotheses, what evidence you have for any conclusions you’ve drawn, and also descriptions of any blockers you’ve run into along the way. Add screenshots and any mysterious error messages as well as any relevant links, etc. It’s unimpressive to say, “Hi, I’m confused. I need help.” It’s very impressive to say “So I’m trying to accomplish A. I’ve tried B, C, E based on these links. I don’t think those work because of X, Y, and Z. My best theories for how to proceed are F or G. Do you think that’s a good direction to go? Is there anything I’m missing?”