Study Strategies
Most people study inefficiently. This is mainly because they never really learned how to study the right way, even after years of university in some cases! In this chapter, we will show you some of the most important strategies for learning in a much more time-efficient way.
📅 Planning
The first part of studying should be to make a study plan. Your project work will consist of various components:
Live interaction in the sessions with your guides and team
Project Tasks & Tickets - where you apply what you learned
Project Tasks & Tickets: Working on project tickets takes most of your time each week. For the Full Stack Circle, it can be between 10-15 hours! Break down your tickets into smaller, manageable tasks and allocate time for each. Start working on tickets early rather than waiting until the sprint deadline approaches.
Research the necessary technologies for your assigned ticket
Apply this knowledge in implementing your ticket
Prepare updates and questions for the next session
Planning helps to allocate time to coding. Remember, you are in charge of your learning journey!
💻 Don't Just Read, Code It!
Reading about programming concepts or watching demonstrations isn't enough to develop coding skills. Your journey in the Full Stack Circle is all around practical, team-based project experience. Each sprint, you'll have specific tickets to work on. Try to complete your tickets entirely and experiment with the codebase.
Dedicate time to code daily, even if it's just 30 minutes - consistency is more effective than occasional long sessions.
Don't be afraid to experiment beyond the requirements - try alternative approaches and explore "what if" scenarios.
When stuck, try solving the problem yourself before seeking help - this builds critical problem-solving muscles needed in professional development.
❔Ask Questions!
Many students find it hard to ask questions during the sessions and online (through Slack or otherwise). However, becoming a good programmer means you dare to ask many questions. Some tech companies even have a rule: If you are stuck, you have one hour to solve the problem. If you cannot, you have to ask for help. At ReDI School, there are several ways to ask for help:
Ask your teammates or a student from your course
Ask in Slack (preferably in your classroom channel)
Approach a guide during breaks or through Slack in a group
Ask ReDI staff to connect you to a graduate or guide
Summary
Plan your project work - Create a weekly schedule with 10-15 hours for ticket implementation, break tickets into manageable tasks, and start early rather than waiting for sprint deadlines.
Code, don't just read - Build your skills through consistent hands-on practice rather than passive learning; commit code to the project repository daily, even for small improvements.
Ask questions when stuck - Seeking help is a professional skill; use all available channels (team sessions, Slack, peers). Asking questions is a superpower in collaborative development!
Last updated