Our great sponsors
-
Clippy
A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
bloom
The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more (by skerkour)
I'm not familiar with this space - I assume 'Triox' refers to https://github.com/AaronErhardt/Triox (which looks like it's written by you!), but what does 'Bloom' refer to?
I think as you work through an actual problem, you'll eventually fumble your way to solutions. Don't worry if they're not elegant or well-thought-out; if it compiles, that's a great sign. If it doesn't, then pay attention to the error message, as it's generally informative enough to point you in the right direction. The compiler (and clippy if you're up for it), in conjunction with The Book, should give you a sense for how an idiomatic programmer would solve a problem.
I find of the two above that the second one is the harder of the two challenges. To be proficient in the ecosystem, you have to understand not just how to write your own code, but also how to make use of others'. Without knowing your usual problem domains, it's tough to give you reference points, but if you're used to writing web apps (e.g. Hapi or Express apps in Node), consider trying your hand at something like Rocket. There are some great resources to get to know your options depending on your domain (e.g. games, web, GUI). Also, if you're a web dev, don't forget that WebAssembly is a thing, so you might look to try migrating some existing code and seeing if you can keep feature parity.
Interesting that Triox is much easier to find. Maybe that's because Bloom rather advertises as Google alternative than as a cloud server: https://github.com/skerkour/bloom