The whole unsafe memory topic is rather an insightful detour in the book. The line is thin between keeping things “easy” and actually connecting the dots for deeper understanding. At least memory safety can feel like a blessing afterwards and not just smth to take for granted.

I thought the same but the co-author made me change my mind 🙃

I have one chat window right now about it which is a constantly growing pile, so I rather don't share that. I'll keep it in mind for the future that this stuff is also worth sharing, so thanks for the tip

LLMs are amazing learning tools—if you use them with intention.

These 3 things helped me not just get answers, but grow as a Swift beginner.

Got your own AI learning tricks? Tell me 👇

🗣️ Tip 3 — Ask it to challenge you

Instead of asking for help, I’d say:
"Can you check if I understood what I just learned?"

It turned reading into recall.

It made learning feel like a game.

🦆 Tip 2 — Talk it out

After learning something new, I’d explain it to the LLM like I was teaching it.

It’s like rubber duck debugging—with answers.

I reinforced what I knew and found out what I didn’t.

🔁 Tip 1 — Rephrase it yourself

Instead of asking for an explanation, I’d rewrite the code in my own words.

On lazy days, I wanted a shortcut. But forcing myself to retype a snippet as I understood it helped more.
By the end, I often realized I got it—I just needed affirmation.

LLMs have a wide range of applications and its reliability varies depending on the field and use case. I’m happy that you can successfully make stuff work in your business🌈

Don’t worry, it’s not going on a physical shelf, though you’re half right, which is about as accurate as an LLM. A ~50% error rate wouldn’t fly in any classroom, would it?

Thanks for reading.

More info soon!

I soon finish writing a Swift book with @tiborbodecs.bsky.social for absolute beginners — the kind I wish existed when I started.

I left the corporate comfort to teach myself coding — Along the way, I realized how few truly beginner-friendly resources exist.

After years in UX, I realized I wanted to build more than screens — I wanted to build things.