Thanks 😊. Overall I'm really enjoying it these days. I think she is enjoying learning, but even after ~10 months there are still a lot of concepts and jargon that are completely foreign. I didn't realize how much of software engineering relies on acronyms!
The first memory I had of teaching her was explaining how the terminal is just another UI into the computer's underlying functionality (compared to GUIs and voice commands). But to do that, I had to explain what was under the hood in a computer. And down that rabbit hole we went!
These days, she has an app on Google App Engine (leksi.co if you're interested). It's a flask app with a Vue JS frontend. Architecturally, it's using a bunch of different APIs, using background queues & workers, and even has to do some complicated database operations and distributed coordination (she's generating a bunch of MP3s in separate processes and then combining them all together in the final step).
The easier part for me is explaining the architecture design, but when it comes time to translate that to code, it gets really hard. Kinda reminds me of when you can understand a spoken language, but it's crazy hard to actually speak to someone.
You gave me an idea to write about my experience teaching (with her permission).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks 😊. Overall I'm really enjoying it these days. I think she is enjoying learning, but even after ~10 months there are still a lot of concepts and jargon that are completely foreign. I didn't realize how much of software engineering relies on acronyms!
The first memory I had of teaching her was explaining how the terminal is just another UI into the computer's underlying functionality (compared to GUIs and voice commands). But to do that, I had to explain what was under the hood in a computer. And down that rabbit hole we went!
These days, she has an app on Google App Engine (leksi.co if you're interested). It's a flask app with a Vue JS frontend. Architecturally, it's using a bunch of different APIs, using background queues & workers, and even has to do some complicated database operations and distributed coordination (she's generating a bunch of MP3s in separate processes and then combining them all together in the final step).
The easier part for me is explaining the architecture design, but when it comes time to translate that to code, it gets really hard. Kinda reminds me of when you can understand a spoken language, but it's crazy hard to actually speak to someone.
You gave me an idea to write about my experience teaching (with her permission).