livialima

joined 1 year ago
MODERATOR OF
[–] livialima@programming.dev 1 points 4 months ago

We're working to make this possible. If you want to help, you can sponsor us on GitHub or just donate. Any contribution gets us close to make it happen.

[–] livialima@programming.dev 1 points 4 months ago

Oracle is mentioned, just not recommended over AWS or Azure, for example.

[–] livialima@programming.dev 1 points 6 months ago

The general curriculum is basically the same, but each month we try to fix any typos/errors and add any interesting extra to make each lesson more engaging.

[–] livialima@programming.dev 6 points 7 months ago (1 children)

Thanks! I'm glad you liked it. It was more of a way to walk away from Reddit, really. Some people asked for the challenge to be on Lemmy, I just listened to them.

[–] livialima@programming.dev 2 points 8 months ago

Yep, but since VirtualBox can be used in any guest OS and a lot of people come here still using Windows, I sort of simplified the tutorial by just focusing on it so far. I want to expand the "doing things locally" in the future and I accept suggestions on our GitHub.

[–] livialima@programming.dev 2 points 8 months ago (1 children)

Anki is awesome but the best way to memorize commands is to just use them. After you are finished with the challenge you may want to consider practicing with real world scenarios at https://sadservers.com/

[–] livialima@programming.dev 1 points 8 months ago

In a production environment? Not really, there are better ways to do it. But it's a good beginner exercise.

[–] livialima@programming.dev 1 points 8 months ago

Oracle is mentioned alongside AWS and Azure free tiers on the other Day 0 article.

[–] livialima@programming.dev 1 points 8 months ago

Oh yeah, it slows things down, for sure. But if you never used anything like vim before, that slow pace can benefit the learning experience (at least that happened to me when I started). Bottom line is: vim is a lot. Be patient and it will get easier (and faster) over time.

view more: next ›