human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "how do you feel developer an explanatory theory of the impact of affects on programming performance"
  Abstract: Affects---emotions and moods---have an impact on cognitive activities and the working performance of individuals. Development tasks are undertaken through cognitive processes, yet software engineering research lacks theory on affects and their impact on software development activities. In this paper, we report on an interpretive study aimed at broadening our understanding of the psychology of programming in terms of the experience of affects while programming, and the impact of affects on programming performance. We conducted a qualitative interpretive study based on: face-to-face open-ended interviews, in-field observations, and e-mail exchanges. This enabled us to construct a novel explanatory theory of the impact of affects on development performance. The theory is explicated using an established taxonomy framework. The proposed theory builds upon the concepts of events, affects, attractors, focus, goals, and performance. Theoretical and practical implications are given.

Connected through hyperedge HE-1 (induced by source paper "happiness and the productivity of software engineers"):
  with members:
    - "what happens when software developers are un happy"
    - "on the unhappiness of software developers"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "software developers moods emotions and performance"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-2 (induced by source paper "what happens when software developers are un happy"):
  with members:
    - "unhappy developers bad for themselves bad for process and bad for software product"
    - "consequences of unhappiness while developing software"
    - "on the unhappiness of software developers"
    - "mining valence arousal and dominance possibilities for detecting burnout and productivity"
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "the affect of software developers common misconceptions and measurements"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "software developers moods emotions and performance"

Connected through hyperedge HE-3 (induced by source paper "towards a theory of software development expertise"):
  with members:
    - "the links between agile practices interpersonal conflict and perceived productivity"
    - "worse than spam issues in sampling software developers"

Connected through hyperedge HE-4 (induced by source paper "consequences of unhappiness while developing software"):
  with members:
    - "unhappy developers bad for themselves bad for process and bad for software product"
    - "mining valence arousal and dominance possibilities for detecting burnout and productivity"
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "the affect of software developers common misconceptions and measurements"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "software developers moods emotions and performance"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-5 (induced by source paper "on the unhappiness of software developers"):
  with members:
    - "consequences of unhappiness while developing software"
    - "mining valence arousal and dominance possibilities for detecting burnout and productivity"
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "the affect of software developers common misconceptions and measurements"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "software developers moods emotions and performance"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-6 (induced by source paper "unhappy developers bad for themselves bad for process and bad for software product"):
  with members:
    - "understanding the affect of developers theoretical background and guidelines for psychoempirical software engineering"
    - "do feelings matter on the correlation of affects and the self assessed productivity in software engineering"
    - "software developers moods emotions and performance"
    - "happy software developers solve problems better psychological measurements in empirical software engineering"

Connected through hyperedge HE-7 (induced by source paper "towards the assessment of stress and emotional responses of a salutogenesis enhanced software tool using psychophysiological measurements"):
  with members:
    - "unhappy developers bad for themselves bad for process and bad for software product"
    - "at ease with your warnings the principles of the salutogenesis model applied to automatic static analysis"
    - "software developers moods emotions and performance"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.SE(Software Engineering)