101–110 of 171 posts
I build an Abstract Syntax Tree (AST) and usually something with a fluent interface that builds a query. I find this helps me understand the nuances of interfaces and inheritance in a given language and I’m generally interested in the problem so I tend to get far enough to really learn something. It also helps to practice breaking a problem into steps as an AST is structured in such a way as to encapsulate distinct b…
AST?
If it's server i usually do something related to the actual project though.
1. Find an interesting project that suits the language/framework and keep the scope very minimal so I can complete it in 2 days (weekend). I can always learn more doing a second or third project. But I find that I can maintain my motivation when I see results and complete a project.
2. Restrict the number of new technologies for the project to maximum two (best if it is one). When there are many new things, I find that it can be exhausting and I give up after just a couple of hours. So for ex: When I initially learned React, I didn't know GraphQL, so even if I see a case where GraphQL might be the best fit, I will use REST API. This way I'm not stuck on all fronts.
To answer the first question, there is no single project I build to learn every language because that becomes boring for me. I try to build different projects every time.
For ex: When learning React, I built a HN reader, Foreign exchange meme reaction, and an app where I can see the time of all my teammates spread across the globe (all completed and live). When learning ReactNative, I built a small Twitter clone (haven't published it).
To Do list apps
What are the big downsides in creating a Todo app every time instead of doing a more suited app for each language? Should I reconsider this strategy?
I build an Abstract Syntax Tree (AST) and usually something with a fluent interface that builds a query. I find this helps me understand the nuances of interfaces and inheritance in a given language and I’m generally interested in the problem so I tend to get far enough to really learn something. It also helps to practice breaking a problem into steps as an AST is structured in such a way as to encapsulate distinct b…
But yeah, 'hacker' exercises are a great way to get acquainted with low level code.
Earlier quoted context omitted.
Is there a tutorial for the boilerplate for setting this up? Where would I even begin as someone who has never built any graphics.
As for nitty gritty graphics, I highly recommend https://pikuma.com . They have free and paid courses, and go into a lot of the in-depth aspects you wouldn't get from using a web framework like I typically do. As for game mechanics, Wikipedia is a surprisingly solid resource. I mean, it's expected that these things are covered, but the depth is amazing. Check out this page for example! https://m.bulbapedia.bulbagarde…