Explore the vast range of titles available.

Firm participation in open source software (OSS) development is a noteworthy phenomenon and includes two types of firm-participating OSS projects: community founded (developed from an open project) and spinout (spun out from an information technology firm’s internal project). OSS project leaders implement quality controls to improve the quality of developed products. They may not be aware that their implementation of quality controls produces a side effect—quality controls signal unobservable project quality to volunteers and promote volunteers’ continued participation intentions (VCPI). We focus on two quality controls— accreditation and code acceptance , which, respectively, map to the input and output quality of an OSS project—and compare their respective effects on VCPI in community-founded and spinout projects. We propose that accreditation and code acceptance influence VCPI by signaling unobservable input and output quality to volunteers. As we focus on continued participation, we theorize as to how volunteers’ tenure in OSS projects moderates the relationships between the signaling effects of input and output quality controls and VCPI. Furthermore, we theorize as to how the OSS project type moderates the effects of quality controls on VCPI. We surveyed 304 volunteers from 40 OSS projects and constructed a two-level model of project and developer factors to explain VCPI. Our findings indicate that both accreditation and code acceptance enhance VCPI. The signaling effects on VCPI associated with accreditation decline with volunteer tenure, but those associated with code acceptance do not. Accreditation and code acceptance influence VCPI, with community-founded projects exhibiting weaker direct positive effects and spinout projects exhibiting stronger direct positive effects. We discuss the theoretical and practical implications of these findings.

Anxiety about giving and receiving code reviews has been documented as a common occurrence that leads to developers avoiding code reviews by procrastinating and limiting their cognitive engagement with them. This avoidance not only increases anxiety in the long term, but also prevents developers, their teams, and their organizations from accessing the technical and sociocognitive benefits of effective and efficient code reviews. However, software research has not yet empirically examined code review anxiety, and from this, tractable intervention targets and strategies for mitigating code review anxiety. In this study, we present an empirical framework for understanding the factors maintaining and exacerbating code review anxiety. Utilizing a randomized waitlist control trial, we also tested the effectiveness of a novel single-session cognitive-behavioral workshop intervention. Our results show evidence that positive impact can be obtained from a brief intervention and suggest code review anxiety can be successfully mitigated by targeting developers’ cost bias, anxiety self-efficacy, and self-compassion.

Quantum computing proposes a revolutionary paradigm that can radically transform numerous scientific and industrial application domains. To realize this promise, these new capabilities need software solutions that are able to effectively harness its power. However, developers may face significant challenges when developing and executing quantum software due to the limited availability of quantum computer hardware, high computational demands of simulating quantum computers on classical systems, and complicated technology stack to enable currently available accelerators into development environments. These limitations make it difficult for the developer to create an efficient workflow for quantum software development. In this paper, we investigate the potential of using remote computational capabilities in an efficient manner to improve the workflow of quantum software developers, by lowering the barrier of moving between local execution and computationally more efficient remote hardware and offering speedup in execution with simulator surroundings. The goal is to allow the development of more complex circuits and to support an iterative software development approach. In our experiment, with the solution presented in this paper, we have obtained up to 5 times faster circuit execution runtime, and enabled qubit ranges from 21 to 29 qubits with a simple plug-and-play kernel for the Jupyter notebook.

Human values such as honesty, social responsibility, fairness, privacy, and the like are things considered important by individuals and society. Software systems, including mobile software applications (apps), may ignore or violate such values, leading to negative effects in various ways for individuals and society. While some works have investigated different aspects of human values in software engineering, this mixed-methods study focuses on honesty as a critical human value. In particular, we studied (i) how to detect honesty violations in mobile apps, (ii) the types of honesty violations in mobile apps, and (iii) the perspectives of app developers on these detected honesty violations. We first develop and evaluate 7 machine learning (ML) models to automatically detect violations of the value of honesty in app reviews from an end-user perspective. The most promising was a Deep Neural Network model with F1 score of 0.921. We then conducted a manual analysis of 401 reviews containing honesty violations and characterised honesty violations in mobile apps into 10 categories: unfair cancellation and refund policies; false advertisements; delusive subscriptions; cheating systems; inaccurate information; unfair fees; no service; deletion of reviews; impersonation; and fraudulent-looking apps. A developer survey and interview study with mobile developers then identified 7 key causes behind honesty violations in mobile apps and 8 strategies to avoid or fix such violations. The findings of our developer study also articulate the negative consequences that honesty violations might bring for businesses, developers, and users. Finally, the app developers’ feedback shows that our prototype ML-based models can have promising benefits in practice.

