It was just things like her saying, "This is a hardware problem, not a software one" and "I think in subroutines" that felt very off.
As a (woman) programmer in the late 80s, these are things I would have said. Especially the last one. When working with (then relatively new) languages like Pascal and C, we were all rigourously focusing on how to compartmentalise as many tasks as possible into (generic term) subroutines, because it made coding and debugging much, much easier. Since many of us had stared out on the original BASIC, this meant changing the way we thought about programming, and so there was an overemphasis on viewing every task in terms of inter-related subroutines, and a lot of us began seeing life like that..
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Wed, Aug. 29th, 2007 06:41 pm (UTC)It was just things like her saying, "This is a hardware problem, not a software one" and "I think in subroutines" that felt very off.
As a (woman) programmer in the late 80s, these are things I would have said. Especially the last one. When working with (then relatively new) languages like Pascal and C, we were all rigourously focusing on how to compartmentalise as many tasks as possible into (generic term) subroutines, because it made coding and debugging much, much easier. Since many of us had stared out on the original BASIC, this meant changing the way we thought about programming, and so there was an overemphasis on viewing every task in terms of inter-related subroutines, and a lot of us began seeing life like that..