Is it possible to be able to programming in 1 month?

Not sure where you got that from. You don't need college, you need to *work* on building your skills up over time.

Can you read sheet music? If not, then they are more advanced and capable than you. Also, apple to oranges my friend.

Congrats! You're part of the other 49.9%!

Learning "programming" isn't the same as knowing how to effectively program. Syntax is the very least of your worries as a new programmer. That's the very easiest part of our job. Knowing how to solve complex issues and having prior experience with building fast, maintainable, and modular code is in an entirely different universe.

Sorry if I come off as rude, but perhaps it's partly because I get frustrated by everyone calling the job easy. If it's easy, you're probably doing something wrong.

 

I'm almost completely self-taught. The portion that wasn't self-taught was a short stint in a community college. I stopped attending because of finances and the fact that I knew more than at least one instructor.

It wasn't an easy process to reach that point though and I am now quite a bit beyond it. I still don't feel like I know anywhere near enough and I've been at it since I was 12 (I'm now 32). The differences between code I wrote after a month of learning, code I wrote a decade ago in college, and code I write now is very noticeable.

I've always felt like IQ tests are meaningless. A quick search on the Internet seems to confirm that I am not the only one with this viewpoint. Either way having a higher IQ doesn't mean that month will suddenly be the equivalent of years of experience.

 

They're useless. They're just tests for entry to MENSA. I've seen people bragging about their high scores, but unable to actually *do smart things*. It seems many geniuses have serious tunnel vision.

You only need two things for programming: A pulse and the right sort of laziness. If you stop everything else to spend a week on a tool that saves you hours a day for years, that's the right sort, and you learn when it is the time to work on such shortcuts only by doing

 

Da truth.

Of course, when you become a true master, you will then discover a way to negate the entire need for tool you just spent a week on a few short days after completing it. :: slaps forehead ::

 

On second thought, even a pulse is optional if you're a heartless cyborg.

 

Huh? It is.

Spoiler

After 5 years
...

Spoiler

Well, to be honest, your average programmer copy pastes, so it is easy for them after just one month

 

IIRC there were studies backing opinion that IQ is useless. Basically, there's more than one kind of intelligence, IQ - at best - measures only one kind of it, and most likely just measures person's ability to take IQ test.

 

You know you're smart when you don't expect to be competent in programming within your first month.

Just pull apart examples and immerse yourself in it, or keep chasing books. The internet is pretty much all you require to become competent.

 

Geez..

This is default expected skill level for properly trained guitar player with 5..7+ years of training:

Here's some piano examples:

Here's expected proficiency level for adult player:

Here's "skilled" (meaning highly technical for his age) level for a kid:

Now roughly translate that to programming, and you'll get the picture.

 

So, Someone assume that my book title is "Learn how to program in 1 month" Well, if you read one book for one year then you're the worst reader after all.

I should change title from 1 month to 12 day because it's not take that long to read a book while practicing in the same time.

In one year I could read up to 4 book while applying all my technique at the same time.
I'm lack of something and you also lack of something that your answer is misleading to something else and keep saying that "You won't be programmable in one month."

You have misconception about the word "devote in" and "Casually".
You even don't think about Motivation which is more important than anything else.
"A new wave push the old wave."
Doesn't mean you've been here for century making you stronger than the new wave.

Sorry, if you don't understand the above sentence. I would take time to understand more about programming more than to spend it on Grammar class.

 

I'm bored, I'll bite...

You have been playing guitar for 9 months and you can 'shred', are you better than you were after playing for 1 month, for 1 week, for 1 day? Gee its almost like your experience has made you better.

Reading music and understanding music theory are useful skills which make it easier for you to do certain things in music. Lets imagine you are a virtuoso who can play any piece of music after one hearing, you walk in to play a piece of music with a group of friends. In order for you to play the 15 minute piece of music you have to hear someone else play it, so what takes your music reading friends a few seconds (put a page on their music stand), takes you at best 15 minutes (and even then you rely on someone else reading the music, or having a recording). At least in some musical situations you are at a significant disadvantage and have a negative impact on the team (band).

Lets imagine you are 'shredding' with a band and you are trying to explain to the bass player why their walking base line is not right for the chords you are playing. If you have no shared vocabulary (i.e. music theory), then you have to basically rely on saying "thats the wrong note there", "that note you just played doesn't fit", it could take minutes, hours or even days to iron this out. With a shared vocabulary you might be able to say something as simple as "I'm using a harmonic minor scale, so the 2 needs to be a minor7b5". In one phrase everything is sorted.

There are parallels in programming. Being able to program is more than being able to write efficient algorithms. Its being able to talk about code. Its being able to understand why one design pattern might better than another even though the other is faster. Its being able to remember the undocumented caveats of a hundred APIs because you tried to do something before and had to dig deep in to the internals to realise the API has a bug (which is surely called a feature).

In the end whats the point of asking a question if you think you already know the answer?

 

Interesting read regarding learning to code and the needed time frame : http://norvig.com/21-days.html

 

