Still waiting for a code teaching site that actually explains how everything fits together.
What's HTML used for? What's CSS? What's the bigger picture? What's the difference between java and javascript? Why are there so many languages. What are all these terms you are spitting out? Can we get some real world analogies so we can grasp some concepts?
But every single lesson from all these startups starts with type 'this' in or 1+1.
I don't think coding lessons should start with 1+1. It should start what coding is, what the language is, why I am learning it and what I could do with it and most importantly, what is different about it compared to rest of the languages. You got Python, Java, HTML, CSS, Ruby, C+ and the list goes on. I think it'd be very beneficial to have a map, that shows every day stuff that people use and list how it was built. ie: iPhone are built on 'X', Android are built on 'Y', Websites are normally built with 'Z', but you can add 'A', 'B' and 'C' to make it even better etc.
To me, the approach taken by these sites are almost identical. And they're all missing something…
Actually, most of that information is unnecessary to start coding. In fact, it actually works as a barrier to entry. People who don't understand a programming language aren't going to understand the different nuances between Python and Ruby.
Instead, you teach development by having people start coding as soon as possible. You get them playing with the code, manipulating values, and seeing the outcome. Once they see that they're creating something and they enjoy doing it, that's when you explain it to them. Khan Academy has taken this approach and it has proven extremely effective in getting children to start coding.
It's really basic game theory - you don't have to explain the entire backstory or all the controls to get someone playing a game. You drop them in a situation and go "OH SHIT YOU'RE UNDER ATTACK - PRESS X TO ATTACK." You give them one instruction and get them hooked. After that, you can then go through the basic tutorials that explain the menu system and or what numbers mean or how you level up or whatever. But the point is to explain things to them as they need to know them and not before.
The point is to get people coding as quickly as possible. If someone has to read 60 pages of introductory text, they're not going to do it. It's asking for too much up front.
I'm not sure what the research on that methodology looks like, but speaking anecdotally as someone who's teaching themself how to write dynamic websites, I find that methodology to be very unengaging. '1+1=2' and 'Hello world' console input may hook a younger mind, but I need to see a bigger picture to know whether or not this is going to amount to anything I might be interested in. I shouldn't have felt like I was willing myself through CodeAcademy at times. My time as an adult is limited, so it's important that educational products like these forge a framework for my creativity (and therefore interest) as quickly as possible.
Learning piano, Norman Monath's 'How to Play Popular Piano in 10 Easy Lessons' did exactly this, whereas a lot of the material I ran into did things the classical way, which was entirely boring.
I see what you're saying and there are some sites that do a pretty decent job of what you're saying. For example, Opera has some amazing documents on their site. The much maligned w3schools even does a pretty decent job of showing how everything fits together (in the context of web development).
The problem that I see with your approach is that it is really hard to explain certain concepts to people without any experience. For example, if I wanted to explain the difference between Java and Python, I would likely have to get into the difference between static and dynamic typing. I can't think of a way to explain a type system to someone who can't write a basic program.
Another concern I have is that too comprehensive a resource could actually teach bad habits. If I would have learned from one source, I wouldn't have learned how to debug via Google. I can't tell you how many times knowing how to answer questions with a search engine has saved me!
Great comment though - I bet the developers love reading feedback like this!!
You know, the problem is you are smart and you are not aware of how people are approaching computer programming topics. IMHO, sorta like a startup pitch, if you can't explain the difference (to a beginner) between two languages in less than 4 sentences, you probably lost them.
There's really no need to explain the differences in languages to a beginner. When you're teaching someone to code, you're not teaching them a language. You're teaching them (or should be teaching them) concepts that they can take to any language they need. You teach them logic, flows, etc - how to think in terms of solving a problem through programming.
On top of this, once the coding starts, too many languages focus on command / effect (note: not cause / effect). This is arguably fine for basic looping and data structures.
The problem is I see this knowledge break when 1) it is applied to a more difficult problem that 2) is outside of the scope of the provided loop.
Spending time understanding the conceptual elements (when, where, why) before the how doesn't give immediate results, but it saves many headaches down the road and makes future tools / languages much easier to learn.
I agree with this. I think some attention needs to be paid into teaching people how to set up their environment outside of the browser.
I mean it doesn't sound too good if you say, 'oh I've learned to use Python' and someone asks you to show them & you have to show them inside of the learnstreet tutorial as you don't know any other way.
I do think it's great people are investing time and effort into this area but it just needs some context so that people can actually walk away with skills from it.
You should change your Github OAuth permissions. I'm never giving you access to private repos - and would only give you access to public repos if you were creating a repo for me to do the Code Garage stuff (it isn't clear if you do that or not).
I'm happy to auth with Github if you just request my public profile.
We’ve built a site where you can learn Python, Ruby, and JavaScript in a fun, engaging and interactive way. How is LearnStreet different from other learn-to-code sites you ask?
UI/UX: A key aspect of LearnStreet’s courses is its distinct UI/UX. In order to see this, simply sign up!
Multi-modal: Our courses are designed for beginners, and we have multiple ways to help you learn, including live chat, Twitter, Q&A, hints, videos and background material. If you don’t know which language you want to pick up, check out our teaser videos in the Courses page! http://www.learnstreet.com/lessons/languages/javascript
Code Garage: If you already know how to code, check out Code Garage where you can try your hand at cool coding projects like building a Mastermind game or a Sudoku Solver. http://www.learnstreet.com/cg/simple/projects/javascript
Dev Tool: We’ve culled the web to provide some key resources beyond the core programming language that will help you gain a better understanding of what it takes to become a competent coder. http://www.learnstreet.com/dev_tools/
We just launched about a week ago and would love to get your feedback. We are looking for expert coders to help build out our other courses so check out the Contribute section on our site as well.
This looks great guys! I especially like the tutorial flow.
Some criticism:
You should show JS syntax errors instead just showing a generic error message. I understand you don't want to scare newbies away with compiler errors, but your solution just makes debugging more difficult.
You should show syntax errors, but translate the default JS error messages into something friendlier. Codecademy does this for their intro lessons.
That Heroku video you link to on the Dev Tools page is about 4 years old, and is demoing a version of the product that no longer exists (their attempt at an online IDE of sorts).
I don't understand why we cant skip around the lessons in the python tutorial. I don't need to start at lesson 1; i want to skip around to different lessons.
I get it. It's just that I'm not a beginning programmer. I mean, unless the site is only for novices with zero programming skill, you're requiring all intermediate programmers to relearn stuff they've already mastered.
Also, I wanted to browse around the lessons in order to evaluate the quality of the site so that I could decide whether to recommend the site to non-programmer friends.
That should have been the first thing you said. :)
But such tutorials are obviously for rank beginners, experienced programmers don't use these kinds of sites. Unless it's a dramatic jump, like from COBOL to Haskell, to learn a new language they go straight to the language's documentation:
Disclaimer: I'm a teacher at Dev Bootcamp (http://devbootcamp.com). Everything I say comes from love -- if I didn't care about this deeply I wouldn't bother to remark in the first place. :)
Very nice! We can always use more absolute-beginner tutorials in the world.
Just started the Ruby tutorial:
"Great! So what just happened here? To begin with, let's define what you typed 2 + 2 as instructions. The ruby console reads your typed instructions, interprets it, and then acts on the instructions the way you gave it. This step is called evaluation. Instruction when complete are called an expression. If the instructions you have typed are incomplete (for example, if you typed 2 + and hit enter), this console will show an error message. The instruction you typed, 2 + 2 is an expression. It is important to remember that evaluation of an expression always returns a value. This value is what is shown as result on the console. In this case, 4 was the result of the evaluation."
If someone honestly knows nothing about coding, you've probably just lost them right there. Questions a beginner would ask:
* What is a "ruby console?"
* What instructions? I typed "2+2."
* What does "interprets" mean?
* How can instructions be complete? Were they ever incomplete? How do I know when they're complete?
* "Returns?" "Value?" "Result?"
In a few sentences, with jargon highlighted:
I type instructions into a console which turn into expressions when they're complete. The consoleevaluates the expression and returns a value, which is shown as a result on the console.
A beginning programmer won't have the mental models necessary to make sense any of that. It's context-free. Most of those words have no prior associations, and those that do will lead them astray. Metaphor is your friend.
I second this. For anyone trying to teach computers (and anything else), this will save you from repeating all the mistakes that all the other computer programming education startups are making/will make in the future.
Again, just to be clear, this book is really really really really important.
Mindstorms? I did a quick google and there are assorted books with that title (after you filer out "lego"). None seemed to be relevant to this discussion.
Looks great, really nice. Minor point, I have a feeling (and can't find evidence to the contrary) that Twitter's stack is actually Java, not Ruby [1]. They may have changed back since then, but I can't find anything about it. Maybe I'm totally off though, and other parts of their stack are rails. I don't know - I'm not really a webdev guy...
[EDIT] - any reason for the downvote? I'm totally fine with being wrong, or have I just completely missed something?
The reason I brought it up was because when you select Ruby, one of the motivational messages opens with, "Twitter uses Ruby to power 400M incredible tweets every day."
Twitter runs a whole range of different technologies, as you can see from their Github page [1]. Much of their performance-sensitive code is Scala, but they also run Python, Ruby, C, and Javascript tools.
Their front-end, however, remains Ruby. The link you posted is just about search infrastructure.
Although these types of sites (Codecademy, etc) are great and teach absolute beginners all the basics of programming, they've left me lost as to how to continue developing my skill set. I've hit a wall for some time and am stuck in this strange better-than-a-beginner-but-still-terribly-amateur middleground where the resources I keep coming across are either tailored for fresh beginners or more advanced programmers.
Does anyone have any suggestions or good resources that are tailored to my level?
Everyone is different. Speaking for myself, I never found books or tutorials useful. My mind simply balks at the prospect of doing exercises for the sake of it.
Instead what worked really well for me is to find a practical problem that I wanted to solve (maybe with the goal of making money from it). It turns out that just about any interesting project that you dream up for yourself will have aspects that are outside of your current knowledge/ability. Then as soon as you hit these parts start looking for reference materials, documentation or tutorials specifically related to this problem. Before you know it you're learning new stuff.
And the upshot of this approach is, that if you stick with it you may end up with a functional product at the end, which you can sell.
Also read other people's code. I find it really humbling to read well crafted code. It also motivates me to continue refining my own code.
And I'm the exact opposite. I love exercises. You should find what works for you and stick with it until it doesn't work for you! For a while, I would read a section out of a programming book, think to myself "Could I explain this better?", and if I could, I'd write an article. If I came across an exercise in a book, I'd think to myself "What if these requirements had to be met? What if this needs to be read in from a keyboard? A database?", and I'd expand the exercise into a full fledged project. Just do your best to keep yourself interested. Find a reason to stay excited.
I'm not quite at your point yet, but I'm getting close. I've taken a class in Java, built some simple programs like an address book etc. Then I journeyed into python, ruby etc. Nothing really struck a chord with me until python.
In any case, I'm still plugging away, but I have learned about doing basic math, variables, etc etc quite a lot. I'll keep going but, in the end, what I want to make is a fully functioning and actually USEFUL web app that LOOKS and FEELS professional.
So many of these online resource just take you half way. They try to be SO user friendly and approachable, but in doing so the tutorials are filled with too much useless fluff. "We are different because we make learning FUN!"
Get a copy of Structure and Interpretation of Computer Programs [1] and read it beginning to end.
It won't teach you how to use any frameworks. It won't teach you how to write a particular language (well, you'll learn a bit of Scheme, but that's a by-product). Instead, it will teach you to think computationally, which is a far more valuable skill.
I can't emphasise enough how much that book improved my programming. Everyone should read it. If you read that book beginning to end and do all the exercises, I don't think it's an exaggeration to say that you will instantly be in the top 1-10% of programmers worldwide.
I'm not a Rails dev, and I admittedly never made it all the way through this book (more out of lack of time than lack of interest, though), but I was very impressed with the first few chapters of
http://ruby.railstutorial.org/ruby-on-rails-tutorial-book
It manages to cover material fairly quickly and talk you through getting a working webapp up and running (and deployed!) while still taking the time to explain the little things that a more experienced dev might find obvious.
If you want to go out and try some more mathematical approach use the exercises on http://projecteuler.net/ to improve a little on the math side
If you want to understand what the computers does and on what level you just need to start reading books or going to courses
Books about algorithms and data structures (Cormen et al)
Any book introductory to Operating Systems is a must (Tanenbaum or Silberschatz operating systems)
This. I learned to program just by reading a book to get basic syntax and then doing as many Project Euler problems as I could. I got to about 60 and by that point I was ready to try some cool things like making my first app.
This might be an obvious suggestion, but have you tried building something useful? I have found myself in that strange in between space before when learning a new language, and by starting to build something I am able to quickly move past that middle ground.
I like it, I agree with the GH comment, I used twitter,
your tutorial is great, though a bit long, didn't wait till the end. I would add a "skip the basics" option for people who already know adding numbers. but besides that looks great, but how are you different from all the others? (See partial list here http://eranmedan.com/post/22359967135/codeschools)
If you are looking for a new approach in learning how to code, check out CodeHS. While LearnStreet is an amazing tool, and another great way to be introduced to programming, the site immediately feels very similar to Codecademy. A responsive console is very cool, but I don't think it is the best way to connect with absolute beginners.
Our philosophy is that the key to teaching beginners is on providing help from real people, and that is what we are doing at CodeHS. Would be grateful for any feedback from the HN community.
LearnStreet is a great introduction to the world of coding. They have a bunch of really awesome Code Garage projects, and I especially like making the games, and Conway's Game of Life. Their teaching methods are very welcoming to someone who hasn't been exposed to this stuff yet, and I recommend anyone who is even remotely interested in learning how to code to give it a try, you won't regret it.
LearnStreet coming out with a bold statement, but from a quick review of the site, they are offering something different. This is going to be a big market for the service that cracks the code...pun intended.
I can't play around with code after the lesson is over. As a UX analyst, this bothers me. The interpreter shouldn't just shut down after the lesson is complete.
the indentation the code editor shows does not always reflect the actual indentation of the code. so i had to c+paste it into another window and then back again to get the code to run...
What's HTML used for? What's CSS? What's the bigger picture? What's the difference between java and javascript? Why are there so many languages. What are all these terms you are spitting out? Can we get some real world analogies so we can grasp some concepts?
But every single lesson from all these startups starts with type 'this' in or 1+1.
I don't think coding lessons should start with 1+1. It should start what coding is, what the language is, why I am learning it and what I could do with it and most importantly, what is different about it compared to rest of the languages. You got Python, Java, HTML, CSS, Ruby, C+ and the list goes on. I think it'd be very beneficial to have a map, that shows every day stuff that people use and list how it was built. ie: iPhone are built on 'X', Android are built on 'Y', Websites are normally built with 'Z', but you can add 'A', 'B' and 'C' to make it even better etc.
To me, the approach taken by these sites are almost identical. And they're all missing something…