Cross-platform mobile application development has gained significant traction in recent years, driven by the growing demand for efficient, cost-effective solutions that cater to both iOS and Android platforms. This paper presents a state-of-the-art review of cross-platform mobile application development, emphasizing the industry trends, framework popularity, and adoption in the job market. By analyzing developer preferences, community engagement, and market demand, this study provides a comprehensive overview of how cross-platform mobile development frameworks shape the mobile development landscape. The research employs a data-driven methodology, drawing insights from three key categories: Developer Sentiment and Survey Data, Community Engagement and Usage Data, and Market Adoption and Job Market Data. By analyzing these factors, the study identifies the key challenges and emerging trends shaping cross-platform mobile application development. It assesses the most widely used frameworks, comparing their strengths and weaknesses in real-world applications. Furthermore, the research examines the industry adoption patterns and the presence of these frameworks in job market trends. Unlike earlier research, which included now-obsolete platforms like Windows Phone and frameworks such as Xamarin, this study is tailored to the current cross-platform mobile application development market landscape. The conclusions offer actionable insights for developers and researchers, equipping them with the knowledge needed to navigate the evolving cross-platform mobile application development ecosystem effectively.

Purpose This study examines the influence of developer experience between human resource management (HRM) practices and innovation in software (S/W) engineering. This study uses motivation theory and investigates how HRM practices influence the innovative behaviors of S/W developers by using a mediator of affective developer experience. Design/methodology/approach For this, this study used a survey of S/W developers working in Korea. Out of 431 responses collected from 35 companies, 352 responses from 34 companies were usable for analysis and takes structural equation modeling. Findings The results show that developmental appraisal, externally or internally equitable reward and comprehensive training increase their affective developer experience affecting innovative behaviors positively in turn. However, selective staffing has no effect. Originality/value The results show that S/W developers pursue individual growth rather than success in their organizations. The findings show the context of S/W engineering in Korea and provide universalistic perspective when top managers motivate their S/W engineers by HRM system.

Integrating theory and practice and developing professional skills required for the Software Engineering (SE) market are still challenges for universities. In this context, this article aims to investigate the effects of Developer Experience (DX) in a Project-Based Learning (PBL) approach during the SE teaching-learning process. To do so, we performed a case study on an SE subject in an Information Systems (IS) course over two semesters, using a PBL approach and a DX questionnaire. As a positive aspect, the results highlighted the development of teamwork skills and experience close to the real professional context. As a negative one, the participants reported a short time to assimilate new knowledge. Thus, it is possible to highlight two implications for teaching practice in SE: (i) checking the students' level of knowledge before starting the projects and (ii) continuous monitoring of the activities. Integrar teoria e prática e desenvolver habilidades profissionais necessárias para o mercado de Engenharia de Software (ES) ainda são desafios para as universidades. Nesse contexto, o objetivo deste artigo é investigar os efeitos da Experiência de Desenvolvedor (DX, do inglês Developer Experience) em uma abordagem de Aprendizagem Baseada em Projetos (ABP) durante o processo de ensino-aprendizagem de ES. Para isso, foi realizado um estudo de caso em uma disciplina de ES de um curso de Sistemas de Informação (SI) durante dois semestres, utilizando uma abordagem de ABP e um questionário sobre DX. Como aspecto positivo, os resultados ressaltaram o desenvolvimento de habilidades para o trabalho em equipe e a vivência próxima ao contexto profissional real. Como aspecto negativo, os participantes relataram o pouco tempo para assimilar novos conhecimentos. Com isso, é possível destacar duas implicações para a prática docente em ES: (i) verificação do nível de conhecimento dos alunos antes do início dos projetos e (ii) acompanhamento contínuo das atividades. Integrar teoría y práctica y desarrollar las competencias profesionales necesarias para el mercado de Ingeniería de Software (IS) son desafíos para las universidades. En este contexto, el objetivo de este artículo es investigar los efectos de la Experiencia del Desarrollador (DX, do inglés Developer Experience) en un enfoque de Aprendizaje Basado en Proyectos (ABP) durante el proceso de enseñanza-aprendizaje de IS. Para eso, se realizó un estudio de caso en una disciplina de IS de un curso de Sistemas de Información (SI) durante dos semestres, utilizando un enfoque ABP y un cuestionario de DX. Como aspecto positivo, los resultados destacaron el desarrollo de habilidades para trabajo en equipo y una experiencia cercana al contexto profesional real. Como aspecto negativo, fue reportado el poco tiempo para asimilar nuevos conocimientos. Con eso, es posible destacar dos implicaciones para la práctica docente en IS: (i) verificación de conocimientos de los estudiantes antes del inicio de los proyectos y (ii) seguimiento continuo de las actividades.

