Objective In recent years, the global increase in drug resistance rates against antiretroviral therapy (ART) regimens has underscored the importance of incorporating HIV drug resistance testing into routine clinical practice and its critical role in treatment success. The aim of this study was to determine HIV drug resistance and the associated genetic mutations in 278 treatment-naïve HIV-1–infected patients followed at our clinic. Methods This single-center retrospective study evaluated treatment-naïve HIV-1–infected individuals followed at our institution. Prior to ART initiation, whole blood samples collected in EDTA tubes were sent to the National HIV/AIDS Confirmation Center and Viral Hepatitis Reference Laboratory of the General Directorate of Public Health, Ministry of Health of Türkiye. Viral RNA extraction was performed, and the HIV-1 pol region was amplified using reverse transcription polymerase chain reaction (RT-PCR). Amplified products were examined by agarose gel electrophoresis and subsequently sequenced using the Sanger sequencing method on an ABI 3500 XL platform (Applied Biosystems, USA). The resulting FASTA sequences were aligned using Unipro Ugene v50 software, and consensus sequences for the protease and reverse transcriptase (RT) regions were generated. Viral subtype determination was performed using the Rega HIV-1 Subtyping Tool (v3). Drug resistance mutations (DRMs) were classified using the Stanford University HIV Drug Resistance Database (HIVdb v9.7), and resistance rates and mutation profiles were determined for protease inhibitors (PIs), nucleoside reverse transcriptase inhibitors (NRTIs), and non-nucleoside reverse transcriptase inhibitors (NNRTIs). Results Of the 278 treatment-naïve HIV-1–infected patients included in the study, 240 (86.3%) were male and 38 (13.7%) were female. The mean age was 41.8 ± 12.5 years, with no significant age difference between sexes (males: 41.5 ± 12.5; females: 43.4 ± 12.5; p = 0.397). Resistance-associated mutations (RAMs) were detected in 154 patients (55.4%). After excluding mutations that did not affect susceptibility to any antiretroviral agent, clinically relevant DRMs conferring resistance to at least one drug class were identified in 123 patients (44.2%).When DRM frequencies were evaluated in the entire cohort (n = 278), PI-associated mutations were detected in 51 patients (18.3%), NRTI-associated mutations in 14 patients (5.03%), and NNRTI-associated mutations in 63 patients (22.7%).After exclusion of polymorphic mutations in the NNRTI group, NNRTI resistance-associated mutations were identified in only nine patients (3.23%). The most frequently observed mutations were M46L for PIs, revertant-type T215D/N/S for NRTIs, and E138G/A and K103N for NNRTIs. Conclusions According to our findings, susceptibility rates of agents recommended for first-line therapy were 99.6% for TDF, 98.2% for FTC and 3TC, and 98.5% for DOR, whereas susceptibility rates for alternative treatment options were 83.8% for ATV, 99.6% for DRV, and 78.4% for RPV. Comparison of the observed DRM rates with the literature demonstrated that PI resistance was higher than reported global estimates, while NRTI and NNRTI resistance rates were consistent with international data. Antiretroviral drug resistance is well recognized as a key determinant of ART failure. Accordingly, prioritizing agents with a high genetic barrier in first-line therapy is essential for achieving sustained viral suppression and long-term treatment success.
Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 728 citations· ⚡54
Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, the results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduAug 17, 2026
A USAF cadet and a Lincoln Laboratory researcher found AI chatbots can help nontechnical service members produce viable software applications for their unique problems.