this post was submitted on 16 Dec 2024
599 points (98.7% liked)
Technology
60055 readers
3959 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Seem to be 2 problems. One is obvious, the other is that such tedious boilerplate exists.
I mean, all engineering is divide and conquer. Doing the same thing over and over for very different projects seems to be a fault in paradigm. Like when making a GUI with tcl/tk you don't really need that, but with qt you do.
I'm biased as an ASD+ADHD person that hasn't become a programmer despite a lot of trying, because there are a lot of things which don't seem necessary, but huge, turning off my brain via both overthinking and boredom.
But still - students don't know which work of what they must do for an assignment is absolutely necessary and important for the core task and which is maybe not, but practically required. So they can't even correctly interpret the help that an "AI" (or some anonymous helper) is giving them. And thus, ahem, prepare for labs ...
If you're in school, everything being taught to you should be considered a core task and practically required. You can then reassess once you have graduated and a few years into your career as you'll now possess the knowledge of what you need and what you like and what you should know. Until then, you have to trust the process.
People are different. For me personally "trusting the process" doesn't work at all. Fortunately no, you don't have to, generally.
I have never had a student with this attitude pass my program, and I've had a great many students with this attitude. Take from that what you will.
Then you are a bad instructor, obviously.
Because it's often not like this and the difference is usually in the instructor.
That's what I take from that.
(Other than common sense about meaningless mimicking versus gradual understanding from small steps, confirmed by plenty of research about didactics.)
I'm going to be totally honest, on a re-read I do not understand what you're trying to say here.
Not sure which particular parts are confusing, so I'm going to guess and rephrase like this:
People are obviously different, it's obvious that a certain process can't fit all sizes, so if there's a kind of "attitude" with which that process fails, then the problem can be both with the process and with the attitude.
And in my personal experience there are processes which work just fine with that attitude.
Processes are built for human needs. Not humans are built for processes.
So the problem is with the process, which includes the instructor who seems to think that it's not.