What's your point anyway?

You wanted advice, you've been given it.
One month will give you some very basic knowledge, but it won't give you enough skill to work on anything remotely complicated.Even with C# being simpler language. That's just how it is.

 

But programming is not playing instrument. Play guitar need me to break to build calluses. So even if I try to learn it, I can't I need break because my finger is burning. It's not the same as learn to program.

The advice is not clear enough and my gut tell me that this is not the advice that I'm asking for.

 

My gut tells me if you were serious you would have been practicing instead of asking pointless questions on a forum

 

There are numerous problems that can appear from using a keyboard and mouse repeatedly. One of them is linked below.

https://en.wikipedia.org/wiki/Carpal_tunnel_syndrome

 

So you're asking a question, yet only accepting a predetermined response? Hmm, seems to be a case of ultracrepidarianism.

Sorry, but it seems you have the Dunning–Kruger effect in a topic you started a couple days ago.

 

Or alternatively he wasn't asking a question but rather making a statement and wanting everyone to agree with him.

 

Reminds me of "I'll make a great game in one week despite not having any experience!".

 

Knowing the syntax of programming is the equivalent of knowing the proper sentence structure of a foreign language. You could probably learn all the intricacies of japanese sentence structure, levels of politeness, etc in a month, but that doesn't mean you can speak japanese.

I know all about vertices, edges, faces, scaling, rotating, translating, subdividing, smooting, etc, but a 3d modeler I am not, because I don't think like an artist. I'm trying, and I am gaining experience, but no one in their right mind would pay me for my "art". They do pay me for my programming however. I read about 10 books a year on programming in my teens, it didn't make me a programmer. I got my first job as a programmer at 21 years old, I was incompetent, but a company was willing to give me a chance. 16 years later I'm an expert, and all that expertise has shown how much more I need to learn on a daily basis.

 

Why all the long answers... no.

 

@Rodolfo Rubens @GTHell Sure you can. Doesn't mean that you won't be coding yourself into trouble more often than not. Though I expect everyone to have a different answer. The OP didn't specify what they meant by learning to program. Simple apps with good coding standards absolutely, being able to design medium/complex systems that were highly testable, highly understandable and done with small amounts of code probably not.

 

I didn't say that I want you to agree with me.
Look at your answer and other people answer yourself.
Keep making more assumption. Your answer will never help anyone. especially like this:

You should know that I'm learning now. I'm learning from you guy and yet you reply me back with a pointless view of yours.

Only jpthek give me a good advice and answer.

Done

 

You got the taste of community? Now I recommend you to ignore everything and learn instead. We will seen it in one month.
Edit- This thread reminds me the "noon to pro" thread of @iamthwee

 

Rephrasing:

In my whole life I have not known or heard of anyone on that planet who has learned programming to a professional level in one month. The chances of you being exception are low.

Based on my experience and information I saw from other people it appears that the most important component of learning to program is constant PRACTICE which is occasionally supported by reading books to fill gaps in knowledge.

The study requires about 1..2 years of practice at least (for simpler language) and up to 5..7 years for more complex languages. College and special educations are not necessary, you can be self-taught.

-----

Most people have no reason to care about what you're using for learning programming and how. That's your problem not theirs. You asked the question, you got an answer. Do whatever you want with that information.

 

I didn't say professional in one month.
My point is can I make a game after finish a book. And look at all those answer.

 

Yes.
But that game will be either "snake" or "tetris".

And unless your book also covers unity, after finishing the book you'll have to waste few more weeks learning unity.

 

Then you should've asked this instead of an extremely ambiguous question. Yes, you can make an extremely simple game after reading a book. It'll come with some difficulty, but you should be able to make Tetris or Space Invaders.

 

Not really. I mean, you're going to be able to regurgitate what you saw in that one book, but you're not going to understand it that well. The problem is that making a game isn't just programming. It is a bit too much to explain in one little thread reply, but suffice to say it's a big area to study and you can spend years learning little things and improving and practicing before you're really able to put on your big boy pants and just start solving problems yourself. I don't mean professional, that just means getting paid to do something... I mean, to be good enough to just imagine something and then make it happen, it takes a lot more knowledge than it seems like it does. It's sort of like building anything else, you might know what you want... but if you start, you'll quickly realize that there's a lot more pieces and parts than you anticipated and if there's no instructions to follow, you're on your own.

Give yourself 2 years of no judgement if you start today before you can use enough tools and parts well enough to make cool stuff.

 

The book title is Learning C# with unity 3d so.... I already made a fps mouse movement and make a loop of cube in my first game.

I also don't see why I need to be a rush.
I just feeling like I want to success my life under 25 yr old.

 

