How Do I Transition from Coding Course to Real-World Programming?

When starting a new job, especially as a newbie, it's totally normal to feel stuck. You don't yet know the codebase or the domain you're working in. I remember when I started my first dev job, it took me a good 6 to 12 months just to learn the domain. It’s an expected learning curve, so don't be too hard on yourself. Just take your time, ask questions, and you'll get the hang of it!

As a junior dev, it's unfair to compare your pace to that of a senior. Just being able to figure out a ticket is a success in itself! If you see someone solve problems quickly, ask to shadow them. Learning their thought process and problem-solving techniques will help you understand better, and over time, you'll develop your own speed.

Odin should definitely be enough to get you prepared. Also consider tackling CS50 if you feel your programming skills need a boost.

Don't be too hard on yourself; what you're going through is super common! Courses often teach the tools, but figuring out how to apply them to real-world problems takes practice. Start with small projects that focus on one concept, like a to-do app or a simple weather app. And don’t sweat it if your colleague solves issues faster—experience will help you recognize patterns and connect the dots. Just keep building!

If you're feeling overwhelmed, that's just a sign that you're pushing your limits, which is a good thing! Problem breakdown is key. Try starting with simple, working prototypes—once they are up and running, the structure will often emerge naturally. Also, use a whiteboard or a rubber duck to talk through your thought process. And remember, the best engineering involves clear communication. Don’t hesitate to piggyback on your colleagues’ knowledge and experiences!