How long would you say it took you before getting a fundamental understanding?

I would say years, as with any complex activity.

I’m still forgetting things I learned 3 or even 4 times like how to do a for each loop.

You can forget in 2 different ways:

1. Forget how to use something, so you need to look how to do it.
2. Forget that something exists, so you cannot even look for it because you are not aware it’s a possibility.

You will forget-1 everything which you don’t use on a daily basis. That’s what internet is for. Forgetting in the 2-nd sense is much more rare and you should do something if that’s the case.

all of it feels too advanced and I get lost on how to begin

This is a bias most of us have, you overlook how easy is for you to do things that previously were impossible and focus on how hard are the things you still don’t know how to do. And computing is so complex right now that there always be “infinite” things you don’t know.

Try showing what you know to someone who doesn’t know how to code and you will get an idea of how much you have learnt :).

Anyway, I don’t really have good advice :/, just wanted to confirm that what you feel is expected. Good luck!

Source: StormyGail Art (Twitter)

Nitter link

Nitter RSS Feed: https://nitter.cz/stormygailart/rss

Web: https://stormygailart.com/

Source: A Friend in Need by JoeGPcom on DeviantArt

The author also has a Tumblr, but I couldn’t find the comic there: https://jeffmumm.tumblr.com/archive

Credit Antоn Gudim

• Proxigram: https://proxigram.privacyfrontends.repl.co/gudim_public
• RSS Feed: https://proxigram.privacyfrontends.repl.co/gudim_public/rss
• Instagram: https://www.instagram.com/gudim_public/

Summary generated with claude.ai from the video transcript:

Christopher Neugebauer discusses how even simple things in Python like print() hide complexity, and how Python has evolved to model more complexity so users can write simpler code. He explores ideas around internal vs external complexity, managing complexity through testing/types, and how our definition of simplicity changes over time with new tools/opinions.

Key points:

• Simplicity often hides complexity somewhere in the system
• We should think about who experiences simplicity vs complexity
• Python models complexity so users can write simpler code
• Tools like dependencies and type annotations help manage complexity
• Definition of “simple” changes over time as tools/opinions evolve
• We should simplify appropriately for end users, not everywhere
• Complexity exists; we can choose to contain it or not for users

First Google result for the search Railway Oriented Programming in python:

• Agile & Coding: A Pythonic Railway?

Repository: DavidVujic/pythonic-railway: Experimenting with Railway oriented programming and Python

YouTube video (5min): David Vujic - A Pythonic Railway?

Appreciate the appreciation ^_^

Which (if I understand correctly) is almost what Forth does. I’ve heard it described as “the only syntax in Forth are the blank characters” :).

For those out of the loop, like me, from Wikipedia:

Captology is the study of computers as persuasive technologies.[1] This area of inquiry explores the overlapping space between persuasion in general (influence, motivation, behavior change, etc.) and computing technology.[2] This includes the design, research, and program analysis of interactive computing products (such as the Web, desktop software, specialized devices, etc.) created for the purpose of changing people’s attitudes or behaviors.[3]

B. J. Fogg in 1996 derived the term captology from an acronym: Computers As Persuasive Technologies. In 2003, he published the first book on captology, entitled Persuasive Technology: Using Computers to Change What We Think and Do.[4]

Captology is not the same thing as Behavior Design, according to BJ Fogg who is the person who coined both terms and created the foundation for both areas.