Earlier software development processes (SDPs), such as waterfall processes, were mainly focused on process steps and did not address people- and product-related issues. Emergence of Software development methodologies (SDM) has created a new paradigm for developing software systems. A SDM is a special kind of technically engineered framework for organizing SDPs; this framework is expected to specify three main interwoven elements, namely people, products, and process. It has since become evident that it is impossible to provide a general-purpose SDM for developing all the various kinds of software systems, and it has thus become essential to construct the most appropriate methodology for the system development situation in hand, a practice commonly called Situational Method Engineering (SME). The problem with existing SME methods is lack of adequate attention to the role of people who might seek or possess valuable knowledge about the project situation. This knowledge can be tacit information that is hidden in the developer’s mind, or it might be explicitly available. This paper proposes a knowledge management (KM)-driven and DevOps-based SME method as a new integrated multi-view methodological paradigm that satisfies the need for sharing human experience in engineering SDMs. The method has been proposed by reusing general SME practices and complementing them by embedding appropriate KM and DevOps practices to alleviate the weaknesses of previous SME methods. Furthermore, the proposed method has been evaluated through four case studies and also by conducting a criteria-based comparison with eight prominent SME methods.

Background: Developer experience should be considered a key factor from the beginning of the use of development platform, but it has not been received much attention in literature. Research Goals: The present study aimed to identify and validate the sub-constructs and item measures in the evaluation of developer experience toward the use of a deep learning platform. Research Methods: A Delphi study as well as a series of statistical methodologies including the assessment of data normality, common method bias, and exploratory and confirmatory factor analysis were utilized to determine the reliability and validity of a measurement model proposed in the present work. Results: The results indicate that the measurement model proposed in this work successfully ensures the nomological validity of the three second-order constructs of cognitive, affective, and behavioral components to explain the second-order construct of developer experience at p < 0.5 Conclusions: The measurement instrument developed from the current work should be used to measure the developer experience during the use of a deep learning platform. Implication: The results of the current work provide important insights into the academia and practitioners for the understanding of developer experience.

Purpose - The purpose of this paper is to understand the trends and contribution of private equity (PE) investors in real estate development in India because the real estate sector in India had witnessed significant investments from PE firms in recent years. Design/methodology/approach - The study focused on residential segment of real estate development, as it is the largest among all the segments. Two types of analyses have been done in this paper: first was to compare residential projects with PE investment with those that did not have any PE investment. The results were based on an analysis of 453 residential projects. The second was an analysis of only those projects that had PE investment. This paper studied if there were differences in investment patterns between domestic and foreign PE investors, and dedicated and diversified PE investors. Findings - Projects with PE investment were larger, as compared to projects that did not have any PE investment. The results of this paper also showed that PE firms preferred to invest with developers who had significant experience in undertaking larger-sized projects. PE investments significantly happened in projects that were located in metro cities. While PE firms as a whole preferred to invest in project mode, domestic investors were more inclined to invest in a project structure as compared to foreign PE firms. Though foreign PE firms invested more amounts per deal on average, there was a negative relationship between foreign PE firms and the extent of their shareholding in the investment. Practical implications - Encouraging PE investment in real estate projects would contribute toward to increasing the transparency in the sector. Strengthening the domestic PE industry would increase investment flow for real estate projects. PE investors who are able to add value to their investments are able to obtain higher shareholding. Originality/value - Empirical research on Indian real estate industry is scarce because of the lack of transparency and availability of reliable data. This is one of the initial studies on the Indian real estate sector based on a robust dataset.