Just start, pace yourself (don't get frustrated and quit, or take long breaks from coding) so it is a gradual process and you can get better. No guarantee you will master it before 25 though.

 

What do you define as successful and how old are you now?

 

Look, instead of trying to "prove" something to someone, just start coding, you'll learn more.

As for being "successful", depending on definitions, chances might be quite low.

So just find something you like doing and stick with it. At least that's one way to do it.

 

Success is when you feel that you did something right and you feel right. Between, I'm 18-19 years old.

I will.

Look like I'm going to go with 2.5d hack and slash game because I want to make a good animation character rather than good graphic game.

 

Just checking. Sometimes you get people who want to make it rich and are nearly at the age.

 

Will you help me through this journey?

 

Of course.

 

That's an interesting definition that you define success at a technical skill purely in terms of your emotions.
So if you become good enough at programming and game development to make 100 billion dollars in game sales, but for whatever reason it still doesn't feel right, you would consider yourself a failure at programming?

 

He's defining success as finding fulfillment. It's about the same as those of us who do game development as a hobby.

 

Wow this comes up often. Thankfully there are loads of highly functioning unity addicts who have discussed everything from learning theory to the state of the industry to answer it but this discussion still comes up and always puts me in mind of those dreadful SAM's books lol.



So yeah, you should be rocking in 24 hours or you're behind the curve. Don't forget your copy of 5 minute abs and how to make $10 000 a day working from home.

When people say that you should just about be able to code tetris, that's assuming a tetris example in your book(s). I mean is this 3D tetris, 2D tetris or something else entirely? - this decision can have a profound impact on how you design which could change the process considerably and then you might need different book...

Just considering guitar playing and video game creation. My son and I play guitar and its great fun. Sometimes we're on form and shred but mostly we chill and learn covers together. That said none of them are going to make it onto an album, just licensing covers is more pain than it's worth. In terms of albums, cover artwork, recording equipment, recording space and "where the hell are we going to find a drummer at this hour" are factors. And that's an indie production without producers, songwriters, sound engineers, studio time...

Video game creation is a combination of a dozen different disciplines, programming is one.

And that's the rub, being able to play guitar is not quite the same as being able to write and record, market and sell an album.

Still if anyone here was prepared to accept defeat then, well, we wouldn't be here, lol.

 

I got my first job by reading Sam's teach yourself delphi in 21 days to prepare for my interview. I already knew several languages though.

 

You weren't trying to become a programmer though. You already were a programmer and simply needed to pick up another language. That's quite a big difference and for that purpose those books may be adequate.

 

I also started with books very similar to that one.

To note, the "24 hours" are spread over 24 days, and if you do all of the exercises listed it's going to take significantly longer than that. It's sneaky marketing to make it sound like you'll be up to speed in a day. You won't.

That said, I still found at least one of those books useful as a starting point as a teenager. I also remember another being kind of rubbish. So all in all I suspect it comes down to the author more than it does down to the brand or franchise.

 

Maybe, but to be able to do things smoothly without getting an intense headache requires more than a month.

 

IQ is pattern recognition. At the right levels IQ is invaluable but too low and too high can be crippling.

 

You can learn the C# syntax in 1 week - you can spend your entire life coding and still learn it.

 

No.

Programming is not about typing a few lines it is about problem solving. After 20 years of programming I still learn new things every day.

 

So basicly after 30years of programming i can safely say, within one month you will at least know if u r cut out for it or not. If you keep waking up thinking of coding then its for you. Take ur time pick a project(s) and try and make it and NicBischoff is 100% right its problem solving that makes a programmer not coding. So pick a problem and try and solve it via code in 5 diferent ways then repeat with new problem and just keep going. If you dont dream of problem solving in your sleep then expect it to take longer . Enjoy the ride

 

I'm completely self taught, and I've been programming now for about 3 years. I went straight into C++ doing image processing for a machine vision project I got offered by someone I knew, after graduating in an unrelated field. It wasn't too hard to pick up, but even though I lived and breathed programming it still took me a year to finish the project satisfactorily.

IMO there are a few things that take longer than others to learn. One of them is project architecture. To plan out a big project, decide all the classes and the way each class interacts with the others, to set out all the little tasks and fallbacks in such a way that it feels easy to hold the map of functionality in your head as you work, this ability takes some time to develop.

Another is the ability to take an abstract concept and translate it into programming. Sometimes you know the syntax, you know how to approach common programming tasks, but then you have a great idea to solve some issue you've got, and although you know what you want to do intuitively the underlying logic of it is a bit elusive. The first time I programmed a behaviour tree I had this problem. I understood intuitively the tree but how did I go about setting it up in code? Often a concept in the abstract has a certain anatomy but translating it to programming gives it an entirely different one.

Another thing that takes time is the ability to dive into other people's code. This is because they might have approached learning in a different way, with different books and teachers who had a different idea of what the 'best way' was. Sometimes code for the same task looks so utterly different it could have been written in a different language. It takes time to become accustomed to knowing where to look for the important bits and how to orient yourself in other people's code.

IMO a month is good enough to learn some basic stuff, but don't expect to be able to do great things until you've spent quite some time, and always realize that you are only as good as the last project you finished properly, there is always another project that comes along and challenges you to learn stuff you never knew that you didn't know

 

Why is everyone young in such a hurry, and old people like to take their time?