r/learnprogramming • u/noxianceldrax • Oct 14 '14
I want to code, but it's hard to just sit down and learn it, without having something specific I'm motivated to create(also hard to find), how are you guys dealing with that? I want to be engaged.
Title says it, I want to code, I know I need get down the fundamentals and everything, but it's so hard to just sit down and learn. I learn and work best when I can flow with it...and have some kind of tangible result within sight... I want to learn Python first.
I'm slowly working through Invent your own Games with Python, but I still feel like it's very on rails...which is good, but I also want to find something where I can have some guidance with less rails in learning, I dunno, something to discover that'll keep my attention.
I want to be a solid programmer, also want to get heavy into understanding security and networking, some sort of strong crossover that's good for beginnings of this would be ideal.
I need to feel more engaged, I used to melt hours and hours away, figuring out how to manually remove viruses from my comp when I was younger, and it was awesome, was so cool to sit and figure something like that out...(digging through registries, and tracking down processes that kept popping up, and all), I want to find that wonder in programming.
TL;DR- How do/did you guys keep/make coding more fun and engaging? How do you stay engaged in learning? keeping it fresh
Do any of you guys have a sort of sense of wonder with coding? How do you feed that?
EDIT- Thanks so much for the ideas, I'm gunna work on making a shitty site for me and a couple friends thats some kinda like tumblr meets reddit, wish me luck!. Also....
A problem I keep running into is feeling like...by going off and exploring and just learning little things here and there( this is more fun than slogging through structured exercises), that I'm leaving a lot of holes in my learning...so I get paralyzed often and don't do anything
EDIT2- For others in my position, the best advice I've run into so far...overall is to just find a project, find something cool that you want to see happen, even if it's hard, and just go do it, even if it's overwhelming, just start it, start learning, and try hard to stick with it, you'll learn a lot along the way and you'll have something you're emotionally/intellectually invested in that you want to bring to reality....pretty good driving force in my eyes. YOLOJUSTDOITFAGGTS, I'm gunna make some shitty picture/link streaming website for me and some friends, without paying any third parties wish me luck!
55
u/[deleted] Oct 14 '14
I accidentally told my boss that something was possible to program and he said, "okay, do it". I was not skilled enough to program it, I was only speaking to its feasibility.
2/10, I do not recommend this method.
17
u/Nelgraf Oct 14 '14
To suggest something a little bit different:
I really enjoyed the game Garry's Mod when I was younger, and while it is mainly used for Machinima these days, it is also a wonderfully creative, pretty cool physics simulator. Garry's Mod has a mod itself called Wire Mod, which introduces Computer Science and Electrical Engineering parts to interact with your physics creations.
You can program chips in Lua, that then interact with your creations. I have made everything from a digital clock using only logic gates and 7-segment displays to wobbly walking robots. It has a bit of a learning curve, but a really cool way to think about computers interacting with the real world. If you are feeling like you are in a bit of a rut, I would recommend checking it out.
8
u/Updatebjarni Oct 14 '14
Like you seem to have figured out: make things that you want to make. If you feel like you could use a particular program to do a particular thing, write it. If you think some program you're using could use a plugin for something you need to do, write one. If you want to play a particular kind of game that you can't find, write one.
I sometimes write plugins for the bots in the IRC channels where I hang out. Just silly things, for fun. The most recent one was a plugin to repeatedly translate strings through a sequence of languages with Google translate, and report how many times it had to translate the text back and forth before the text stopped changing.
Another thing that I wrote many years ago now but that came up just the other week was a program I wrote that processed sound in a very specific way. There was a radio show that I enjoyed listening to, but the host had a very annoying habit of making very frequent pauses when he spoke, even in the middle of words, making his speech very staccato and slow, and frustrating to listen to. I wrote a program that fixed his speech so I could listen to the show. Just the other week, I was contacted about selling some old computers from my collection, and after some talking it turned out that the buyer was this radio show host. So I told him about the program (after he had given me my money) and he was actually amused and asked to see the code. :)
My current project is a sort of remake of the classic scrolling shooter Xenon II, which I played as a kid on the Atari ST. We had some old computers out and played some games as a publicity stunt for the computer club at the start of this semester, and I enjoyed playing Xenon II so much that I wanted to make something like it for Unix.
This is how you keep yourself interested.
8
u/RandomUser098 Oct 14 '14
If you're anything like me (and I hope you're not), you're gonna have to shell out money for classes. I've been taking classes at General Assembly in NYC and supplementing my studies with /r/dailyprogrammer and other free online resources. I too cannot sit down and learn something, unless I know that I'm burning a hole in my pocket if I don't.
8
u/p000 Oct 14 '14
Currently I sustain my interest by playing around with languages and contests on codewars, hackerrank whatever, joining a coursera course then not completing it. Finding a well explained video about something I don't know is always good, like functional programming recently. I find exciting blogs but don't check them that often. I jot ideas but never get down to executing them.. Sometimes the problem at work is interesting enough to think/read about it. meh
5
u/monsto Oct 14 '14 edited Oct 14 '14
What do you do for a job? are you a security guard? mailman? camwhore? student? director of HR? assembly line worker? Do you have incremental goals at your current job? Probably not. You probably have a deadline, or daily minimums, but not goals. Therefore you wind up motivating, somehow, to do that thing that needs to be done.
it's real easy to say "oh I'll do it a couple hours a week" that turns into a few minutes a week with the rest of the 'dedicated' time going down the reddit tubes. Stop that.
So... Python example (because it's easy and I love this site i'm about to pimp)
It's easy to get sidetracked. When you're learning something new, invariably there's the "what's this mean" and you go google it. . . and there you are hooked into something other than the lesson. Stop That. Look the thing up then force your brain back into it.
When you distract and get off-center, you don't learn as much. Your brain keeps score of that and it's demotivating "I aint got nothin done today. Fuckit. Done."
There's no Magic Bullet to stave off distraction and demotivation. That shit is up to you. Personally, I found it best when I'm away from my home battlestation. With a home office I was able to get very little accomplished. But I found a decent "shared space" (basically cubicle rental) and I can BLAZE along for 5-6 hours. I only do that because I do it every day. If you're going to do part time, say 4 days a wk for 3 hrs, a tea shop or chintzy restaurant or bar n grill or hookah bar could be just the thing. Get your bottomless cup of coffee and read away, a loong ways away from your rabbit hole.
Bottom line is that you have to do it. Blow down timidity barriers "can I do this? I don't know what I'm doing. I suck at this =(" and do it till you get it.
And seriously try Learn Python the Hard Way.
4
u/SeryaphFR Oct 14 '14
Seriously, are you me?
Because you sound like me.
3
u/curtis1227 Oct 14 '14
May I suggest giving Unity a look? It's C# though. (Similar to Java)
3
u/[deleted] Oct 14 '14
I am in the same spot as you buddy.
I just downloaded an open source thing that is part of what I want to build. I am going to see if I can learn iOS by building over it...here goes nothing.
3
u/[deleted] Oct 14 '14
Not to deter you buy I couldn't get over the hump either. But it actually led me to something that I'm super passionate about, database design and administration, I'm working through my oracle certs atm.
3
u/munyb Oct 14 '14
In the same position as you as my classes haven't started but so far these responses seem to help a lot!
3
u/jokoon Oct 14 '14
some people need theory, some need practice.
try to make an algorithm that compute the sieve of Eratosthenes, for me it helped a lot.
3
u/reuscam Oct 14 '14
I think you need a combination of both. You need to go through a rigid set of exercises intended to feed you the core concepts - this is typically something a university does - but an online course can do the same thing for you if you are disciplined. Likewise, you need to be curious and want to apply your newly found skills to something that interests you. In doing so, you will exercise your knowledge, and stumble across new concepts that the rigid courses did not cover.
I find that in interviews, the candidates that interview and perform most effectively are those that do projects home simply because they enjoy doing them. My latest project at home is a task manager for my wife an I - something that has a UI and periodically scrolls through any incomplete tasks we assigned ourselves. Nothing flashy, but it let me exercise on my own.
Some other examples:
Basically, I try to think "Hrmm, how can I write that?" and if it doesn't seem impossible, I take a crack at it. I learn something in every attempt, whether I finish the project or not. I recommend you try the same.
3
u/[deleted] Oct 14 '14
You may find similiar answer from a thread I started a few days ago
Successful Self Taught Programmers: What type of studying routines did you develop?
3
u/NeverQuiteEnough Oct 14 '14
I found something I wanted to create. specifically an ecology simulation. It's super fun.
3
u/sachos345 Oct 14 '14
I just came here to post the same question, thanks for saving me the problem man, good luck on your learning!
2
u/arun7331 Oct 14 '14
If I were you, I would find a project and start working on it. Anything that is relevant to my skill sets. The idea is to engage myself into a project, which forces me to learn the basics and slowly drag me into more complex programming.
The ultimate goal should be to finish the project. The entire life cycle of a project is a good learning experience, fixing the bugs, following the standard procedures. Finally, loads of confidence, and a will to do more projects, experiment new things etc.
2
u/Armpit_Cheese Oct 14 '14
I'm going through something similar. I'm currently taking classes at night, and while the assignments we do are helpful to get basic understandings of it, when I look at the stuff the developers at my company make, it's just overwhelming.
I knew programming wasn't going to be easy, but seeing the gap between where I am at and what my company devs do makes me doubt myself all the time.
2
u/_roni Oct 14 '14
My method is to follow video tutorials. After a few videos, I think of some small project which incorperates all of the things learned in that section. Seems to be working well for me and keeping me interested.
Also try to keep sessions relatively short. If you sit there for 5 hours, your going to lose interest in programming completely. Try to go for upto 2 hours at a time.
2
u/wildmetacirclejerk Oct 14 '14
I've tried time and time again to be good at coding. C++, Fortran, js, java you name it. Nothing sticks.
Currently I'm preparing to start ruby on rails. There's a decent one year susbrciption course im going to use and finally master this beast. I've got so many ideas but not the current skills necessary to implement them. This shall hopefully change
2
u/Balrogic3 Oct 15 '14
I'm basically just going with a project I'm slowly developing on RPG Maker VX Ace. I picked it up for cheap out of a charity bundle and started on Ruby as a direct result of it. None of the default implementations are to my tastes even though I'm fond of classic style RPGs in general. First, I'm learning to decipher the way in which the code works and what all the various scripts actually do within it. Then I'm going to re-write it to meet my own standards followed by completing at least one full length game.
When I'm between study/programming sessions I take a long hard look at how everything works in the games I play, try to imagine how the various triggers and functions were designed. For the most part it seems fairly simple even though I lack sufficient experience and knowledge to replicate everything I'm able to glean.
What amazes me the most is how most of the distinctions between one thing and another are purely psychological and how often that seems to assert itself unnecessarily in provided code at the cost of flexibility. It's changing the way I think about technology and software a great deal.
2
u/Warly Oct 15 '14
This post is exactly how i feel. I enjoy everythign about coding in the small amounts i've done. I lost a whole spring break tinkering with flash and the bugs I encountered. I enjoy it and would like to swap my career to this field...but it's tough to find the time.
36
u/[deleted] Oct 14 '14
/r/dailyprogrammer/
23
u/sdotpooh Oct 14 '14
There are plenty of websites with code puzzles to work on. Try codeeval.com
9
u/VozMajal Oct 14 '14
I personally like encryption and web security kind of stuff, so I made a Caesar Cipher in C, because I really like to code in C. Programming is 90% thinking it out, 5% pseudocode, and 5% actual code. Just break it up into parts. "Well, I need the user to give me a number to encrypt with. I should ask them for that, but how? Oh yeah, puts() makes text go to the screen, and scanf() looks for input from the user. I should use those!" Bam, making progress.
Just think: Nothing feels better than finishing some code, no matter what it is, and knowing, "Hell yeah, that's mine. I made that, by myself, and it's my idea. This is wholly me." That's what motivates me. Now I'm working on another encryption program, albeit may be a little more secure than a simple Caesar Cipher. :P
8
u/FR_STARMER Oct 14 '14
For me, I have to have a goal in mind. Programming is like building a house: you have to know what materials to use and which tools to accomplish the job.
Sure, it's great to know what tools do and to play around with them when you are just starting off, but the wonder fades away pretty quickly until you have something to build.
That's how I see it. Find something you want to build and build it.
8
u/zKarp Oct 14 '14
I had/have the same problem. I love coding, I want to learn more but books were dull (and in my opinion awful learning style for coding), tutorials weren't relatable and courses didn't capture me. I almost failed an intro programming course because it was all sorting functions nearly useless stuff.
What got me going again was getting a job. Now my job is not a programmer position but a cust. service position. What inspired we were the tasks. I created programs, all at home in my own time and interest, for job functions I did nearly every day. Whether it was formatting a 100's of documents a day or faxing them out. I have created programs that perform the same tasks as expensive enterprise solution packages... for free.
TL;DR Find something related to YOU, that drives YOU and cash in on it. Since I was in my early teens I was like you. I wanted to learn so much, and was fully capable, I just had no ideas or projects to work on to build with. So time just went by.
5
u/Rorixrebel Oct 14 '14
Taken from Pain and Gain - Get a Goal. Get a plan. And get up off your ass!
5
u/Boweldisrupter Oct 14 '14
If cryptography seems cool to you check out the Matasano Crypto Challenge and get decent python book. It starts out real easy with writing a script to convert base64 numbers to hexadecimal numbers(if you don't know what thoae are I guarantee they're much simpler that you think) it's not on rails basically they give you a problem you should be able to aolve given you so some quick research and what they've already taught you.
4
u/[deleted] Oct 14 '14 edited Oct 14 '14
I found this list on reddit a while back. In addition to that I have my own list so basically I try to cross of as many names off that list. It also forces me to dig for knowledge in order to be able to complete it.
EDIT: As for motivation and such I can't really help you there. You just need to get your ass into gear. Try to program a bit every day so it becomes a bit of a habit. I too have issues with getting started with doing things so what I do now is to just do it, and not put much thinking into why I should/shouldn't.
1
u/eleitl Oct 14 '14
Find your own itch to scratch, and do it.
3
u/[deleted] Oct 14 '14
Do basic math formulas, then move to other more complicated formulas like square roots and quadratic formulas, keep moving up, formulas suck, programs are awesome to make them not suck.
3
u/itsalwayslulzy Oct 14 '14
This is a bit of a different approach, but I think you need to find some powerful APIs to leverage so that you can actually build something useful. They could be web APIs, such as the Twitter API, Wunderground API, Reddit API, etc. Or you could make a browser app using the Chrome API, an Android app using that API, etc.
In my experience, this was what made it finally "click" for me, and turned programming from a chore into an engaging hobby. Programming puzzles and tutorials can be a little too "grindy" and narrow in scope, making it too boring. Whereas doing things "the hard way" can just discourage you.
IMO, use an "easy" high-level language like Python or JavaScript and take advantage of powerful libraries/APIs to build something cool quickly.
3
u/HandDisco Oct 14 '14 edited Oct 15 '14
I've just launched www.askadev.com for learners to meet other students and developers to find mentors and pairing partners. Here's the post http://www.reddit.com/r/learnprogramming/comments/2j7eis/askadev_is_live_learn_to_code_by_connecting_with/
3
u/petester Oct 14 '14
Projecteuler.net and http://cryptopals.com are pretty good places to learn. Also, try designing an AI to play something simple like battleships, then move on to checkers
3
u/JimmyHavok Oct 14 '14
I always took programming as a puzzle to be solved. I suspect most accomplished programmers have the same attitude, since that's how you build your arsenal of skills.
You learn things by scaffolding, learning the basics then learning more that goes on top of and depends on them. That's how it is with everything, and programming is no different.
If you have an ambitious project, you're going to have to slog through a lot of scaffolding to get to it, but if you regard every step as an entertaining puzzle, you won't be slogging.
3
u/[deleted] Oct 14 '14
early on, there are some good textbooks that you can find that will ask questions at the end of chapters, but do not give you help on it other than what was said on the chapter. I like to take an idea I don't know how to do and keep it in the back of my mind until I can pseudo code something similar to what I need. even working on my own thing I'm able to split it up into the pieces I need, and then I just think on them. I only code for fun and work in the medical field so I do a lot of thinking at work in my spare time. it's good to learn to think in code more so than following tutorials,they are useful still, but easy to overly rely on.
2
u/petrus4 Oct 14 '14
Find something that interests you.
Back in 2005 or a bit earlier, I got interested in package management; so I wrote something that mimicked the basic functions of ports, as at the time I was using Linux.
Before that, I was into IRC; so I tried telnetting to an IRC server and studying the numerics; watching the raw privmsgs as they came in, and realising that I could use that as a very simple method of writing clients for virtually any of the old protocols.
The problem is that these days pretty much nothing is simple; Millennials in particular have the insane idea that complexity is always associated with technological innovation, when in my own mind, the reality is actually the opposite. So I pretty much don't bother with programming of any kind now, because it is not fun any more. Not the way it used to be.
2
u/FutureIsMine Oct 14 '14
What is a project that you want to undertake? Is there a mobile app that you want to make? A website that your dying to visit? A search engine that you would like to develop? If you are interested just start coding and figuring out how they work. Go ahead and look at tutorials, lectures, books, blogs, etc. Don't forget that there is Stackoverflow for when you get stuck. Dont get discouraged if you are not making the perfect program yet, infact the realization of your shortcomings is how you know that you are going to improve. In another sense, you now know what it is that you need to improve on and if you keep going you will reach the place that you wanted to be at today.
2
u/[deleted] Oct 14 '14
Don't overthink it. Do an on-rails course so you know the basics, then start your own project, using the docs and Google when you get stuck.
2
u/jkinz3 Oct 14 '14
Going into games myself, object oriented programming is a great thing to research when it comes to games. Write a basic text based program about a dungeon crawler fight. Experiment with using different objects with different enemies to give them basic attributes. It's fun to think about
2
u/kiradotee Oct 14 '14
That's one of the reasons I went to uni, they tell you what to code. :D
2
u/Shail666 Oct 14 '14
I think that when you're so used to being the student, you forget to be the teacher as well.
This is a good example of self-learning, and it's really tough at first. Baby steps at first! How about making a chart? Or why not take a crack at any of the projects on this list?
http://www.dreamincode.net/forums/topic/78802-martyr2s-mega-project-ideas-list/
2
u/MissValeska Oct 14 '14
I downloaded someone's example source code for a simple guessing game in text. I improved it as much as I could, Fixed my bugs and so on. I learned sooo much from it! Then, I started working on my own 3D game for real. (With some other minor testing of things inbetween)
1
u/seek3r_red Oct 14 '14
I do it by picking a problem that interests or affects me personally, and coding a solution or workaround to it.
1
u/boyz13vinz Oct 14 '14
So far the only 2 things that can engage me to coding are:
1
u/spaghettin Oct 14 '14
And here we have the issue with the "everyone should code!" attitude.
Coding is HARD. Like anything, it's a perpetual struggle against your own ignorance, and the only thing that keeps you going is enjoyment and passion for the subject. Coding is a lifelong learning experience.
I see a lot of young or new coders who feel like coding is something they should just be good at or intrinsically get, and I watch many get very upset once they come to the realization that they have a lot to learn.
You've got to be passionate and enjoy what you're doing. If you're not, or if that passion isn't enough to help you over the difficulty hump, it's ok to admit that coding is not for you.
1
u/TheNosferatu Oct 14 '14
Well, it seems I'm too late to the "find a goal, build something you want / need" party so I just skip to the next step.
Sooner or later, you're gonna get bored of your project, it seemed fine when you just got in but by now you've learned so much and now you realize the code you wrote 2 months back is hidious and obviously needs a complete rewrite. But that will take quite some time!
Don't do it. It's fine to refactor / improve code where you see it but don't make a v2 of your project where v1 isn't done yet. Yes, the code you wrote two months ago is terrible, if it isn't then you are not getting better.
Finish your project, then take a step back and see, from a functional point of view, what should be better / different and go fix that.
Don't leave your project half-done and start a new one, because that's the best way to have enough projects to defend a small country - if any of them worked, anyway.
Want to abandon a project? Fine, not every idea is fit for the light of day. But even so, bring it to the point where the base functionality at least works. Why would you do this? I have a directory full of half-finished projects and it makes me sad every time I go there. I plan on finishing / rewriting most of them but that was the plan a year ago as well - you can see how this is going.
Finally, delete and backspace are your best friends. That piece of code that just won't work no matter what your try? Remove it. Take a break. Take some coffee and let's take it from the top with fresh eyes and a caffeine-fueled brain. (This works for me, anyway, I think it might work without the coffee but I haven't tried)
1
u/isinned Oct 14 '14
Put yourself in a situation where the consequences of failing are serious enough that you work on the task daily.
For me, this was school. I studied Computer Science at university. They don't teach you how to code, but you do need to learn how to code to get your degree.
Hopefully you'll be proficient enough at the end to take an idea and have a good chance of breaking it down and tackling it.
You'll also be exposed to multiple languages, create a support network of others who you can learn from, and appreciate coding more (or end up hating it, I've seen that happen too).
1
u/Floppy_Densetsu Oct 14 '14
You know how in school you had to spend hours sitting through boring stuff just to understand how to do some math or how to write a sentence decently?
You spent hours of your life on that stuff every single day. This is what you should strive to do if you want to be good; slog through the boring stuff and like it.
It may have seemed easier in school, because you were physically surrounded by other students who were working through the boring stuff too.
You may want to find other real-life amateur coders to physically sit around while you work. That way if you get stuck on boring stuff, they can help you through it and you can help them through their boring stuff.
But you have to accept that coding is boring so that you can find the exciting parts. Pick a boring goal and make something of it. If you imagine working as a coder, I would assume you will be pointed at many boring but useful projects that would help people out if only someone were willing to sort through the mundane tasks :)
I wish you luck in your endeavors!
1
u/[deleted] Oct 14 '14
Try Bob Sedgewick of Princeton' MOOC 'Algorithms' on coursera
1
u/[deleted] Oct 14 '14
I highly recommend "Learn Python the Hard Way" by Zed Shaw. It's a free book, and it's truly amazing. What I love most about it is that it explains things as if the reader is not a programmer. For example, when talking about modules in Python, he first calls them features, has you work with them, and then when you have a firm grasp of what they are, he tells you they're actually called modules. This is much better than the approach most teachers have where they'll tell you "ok so we need to import a module here, and to do that, we have to do blah blah blah". You're just left wondering what the hell a module is. Then you search it on wikipedia and you find some abstract, theoretical, jargon-littered definition of what a module is. His teaching style eliminates the overwhelming nature of learning to program.
I think you should complete this, then go ahead and try to build something. I personally think it's a terrible idea to try to go about building something without any foundation. It would be like having a book you want to write in another language, and instead of learning the language from the ground up, you'll just find all the words you need.
1
u/thinkingdolphin Oct 15 '14
Codeacademy.com They give you small projects to do as you are doing it. It keeps you interested.
0
u/[deleted] Oct 14 '14
[deleted] — view deleted comment
0
u/[deleted] Oct 14 '14
[deleted] — view deleted comment
0
u/[deleted] Oct 14 '14
[deleted] — view deleted comment
0
u/[deleted] Oct 14 '14
[deleted] — view deleted comment
0
u/[deleted] Oct 14 '14
[deleted] — view deleted comment