# Best technique in approaching ALX Software Engineering tasks and curriculum
Introduction:
Would you believe me if I tell you that it is really challenging to do a 70 hr/week course with most tasks having a 24hr deadline alone. This is reality and that is why if you have problems working with people then you may want to adjust for this program and for future jobs. The need for working with peers have been emphasized by the ALX team, and the end result is a community you give to sustain and get help from when in need of help.
So why this article? Pardon my lengthy introduction oh ye men of little patience. Next I am going to be sharing the approach senior cohort members have been implementing to excel and also the technique I use and it has been working great, ok lets get it.
Technique and steps to try out:
- Read through the project page
- Read the resources even the man pages diligently
- PSEUDO before CODE
- Cut yourself some SLACK
- Peer learning days not Holidays
- Get good sleep
Ok let's look at each of them.
Read through the project page
Skim through these sections on the project page but don't click on any link just yet. These sections include Concepts, Resources, Learning Objectives, Requirements and More Info. This will get you to the rhythm and give you an overview of what you are learning on that day. It's important as you also read the requirements and instructions that will be vital to scaling through the project.
Read the resources even the man pages diligently
Seems like a lot of work on a good day in an ALX classroom, but this right here is at the core of you being successful or failing in this programme and out there as a software engineer. In fact in Software engineering there is a continuous loop of reading docs. If it becomes part of you, you can't go wrong.
For those who do not have the time, maybe an 8am - 8pm worker can leverage on their peers. If you are lucky to have a Buddy who can explain the Learning Objectives decently and other sections can save you some time and then you do the catching up during weekends when you don't work.
PSEUDO before CODE
This title is a word play, pardon my writing style. Write your solutions to a task on paper before jumping to code. This could save you hours of staring at your pc in futility. Keep an eye on the technologies allowed to be used and instructions. Type in the code with your own hands even if you are copying someone else, this will help it stick as you do it over and over again.
Not submitting before the first deadline is not the worst that can happen to you. At Least it is not worse than putting a code in your repository that you don't understand at all. If you are submitting after the first deadline then do the advanced tasks to boost.
Cut yourself some SLACK
Another word play here, no apologies this time :). Slack should be one of the best technologies we use in this programme. Have you asked yourself this question at any time "What if there was no slack or community for this programme?". Slack is for us. Slack has saved me in situations when I got stuck, but by asking for help I was rescued.
Now please respect people's time, you too can help someone out you should not only go there to get answers. Respect people's time by reading the resources, so when you ask questions others can relate to it easily. Ask specific questions and not for answers like you did in objective questions in high school. Questions like "What is the answer to task 2" should be a taboo. Instead you want to try it to the best you can, then share your well commented code and ask what you are doing wrong. In this way once corrected it sticks.
Peer learning days not Holidays
What do you do on these days, here a day set apart to impact someone's learning or receive the same. So take time no pressure to read about the project to be discussed in a way you can easily explain the concepts to someone else. Once you are done look for a buddy to help or start a huddle on slack, while discussing be open to learn from your peer because you can't know all. If your peer is prepared as you are then its a party of irons sharpening each other.
Personally, my buddy group is dull, so every peer learning day I start a huddle on the slack cohort channel and explain solutions to the previous Advance Tasks as well as take corrections and inputs from others.
Get good sleep
Night crawlers won't like this, get at least 6 hrs of sleep, this is the bare minimum, I think 7hr is standard, I am not medically inclined and this may not be applicable for everybody but just get enough rest. This will refresh your brain and get it ready for the day's tasks.
Conclusion
So my ALX brothers and sisters as senior mentor Maarten van Middelaar would say :) this is not all there is to say, I Just shared my approach and the advice gotten from some senior cohort members. Feel free to implement this and see how you grow. You can also use the comment section to point out some areas i did not do not cover and also help me improve or reach out to me on these platforms