Skip to main content

So much things to do, Yet Idle

It's kind of weird but sometimes, I just have tons of things to do, yet I am reluctant to do any of them, like some massive form of energy would come and do that automatically. And this is now for over a week, and I finally though of doing something which I am always ready for and excited for: writing a blog!
Although it is just to motivate me, you may just read it for seeing how people get energy from what they love ðŸ˜‰.
So, let's jot down every possible thing I gotta do in upcoming months:
> CodeKaksha
> Game of Codes( Making Blogs and slight improvements)
> DTU Times: PhP, Laravel, SQL, and more importantly setting up my dev environment and understanding some codebase from top level.
> GSOC: I have selected an organisation for which I have to learn Ruby on Rails. But that's not the point, I just have to  install it locally and understand company's vision. And raise and solve issues.
> DSA: Yeah, all of these go to vain if I don't do this in JEE style. Remember? Doing any random question and solving it for fun, but sometimes this "fun" is not so enjoyable. But still, this subject is not that bad like chemistry which is almost of no practical use for computer science grads.
> CP: And these are the stories, long stories, and all you have to do is to skip the story part, and identify crux of problem and then, boom, just your solution with some modification of a predefined algorithm, or most of the times, code the whole logic. But the thing is, do it as fast as you can. But the positive thing about it is, I am passionate about it. I build a goddamn site on this, so yeah I can say I am passionate.
>React: This is a secondary skill, and most probably not to cover in these 2-4 months but this is on my target list.

Now, Whole of my day is mostly going on in doing minor improvements in GOC, CodeKaksha, Chatting, Random stuff in YouTube, practicing from DSA sheets by youtubers and filling forms and seeking internships.

But I think, what is hindering my motivation is my chatting habit. I am now tired of advising people, flaunting about myself and GOC and Codekaksha. So, what I need to cut is chatting nonsense stuff. 
And I am now hell tired of seeing same avengers scenes from youtube and Kota factory. So, let's bring some change in the usual form of enjoyment: I would do one of my hobbies and I got many: Chess, Cycling, Cartoons, Blogging, and brainstorming about ideas. So, any time I am tired, I would draw some cartoon, write some blog or brainstorm. 

So, DTU Times thing is once for a while thing, and that's pretty easy too. just learn how to run it on local and its done! For GsoC, I have to fix a time. So, let's start our strategy.
I can give 70 hours per week to work, and honestly, 50 hours. 
>CodeKaksha: 14 hours per week
>GOC & DSA: 20 hours per week(10 for theory, 10 for practice)
>GsoC: 14 hrs per week
>DTU Times: 4-6 hours One Time
>CP: 10 hours
So, almost 60 hours, less than 9 hours per day! But as all know, its just theory and practical is always tougher. But a week's table is still manageable.
Now, I am applying this theory also(as I have worked with many).

You still here? Go make your own one. Shoo! 

Comments

Popular posts from this blog

Competitive Prograaming From 1000 rating to 2400+

Okay, so let's talk about some strategies for competitive programming. I was once a gray coder as I was totally new to programming when I entered codeforces. FROM GRAY TO GREEN:     First of all, you need to be good at brute force and implementation. If you are a complete beginner then do 20-30 800-1200 problems and you will b good at solving A level problems in 5-10 minutes. The try to do B in a live contest in 15-30 minutes only. By only this you can shift your rating to 1200 or so. FROM GREEN TO CYAN Now, to increase your speed you just need to practice more A and B level problems. As you are now quite confident of solving A and B level problems you must now try C also which is generally of 1400-1700 rating. This require some special techniques such as prefix sum, or some simple trick methods for reducing time complexity. Now the mistake I did was I tried to learn more advanced data structures such as graphs, trees, KMP algorithm, etc and that wasn't ne...