As everyone here, I too consider myself as a slow thinker. Some of the reasons for the same, I believe, are (i) Always trying to get the bigger/entire picture of the problem (ii) Trying to increase the precision of the answer for the problem under question (iii) awareness that there will always be unknown unknowns (iv) trying to cater to exact needs of others (iv) Not giving importance to memory (v) a wandering mind, which wants to catch hold of too many things at the same time.

I think adding a concrete language (most probably C) and a course for OOP to the list might prove useful.

When you say "concrete language (most probably C)" are you referring to using one language throughout each subject?

Not one language per subject. A separate subject to have basics strong. I feel learning C as a subject and getting concepts like pointers right might prove useful while learning datastructures and algorithms. The article assumes learning a language is very easy. But for a self taught programmer its easy to fall into the trap of straightaway going to high level language like dynamically typed languages. It would be more appropriate to learn C followed by datastructures followed by compiler design in that order.

Late reply, but looks like C is covered in the Computer Architecture section. How deep does it go into C? That I don't know.

Agreed.The way I see it is, if Jio monitors your contents and selectively provides higher bandwith for Netflix contents putting others at risk or Netflix selectively providing preferences to Jio subscribers, I think that would go against the spirit of net neutrality. Providing reduced rates for certain subscribers is kind of providing premium membership, which is a way to attract consumers.

You can fix under engineering only when it is under control. Too much of under-engineered code may lead to bloated codebase which quickly becomes unmanageable.

Only thing is that it rarely happens (for many it may never even happen).