loading...

re: Where and how to become a self-taught designer/developer✍(and many other areas) VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Most of my skills/experience come from informal channels/projects/tutorials. I find courses and school boring, and i cannot concentrate during lec...
 

Hello Sebastian, thank you for your comment.

I think I don't really understand your point, I posted in this article literally a list of informal channels, projects, tutorials and so on that you can perfectly find online, as an extra.

Actually there are a lot of places, like Udemy and Doméstika, where courses are literally focused about only building a project for your portfolio. Courses are not all about learning the skill, though, but also about building something with it.

Also a lot of these resources I posted are totally free... I don't really know what you mean, but thank you for reading and commenting.

 

Sorry, i might have compressed my comment too much.. -.-'

My intention was to add that courses/school is not the only way to do self tutoring.

I was using my self as an example.

I’ll rephrase:

In my experience interest based projects that do not follow a recipe usually gives better results.

The reasoning being you are forced to learn how to research problems and the memory is retained better, in my experience.

If it came off as a jab on the article, then I am sorry, it’s a great list, and the notes mighty useful! :)

Thank you for your sincere words again, Sebastian!

In my experience I'm not able to create for example, any project by just reading the documentation (as a lot of documentation is poorly explained and lack in useful examples), so I often explore many courses and create my own projects after my doubts were clear and answered.

I agree that problem-searching by yourself will teach you a lot, but I've seen myself googling through responses that weren't useful or were outdated and I think that's a problem when trying to do something from scratch.

Although I found out that sometimes it is better to first understand, study, and then do, because the 'but it works!' doesn't mean always that it works correctly...

Thank you again for sharing your experience!

I concur, these are problems i have faced as well. :)

In regards to bad documentation, a good tip is to learn how to dive into the source for answers.

It seems daunting at first, but after a few dives it becomes more manageable, the quicker one learns this habit the better, as it lessons your reliance on explanations prepared. On top of that it teaches you how other people write code.

Sometimes, the problem of documentation. It is cumbersome to find her. The solution is Zeal, DevDocs, Dash o Velocity.. You can even include this within your editor such as in Visual Studio Code 🙈

code of conduct - report abuse