Ask HN: What are projects I can implement to learn a new framwework?

My first project in any new language is to make a Yahtzee clone. To date I have done this in JS, PHP, Lua (for the Playstation Portable), C, Objective-C (for both iOS and OS X).

Build a blog, that is straightforward enough and simple to implement in all of those. When you're looking at go, consider gin:

https://gin-gonic.github.io/gin/

Any simple game usually does the trick: snake, Yahtzee, black jack. The rules (requirements) are well defined. The pieces (UI) are well defined. That way you can focus on actually implementing the logic in the language/framework of choice. For websites, pick your favorite restaurant and make it. Borrow the text, pictures, etc. and just focus on the code that creates it and not get off on a rabbit trail doing images in paint.net or making up items.

There is some projects that I usually do to get a feeling of the framework:

- Code snippets/tasks manager. Pure CRUD. If you want to get yourself dirty: add authentication.

- A blog (like SEJeff suggested). If you want to get yourself dirty: try to make it multilingual with SEO.

- Syllabication app. Helps me to find how business logic is best placed into app mindset.

I have to go, but if you need more examples just say! :)

Do something you have need for. It'll help with the motivation.

I always use project Euler for the learning a language, once you pass that stage I usually go for pet projects.

As I understand, the classic thing to implement is a todo list. You have CRUD and then need for some sort of storage solution (whether local storage, or DB backed).

I usually start really small, and add features/refactor as I learn more.

I usually look at each language/framework and see what problem they were designed to solve, and then implement something directly that they were designed for as my first foray. Then I will try something slightly more specific to my own needs. But normally I already have something in mind where I feel that language X will solve it better or framework Y is more suited to this problem. And even when I am just playing almost all the authors have a few examples or use cases they feel their language/framework solves really well so I will take a simple one and implement it.

At least for me, I found this keeps me honest and using the tool the way it was intended versus bending/breaking it for my needs just to say I used it. Then after I mostly understand it I can see how far I can bend it to my needs, when required.

To borrow from an article I read earlier today (http://weblog.raganwald.com/2006/06/my-favourite-interview-q...)... how would you enable two people to play turn based (and/or realtime) monopoly (or chess, or any other game) over the web? This will almost certainly be more complicated on the front-end than most apps you'll need to build, and complicated enough on the back-end to be non-trivial.