IBM 610 workstation computer 3420

i don't think it is necessarily gender limited. there may be actually be two separate issues ... one is the different thinking styles and two actually being able to dynamically adapt thinking styles as appropriate to the circumstance.

note that single thread vis-a-vis multi-threaded thinking modes may also spill over into areas like doing single variable-objectiive optimizations vis-a-vis doing multi-model optimizations (aka trade-offs).

one of the things that i was doing back as an undergraduate with the dynamic adaptive fairshare scheduling ... was being able to dynamic adapt scheduling to the bottleneck. some strategies might be able to default cpu use to resource utilization and dynamically adapt scheduling to amount of (cpu) resource consumed. one of the things that i was playing with was attempting to dynamically determine different resource system bottlenecks on a moment-to-moment basis and dynamically adapt bottleneck resource factors given to the different types of resources that might be consumed by a task.

for instance, for a heabily paging constrained-bottleneck moment the amount of cpu consumed by a task may be nearly immaterial in the efficient operation of the overall system.

one of the things that i got into trouble with doing the scheduler is that a lot of kernel programmers tend to be strictly state oriented ... setting and testing particular state bits. there were places in the scheduler that i would arbitrarily switch back and forth from a highly optimized bit-state manipulation style of programming ... to much more a fortran-apl probabilistic (say operations research) style of programming (although done in buttembler). individuals accustomed to a single programming style-mode frequently found it difficult to follow the logic flow across the arbitrary different programming styles.

--