I hate mobile dev. I am doing iOS amd Flutter for 12 years. I want to do Rust stuff, blockchain and so on.

I need some mentor even though I have read two books. Should I find one or rely on ChatGPT?

Any Rust devs here? What is it like?

Rust dev here 👋

Finding a mentor is always challenging since you're basically asking someone to teach you which is quite a time investment

It's best to start with the Rust Book by Klabnik and Nichols. It's relatively short and depending on your programming abilities can be a bit boring but it goes over a lot of the language. After that start doing your own project and curse the ghost of graydon for all the lifetime issues you're gonna face

No seriously, Rust is a hard language because it's very different. It /looks/ familiar but it certainly isn't. Expect a lot of frustration the first 2 or 3 weeks

Oh yeah and I you have any questions feel free to tag me (only works in comments not in posts!) if you have a question. I look at devrant every now and then and I'm happy to answer any question

Have you tried iOS native with SwiftUI without the Flutter bullshit? I‘m doing it for years and it’s the most fun I ever had.

@12bitfloat nice from you to offer :)

Best way to do rust is to try to make something, break it, fix it, improve it, break it again, and fix it again until you become good at it.

@retoor Eh, might as well help people when doom scrolling devRant anyways :D

@Tounai Agreed. I would even generalize that process you described the best way to learn anything.

Ofc with common sense applied, like don't go breaking nuclear reactors and stuff.

I'm in the process of learning rust and then anchor framework

If you wanna learn/do some blockchain stuff and dont mind signing an NDA, we should chat

I have telegram (awesomeest) and discord (sara.awesomeest)... you/anyone can also reach me via email... same name as here @gmail.com.

I still need to decide if rust will be used in any significant amount for our biggest project, but already stuck with python (a necessary evil in mass data of our variety), probably some conda and possibly rust... even if i prefer giant, custom written, oracle orchestrations... likely beyond a healthy level.

@Tounai isnt breaking and rebuilding things the logical standard for just about any engineering?
...or just mine?

@12bitfloat
I actually have a rust book in my amazon cart (scheduked to be finalised/purchased later today) but it was the O'Reilly one. I throughly enjoy the O'Reilly pocket guides and when i need a full book to read through, i typically go with O'Reilly or packt.

I assume you believe your suggestion to be better? (Already added to cart) any specifics you like about it?

And thx for the suggestion (even though it wasn't for me)

@awesomeest Well, The Book™ (https://doc.rust-lang.org/book/ ) is just the default introductory material everyone recommends, partially because it's free and gives a quick overview over much of the language

I'm not too well versed with beginner material though, I only read the book and then went off and did my own thing, so I can't really give any recommendations

@awesomeest use the official free one. Stop being scammed. The official one gives you all you need.

@12bitfloat
yea... glad i got *not that*.

the 2 big, initial, issues with that free one, just from your short few lines...

1. i almost exclusively use physical books. digital books and i rarely get along. most e-readers have some annoying delay or page-turn animation\sound\inability to rapidly turn pages. using something that scrolls tends to suck for me too. idk if it's a smoothness\frame rate issue or just not compatible with how my eyes focus. ive considered experimenting and\or building my own... but that's kinda voided by the same rationale of learning the content>> building something else. i think i just read too fast.

2. beginner books-
though, in any subject, i tend to avoid them like the plague (by start of 2nd grade i already made a short script for Microsoft sam to read whatever was reqd, on a loop, while i played neopets, consoles, etc).

recently this has been harshly reaffirmed. ive had to go through newb books\etc for babydevs.

@12bitfloat

~2yrs ago i found out ppl "practice" code... not just write it and edit\fix\re-engineer. i had literally never considered this. immediately i asked like a dozen ppl i knew about this. it seems mostly a generational thing(from start of dev not age)... so everyone around my age(32) or below actually wrote essentially unusable code before attempting any usable code.

it still blows my mind. doctors\surgeons...you should practice, a lot, on non-humans, when possible... code thats not being immediately put into some corruptible live system... i dont get it.

side note:
do to this, and several other factors (like assuming people "building" a computer, meant what i was doing... cutting\joining\remapping mobos, including Frankenstein-esq de\re-soldering chips etc, and ofc driver creation)... with most things, esp tech, i have a dangerous lacking of any valid frame of reference. teach someone about storage?...im pretty sure i should stop before data fragmentation patterns right?

@Tounai physical book vs my frustration, sanity and time sink... im not one to be scammed.

@awesomeest hmm, practice code as in short snippets.. Meh, short codes are easy. Making smth big that still looks decent and all is connected without workarounds is the art imho

@awesomeest find a physical version of the official one.

@awesomeest agree on physical books. EReader didn't turn out for me and I can't study good on the machine I'll do coding on. Everything I read has to be tried out directly. With a book I read further ahead and also the page turning matters much to me

@typosaurus

What do you define as a workaround?

Never thought of it so maybe its just me... but i always just considered it literally... working around some sort of preexisting construct, whether it's a pile of bricks irl or some annoying, bulky, and/or dysfunctional code/mechanisms.

@Tounai nope... was already in the cart

@awesomeest that‘s an interesting thought.

I‘ve always been using "workaround" to describe a solution which kind of solves the problem, but the way how it is solved has problems itself or the problem is only solved partly.

You made me realize that it’s a bit of a departure from the original meaning, which you have described.

@awesomeest Oh man, when I hear the term "workaround," my first thought is, like, what's wrong with just fixing that crap? But then again, life isn't always about fixing things. Sometimes it's about making them work with whatever you've got. So yeah, a workaround is when you find a way to get by with something, even if it's not the most optimal solution. It's like building your own house out of rocks instead of buying fancy bricks. You know, just doing what you gotta do to survive in this coding world!

@Lensflare yea... im literal af... like to a fault.

Though apparently i messed with you a bit too well in german, i do actually know language, to a degree beyond what i want to publicly acknowledge(feel free to inquire elsewhere).

I innately tend heavily towards original, literal, meanings and/or the etymological roots of terminology.

WARNING: Side Rant
Meanings of words like "selfish" typically annoy me.

Originally, "selfish" literally meant not considering others. No ill will, greed, recognition of some negative thatd effect others, then just doing it anyways despite knowing the probable harms...
Just simply, never having that spark/urge/sight to consider people/things outside of one's mental thought bubble.

The original def of selfish is how most autistics (incl me) innately are. Nothing to do with ego/like/dislike of ppl. literally, not considering-- like having blinders

Now, selfish means you know youre causing hardship but do it anyways to get what you want.

@Lensflare

Side rant, that may give some additional insight into my atypical thought patterns about linguistics...

In 4th gr(near Y2K bs), my favourite book became, and still is, 1984 (read animal farm 1st... ran out of encyclopaedias i hadnt read).

I don't mind colloquialisms, or almost any new terminology, but I am strongly against proliferating the concept of 'it dont matter how i talk if u know what i mean'. Imo USA is the worst.

I can (have, for good pay) explain and theoretically prove the real fallout/dangers in losing the ability of non-colloquial, custom, communication.

Basic/already occurring problems are detrimental at the personal level, yet not inspiring change. The current overly tolerant of... nearly everything, incl harmful thought/actions/etc, promotes social decline, propagating the issues.
Deny a job, as they can't form sentences or have a very limited vocab, explain why= risk being a social media villain/potential lawsuits, don't= propagate the issue.