3 ms·
> Frankly, most 35 y/o engineers don't truly appreciate the intricacies of intra-thread concurrent algorithms You don't need to know the intricacies, just the
by sh4rks 4y ago
> Frankly, most 35 y/o engineers don't truly appreciate the intricacies of intra-thread concurrent algorithms
You don't need to know the intricacies, just the foundational basics. Locks, blocking threads, deadlocks etc. Any half decent CS course will teach you these concepts.
- lfowles 4y agoIf it only takes one course it shouldn't take long for them to get up to speed. Gauge their ability to learn rather than what they have learned.
- sanderjd 4y agoIt is necessary to know such things exist, but expected that their details will be looked up when relevant. Some people write low level concurrent code all the time, and they need to be up on all those details all the time. But many people only do so intermittently, and they only need to be aware of the existence of tricky details in the space, and have the capacity to get up to speed on them.
- HervalFreire 4y agoGive me some examples of intricacies?
- jobs_throwaway 4y agoDo you mean any half-decent concurrent programming CS course? Because your intro (or even intermediate) CS courses don't come anywhere close to broaching those topics, even at elite universities. The real issue IMO is that you can get a CS degree without taking a concurrent programming course
- gardenhedge 4y agoWhy is that an issue? Most programmers won't need to do concurrent programming, right?
- sh4rks 4y agoWell this is news to me. Maybe things are different in the USA
- jobs_throwaway 4y agohow would an intro course even get into these topics? Like, is week 1 here's a variable and a for loop, week 2 pointers, week 3 here's a semaphore?
- sh4rks 4y agoStudents aren't looking for internships after 3 weeks though. You usually start applying at the end of the year. By then, your CS course should have covered the very basics of concurrent programming. Maybe we have different definitions of "CS course"