this post was submitted on 05 Feb 2025
521 points (96.8% liked)
Greentext
5099 readers
662 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't think that's quite accurate.
The "understand it well enough to explain it to a professor" clause is carrying a lot of weight here - if that part is fulfilled, then yeah, you're actually learning something.
Unless of course, all of the professors are awful at their jobs too. Most of mine were pretty good at asking very pointed questions to figure out what you actually know, and could easily unmask a bullshit artist with a short conversation.
I didn't say you'd learn nothing, but the second task was not just to explain (when you'd have the code in front of you to look at), but to actually write new code, for a new problem, from scratch.
You don't need physical skills to program, there is nothing that needs to be honed in into the physical memory by repetition. If you know how to type and what to type, you're ready to type. Of you know what strings to pluck, you still need to train your fingers to do it, it's a different skill.