This might be my first article about such topics. This might contradict other (self-claiming) authors who say that they can teach you a programming language in a number of days. For example, “Learn ASP.NET in 7 days”, “Learn HTML5 in a matter of 3 days”. Let me point out a few of the problems of this type of teaching and learning for new developers, who might fall for this approach.
Who the victims are
The most victims to this type of approach are the young developers. Inexperienced, rushing to learn new things, express-to-impress type of teens and those with a deadline for themselves, fall into this type of approach very often. Sometimes those who cram the rules, types, structures of the language do so.
![]()
Remembering never helps you out! You need to understand how things work.
Most usually, the teens who are eager to learn something in a very short number of time are victims of this approach. 7 days? 14 days? Seriously? What is it like… A pond's challenge! Programming is something that cannot be fed into the minds of other people; you cannot move a clock in simple harmonic motion and expect the human to become a programmer once you're done hypnotizing and brain washing him. It cannot be taught the way we learned it. It must be taught by lowering our standards to the standard that our student can understand us. Our students come to us to learn. We should educate them, not force them to remember what we said.
Who claims such things
I have no personal hatred towards those who claim such. In fact people who are extraordinary in learning and experimenting claim such things. They learn things in a very fast manner. Authors who write a title to their publication in a way, “Learn {subject} in {x} days!” are them self very quick learners. That is why they expect others to learn the same subject in a very fast manner.
It won't be false to claim that they actually are the very genius of their era. They have a very resilient grip of their subject and field. But not all fingers are of the same size. Are they?
Discussing the downsides of this approach
Now let us discuss, why new programmers should not learn programming or any architecture or a framework using this approach. I would state a few points of mine, you can have your own feelings and opinions and might contradict to mine. But, be logical and learn stuff slowly and by understanding what they are to you!
Not at all a true statement
The first problem that I feel about such content is that they are not at all true. How can someone claim to teach you something with a deadline? I teach programming to a few, some of them learn the concept very quickly. Some take time. Some take much time. For those who take a lot of time, I try to ensure that they at least learn and understand the basic concepts and tend to do something with it. I do not expect them to cram to reach the “x” days limit.
More appropriately, such topics for publications are a marketing stunt. Because they are more direct, targeted by those who want to make more in less time, the author is challenging himself to be able to teach you more in fewer days.
Various psyche levels
Humans do not have similar psyche levels. And you just cannot expect everyone to be similar when it comes to the ability to learn and understand something. It is the responsibility of the instructor to teach his/her student in a way that they can surely learn something and not just waste their own time. I have taught people of nearly every psyche level, from geniuses to average students. Those who were geniuses asked such questions that led me to go deep into my mind to extract a scrap of information that I had locked in my limbo for a decade (not really!). Those who were average students need to pay some more time to learn it, they also tried not to understand the concept and apply it. But just to learn it, to learn it!
I had never been a great instructor. So I have tried giving them a lesson in a way a friend would. Publications claiming to 5, 7 or 30 day's time period don't claim that they would teach programming to those with average mind set. They are of the same period and good use to someone who has the 100% same mental ability as the author had when he was learning the same framework or language.
A book, in any way cannot claim that the readers are expected to benefit from the content. But, claiming something that is not expected or guaranteed should not be used. When an author claims something, he must be able to prove it.
Only good side of this
The only good side of this approach is that the subject is catchy! ;)
Personal views
There are many other points, but I would not want to criticize such content any more. Instead I would share my views to beginners how can they benefit from less in more time.
Practice makes you better!
First of all, I should say that you need to practice what you learn. Practice is something that doesn't make the applicable task easier, it just makes you better!
![]()
You should never think things are getting easier. It is you who have evolved.
What Google might respond to your search as?
![]()
I learned programming in a matter of 2 months. I just learned C# at that time. Not software programming! There was nothing that I knew about creating an efficient software, writing a good API, creating a web application and so on. The more you practice the better you get. The more errors you get, the more you will understand. Sometimes when I go back in time 3 years ago and have a look at my questions, problems that I encountered, I laugh. That doesn't mean things are easy. That means practice has just given me enough understanding of these frameworks that now I can slice and dice them in any way that I want to. It also now has an impact on my social life.
![]()
Now, after learning and practicing. I speak less but qualitative. The quality of my speech is great now. I do not speak gibberish (or that I feel like).
There is no limit to study
I can build good applications in a matter of day or two. But that doesn't mean I should give up learning more and more about such a particular platform or subject. I have a good grip on the .NET Framework, but I believe I should learn more and more.
Every new developer must only focus on the learning part. I remember many good threads where I have participated, ended up with the same conclusion. That you cannot learn anything in a matter of weeks, fortnight, month or even a year. You need at least to consume 5-10 years to learn something. Yes, if you're going to cram through the concept for a term test then good, do it. It might even take 3 days for that.
Focus on something… Put smaller time periods in your learning
But to learn something fully, you need to focus on it in a very better way. Give more and more time to it. Let it settle down. Give your education a short time of more like 30 minutes, 45 minutes regularly. Try something, learn something. You would stumble upon more like a million errors before you can think yourself as a pro beginner! Before you can even enter intermediate level, you will fall into the errors like a million, or billion times.
Do not rush!
There is no need to rush. You can learn something in a very easy, smooth and friendly way. For new developers, it is a very good approach to read articles of other developers, read their code. Reading good content, good articles, good code helps you out to understand how they did. Remember they might be better than you (I don't mean to tease anyone here, sorry if you take my words seriously), so if they did something in one day and you took 3 days. Do not hesitate! It is OK!
Finally. It is you that understands best where you are deficient. The best learning environment is when there is an instructor available for you. Books, articles, blogs do not teach you in a way they can. If you are a beginner never rely on them. If books were everything there would have been no requirement for a school, institution or university. There would have been great great libraries everywhere. You should ask your instructor what to do and how to do it. Your instructor should help you out. He should be able to understand where you lag behind others. He should polish you in a way that you can really get into something.