20171122 02 - Engage developers to use better coding practices

Nov 23, 20172 likes269 views

The document discusses using gamification and personalized feedback to encourage developers to write cleaner code with fewer bugs through improved coding practices like testing and by increasing engagement with an industry partner's tool called Themis. Interviews would provide data for the design study on how gamification and competition could motivate self-evaluation and learning.

20171122 02 - Engage developers to use better coding practices

The document outlines 5 reasons why companies should incorporate work sample coding tests into their recruitment process. The reasons are: 1) They mirror real-life tasks unlike general programming tests. 2) They are objective and done before interviews to reduce bias. 3) Candidates are not watched which reduces stress. 4) They are automated so tests can be quickly scored. 5) They save time for HR and IT teams by prescreening candidates before interviews.

Sap abap crm consultant (3 8yrs exp) - immediate joiners onlyKALYAN Chakravarthy

20171122 03 - Les tests de performance en environnement DevOpsLeClubQualiteLogicielle

20171122 04 - Automatisation - formation et certificationsLeClubQualiteLogicielle

20171122 01 - REX : Intégration et déploiement continu chez EngieLeClubQualiteLogicielle

20171122 - Accueil Club Qualité Logicielle LeClubQualiteLogicielle

20151013 - Crédit Mutuel ARKEA : mise en place d'une traçabilité outillée des...LeClubQualiteLogicielle

20151013 - Agirc arrco : Behavior driven developmentLeClubQualiteLogicielle

20151013 - Réduire les coûts des tests de performance ?LeClubQualiteLogicielle

20151013 - Accueil Club Qualité Logicielle LeClubQualiteLogicielle

20151013 - DevOps et qualification continueLeClubQualiteLogicielle

20140410 - Cartographie applicative multi-technologies et analyse d'impactLeClubQualiteLogicielle

20140410 - Implémentation de squash TM-TA - Architecture et méthodologieLeClubQualiteLogicielle

20140410 - Gestion des identités, traçabilité des accés - Analogie avec la qu...LeClubQualiteLogicielle

This document describes an IT security controls framework called the Control Factory. The Control Factory aims to apply principles of software quality and manufacturing to the governance and production of IT security controls. It describes the Control Factory approach which involves formalizing requirements, producing controls, executing campaigns, and reporting results. The key objectives are to increase consistency, quality, and productivity of security controls through automation, reuse of components, and dividing the controls process into discrete services.

20140410 - Choisir et implanter un outil de testLeClubQualiteLogicielle

20130113 02 - TMMI, un modèle pour rentabiliser une organisation de test et a...LeClubQualiteLogicielle

20130113 06 - Travaux de recherche sur la corrélation entre qualité du code e...LeClubQualiteLogicielle

20130113 05 - Inspection continue et roadmap 2013LeClubQualiteLogicielle

This document discusses SonarSource, an open source platform for continuous inspection of code quality and maintainability. Some key facts about SonarSource include that it has over 6,000 downloads per month and over 220,000 total downloads. The document outlines benefits of maintainability management such as lower costs and easier maintenance. It also contrasts the traditional tooling market of being niche and high cost versus SonarSource being affordable and continuous. Strengths of the SonarSource platform include total cost of ownership, functional coverage, and integration. The document shows programming language support and previews upcoming features like cartography/impact analysis.

20130113 04 - Tests d'integration et virtualisation - La vision IBMLeClubQualiteLogicielle

20130523 06 - The mathematics the way algorithms think / the mathematics the ...LeClubQualiteLogicielle

This document summarizes Thomas McCabe's presentation on quantifying shifts in consciousness mathematically. McCabe introduces the Dihedral complexity, which quantifies perspectives inherent to thoughts in the same way the McCabe complexity quantifies algorithm paths. He discusses how algorithm complexity impacts software and how consciousness complexity could have emerging computer science applications. The talk traces the mathematical derivation of algorithmic and consciousness complexity and discusses increasing complexity of consciousness.

20130523 05 - Cyclomatic complexityLeClubQualiteLogicielle

This document discusses cyclomatic complexity, a measure of the number of linearly independent paths through a program's source code. It is defined as the number of edges minus the number of nodes plus the number of connected components. Testing all possible paths is impossible due to the exponential increase, so code coverage tools focus on testing requirements, implementations, branches, and cyclomatic paths. The document provides an example graph with 10 nodes, 6 edges, and a cyclomatic complexity of 5. It discusses using the cyclomatic complexity measure for testing, design validation, reuse, and security analysis.

20130523 04 - Grille d'évaluation - Gestion du patrimoine de testLeClubQualiteLogicielle

20130523 02 - BREDForge foundations - Gense et perspectivesLeClubQualiteLogicielle

This document summarizes the evolution of Bredforge's software development foundations between 2002 and 2014. It describes the progression from an initial Java architecture in 2002 to establishing continuous integration and inspection practices by 2013-2014. The goals in early periods focused on the software architecture and development environment. Later goals centered around providing assistance to developers, establishing practices for Cobol development, continuous integration using Jenkins, and introducing tools for unit testing and code quality. By 2014 the development environment integrated assistance, continuous integration, inspection, and new goals around unit testing and a common environment.

20131210 - Rex Bouygues Telecom - Integration et inspection continue avec RTC...LeClubQualiteLogicielle

20131210 - Gouvernance et conformité open source : à la recherche d'une quali...LeClubQualiteLogicielle

20120124 05 - Le Model-based Testing aujourd'hui (Inria)LeClubQualiteLogicielle

20120124 04 - Retour d'expérience sur la mise en oeuvre de SquashLeClubQualiteLogicielle

20120124 02 - Enjeux et défis de l'integration de composants open source dans...LeClubQualiteLogicielle

Top 10 Client Portal Software Solutions for 2025.docxPortli

Explaining GitHub Actions Failures with Large Language Models Challenges, In...ssuserb14185

GitHub Actions (GA) has become the de facto tool that developers use to automate software workflows, seamlessly building, testing, and deploying code. Yet when GA fails, it disrupts development, causing delays and driving up costs. Diagnosing failures becomes especially challenging because error logs are often long, complex and unstructured. Given these difficulties, this study explores the potential of large language models (LLMs) to generate correct, clear, concise, and actionable contextual descriptions (or summaries) for GA failures, focusing on developers’ perceptions of their feasibility and usefulness. Our results show that over 80% of developers rated LLM explanations positively in terms of correctness for simpler/small logs. Overall, our findings suggest that LLMs can feasibly assist developers in understanding common GA errors, thus, potentially reducing manual analysis. However, we also found that improved reasoning abilities are needed to support more complex CI/CD scenarios. For instance, less experienced developers tend to be more positive on the described context, while seasoned developers prefer concise summaries. Overall, our work offers key insights for researchers enhancing LLM reasoning, particularly in adapting explanations to user expertise. https://arxiv.org/abs/2501.16495

More Related Content

More from LeClubQualiteLogicielle (20)