Catalogue Search | MBRL
Are you sure you want to remove the book from the shelf?
{{itemTitle}}
19,150
result(s) for
"Programmers"
Sort by:
Proving ground : the untold story of the six women who programmed the world's first modern computer
As the Cold War began, America's race for tech supremacy took off. Experts rushed to complete the top-secret computing research started during World War II, among them six gifted mathematicians: a patriotic Quaker, a Jewish bookworm, a Yugoslav genius, a native Gaelic speaker, a sophomore from the Bronx and a farmer's daughter from Missouri. Their mission? Program the world's first and only supercomputer - before any code or programming languages existed. 'Proving Ground' is the fascinating, forgotten story of the six brilliant women who launched modern computing.
BOOK
Toward a theory on programmer’s block inspired by writer’s block
Context
Programmer’s block, akin to writer’s block, is a phenomenon where capable programmers struggle to create code. Despite anecdotal evidence, no scientific studies have explored the relationship between programmer’s block and writer’s block.
Objective
The primary objective of this study is to study the presence of blocks during programming and their potential causes.
Method
We conducted semi-structured interviews with experienced programmers to capture their processes, the problems they face, and potential causes. Subsequently, we analyzed the responses through the lens of writing.
Results
We found that among the programmer’s problems during programming, several display strong similarities to writer’s block. Moreover, when investigating possible causes of such blocks, we found a strong relationship between programming and writing activities as well as typical writing strategies employed by programmers.
Conclusions
Strong similarities between programming and writing challenges, processes, and strategies confirm the existence of programmer’s block with similar causes to writer’s block. Thus, strategies from writing used to resolve blocks should be applicable in programming, helping developers to overcome phases of being stuck. Research at the intersection of both areas could lead to productivity gains through reduced developer downtimes.
Journal Article
Software engineer
\"Carefully leveled text and vibrant photographs introduce early readers to the work software engineers do and the preparation necessary for a computer science career. Includes infographics, an activity, glossary, and index\"-- Provided by publisher.
Book
Improving readability in automatic unit test generation
In object-oriented programming, quality assurance is commonly provided through writing unit tests, to exercise the operations of each class. If unit tests are created and maintained manually, this can be a time-consuming and laborious task. For this reason, automatic methods are often used to generate tests that seek to cover all paths of the tested code. Search may be guided by criteria that are opaque to the programmer, resulting in test sequences that are long and confusing. This has a negative impact on test maintenance. Once tests have been created, the job is not done: programmers need to reason about the tests throughout the lifecycle, as the tested software units evolve. Maintenance includes diagnosing failing tests (whether due to a software fault or an invalid test) and preserving test oracles (ensuring that checked assertions are still relevant). Programmers also need to understand the tests created for code that they did not write themselves, in order to understand the intent of that code. If generated tests cannot be easily understood, then they will be extremely difficult to maintain. The overall objective of this thesis is to reaffirm the importance of unit test maintenance; and to offer novel techniques to improve the readability of automatically generated tests. The first contribution is an empirical survey of 225 developers from different parts of the world, who were asked to give their opinions about unit testing practices and problems. The survey responses confirm that unit testing is considered important; and that there is an appetite for higher-quality automated test generation, with a view to test maintenance. The second contribution is a domain-specific model of unit test readability, based on human judgements. The model is used to augment automated unit test generation to produce test suites with both high coverage and improved readability. In evaluations, 30 programmers preferred our improved tests and were able to answer maintenance questions 14level of accuracy. The third contribution is a novel algorithm for generating descriptive test names that summarise API- level coverage goals. Test optimisation ensures that each test is short, bears a clear relation to the covered code, and can be readily identified by programmers. In evaluations, 47 programmers agreed with the choice of synthesised names and that these were as descriptive as manually chosen names. Participants were also more accurate and faster at matching generated tests against the tested code, compared to matching with manually-chosen test names.
Dissertation
Do Comments and Expertise Still Matter? An Experiment on Programmers' Adoption of AI-Generated JavaScript Code
This paper investigates the factors influencing programmers' adoption of AI-generated JavaScript code recommendations within the context of lightweight, function-level programming tasks. It extends prior research by (1) utilizing objective (as opposed to the typically self-reported) measurements for programmers' adoption of AI-generated code and (2) examining whether AI-generated comments added to code recommendations and development expertise drive AI-generated code adoption. We tested these potential drivers in an online experiment with 173 programmers. Participants were asked to answer some questions to demonstrate their level of development expertise. Then, they were asked to solve a LeetCode problem without AI support. After attempting to solve the problem on their own, they received an AI-generated solution to assist them in refining their solutions. The solutions provided were manipulated to include or exclude AI-generated comments (a between-subjects factor). Programmers' adoption of AI-generated code was gauged by code similarity between AI-generated solutions and participants' submitted solutions, providing a behavioral measurement of code adoption behaviors. Our findings revealed that, within the context of function-level programming tasks, the presence of comments significantly influences programmers' adoption of AI-generated code regardless of the participants' development expertise.
Paper
Modelos financieros con Excel
El contenido de esta obra tiene una orientación fundamentalmente práctica con actividades diseñadas para facilitar al lector/alumno la asimilación de los contenidos en aspectos como la gestión sanitaria y calidad asistencial para médicos. El Centro de Salud y el Equipo de Salud. Planes de Mejora de Calidad en Centros Sanitarios. Ejemplo de Implantación práctica de un Plan de Calidad. Sistemas de información en Atención Primaria. Conceptos de gestión Sanitaria: Producto Sanitario. Conceptos de Gestión sanitaria: Gestión de la atención. Planificación sanitaria. Gestión por Procesos Asistenciales Integrados. La Cartera de Servicios de Atención Primaria. Protocolización de la asistencia en Atención Primaria. Gestión administrativa-legal para médicos. Uso racional del medicamento. Razonamiento clínico y toma de decisiones. Actividades Administrativo-legales: Incapacidad Temporal.Actividades Administrativo-legales: Certificados médicos y documentos de interés judicial.
eBook
Girls who code : learn to code and change the world
An introductory book about coding with interviews and a look at women in the fields that require coding.
Book
Checkpoint-based rollback recovery in session programming
To react to unforeseen circumstances or amend abnormal situations in communication-centric systems, programmers are in charge of \"undoing\" the interactions which led to an undesired state. To assist this task, session-based languages can be endowed with reversibility mechanisms. In this paper we propose a language enriched with programming facilities to commit session interactions, to roll back the computation to a previous commit point, and to abort the session. Rollbacks in our language always bring the system to previous visited states and a rollback cannot bring the system back to a point prior to the last commit. Programmers are relieved from the burden of ensuring that a rollback never restores a checkpoint imposed by a session participant different from the rollback requester. Such undesired situations are prevented at design-time (statically) by relying on a decidable compliance check at the type level, implemented in MAUDE. We show that the language satisfies error-freedom and progress of a session.
Paper