Hacker News Reader

Comment by ErrantX | Hacker News Reader

I tend to agree with the sentiment here; I like to play around with new ideas/stuff/software/architecture, and constantly look for way to make use of it day-to-day.

But if I've decided to take on a new project it's best to default to my usual stack (PHP (Kohana), MySQL Nginx) and rattle out the basics. It makes a lot of sense to solve a "hard problem" in an environment that is second nature to you; too many projects flounder because as well as the project you're also dealing with a new architecture.

(this is why I always dislike this idea of using a project to learn an language... it never works out)

Actually, as an example of this, I've been working on a new project at work recently which uses PHP/MySQL - but I've been looking into packaging it as a VM appliance, and the considerations/work related to that has put me about a week behind getting the actual project done.

View on HN

I tend to agree with you, but at the same time I find that tutorials and even side projects often don't move past the fairly basic usage of a language or framework. So even when I think I have learned something well, I end up having to work through a lot of unforeseen issues while working on a real project that end up being more time consuming than learning the basics. So in some ways I feel that the only way to really learn a new language or framework is to use it on a real project, because that's the only time the real challenges are going to present themselves.

I could be way off though, maybe I just need way more ambitious side projects.

>(this is why I always dislike this idea of using a project to learn an language... it never works out)

How than do you learn a language?

I learn with pet projects, i.e. stuff that doesn't have anything to do with deadlines or customers.

This.

For most of my hobby projects, learning a new language is the main goal.

Small tasks, the tutorials. All sorts of ways.

But if you're learning Ruby, writing a Rails app is not necessarily a good way to start. And if you are learning Rails writing a full on project as you're introduction is going to flounder.

It depends - Rails has so many conventions used (magic behavior) that, while useful, you have to learn them all and even how to override that behavior, before being able to tackle anything else other than simple blogging software; although the learning experience is enjoyable.

On the other hand Django is an (arguably) thin layer on top of Python. You can start from the URLs specifications and how to construct a simple HttpResponse object. And that's all you need to know and how tutorials teach it -- for everything else you can rely on your previously learned skills, while learning shortcuts on the way.

For another perspective -- Rails learning is top-down, while Django is bottom-up.

Yeah, I definitely learned way more about Ruby when I used it to automate a set of tasks (like my build/push process) and writing something minor like a twitter bot or a text parser.

Using Rails on a larger project is good as far as learning a framework, but to get into the language and get into the cool/weirder stuff I've found small projects do the trick.

Reply on news.ycombinator.com