Immediate Search in the IDE as an Example of Socio-Technical Congruence in Search-Driven Development

Search-driven development is mainly concerned with code reuse but also with code navigation and debugging. In this essay we look at search-driven navigation in the IDE. We consider Smalltalk-80 as an example of a programming system with search-driven navigation capabilities and explore its human factors. We present how immediate search results lead to a user experience of code browsing rather than one of waiting for and clicking through search results. We explore the socio-technical congruence of immediate search, ie unification of tasks and breakpoints with method calls, which leads to simpler and more extensible development tools. Eventually we conclude with remarks on the socio-technical congruence of search-driven development.

Embedding Spatial Software Visualization in the IDE: an Exploratory Study

Software visualization can be of great use for understanding and exploring a software system in an intuitive manner. Spatial representation of software is a promising approach of increasing interest. However, little is known about how developers interact with spatial visualizations that are embedded in the IDE. In this paper, we present a pilot study that explores the use of Software Cartography for program comprehension of an unknown system. We investigated whether developers establish a spatial memory of the system, whether clustering by topic offers a sound base layout, and how developers interact with maps. We report our results in the form of observations, hypotheses, and implications. Key findings are a) that developers made good use of the map to inspect search results and call graphs, and b) that developers found the base layout surprising and often confusing. We conclude with concrete advice for the design of embedded software maps

Exploiting Runtime Information in the IDE

Developers rely on the mechanisms provided by their IDE to browse and navigate a large software system. These mechanisms are usually based purely on a system's static source code. The static perspective, however, is not enough to understand an object-oriented program's behavior, in particular if implemented in a dynamic language. We propose to enhance IDEs with a program's runtime information (eg. message sends and type information) to support program comprehension through precise navigation and informative browsing. To precisely specify the type and amount of runtime data to gather about a system under development, dynamically and on demand, we adopt a technique known as partial behavioral reflection. We implemented navigation and browsing enhancements to an IDE that exploit this runtime information in a prototype called Hermion. We present preliminary validation of our experimental enhanced IDE by asking developers to assess its usefulness to understand an unfamiliar software system.

Tackling Software Navigation Issues of the Smalltalk IDE

The IDE used in most Smalltalk dialects such as Pharo, Squeak or Cincom Smalltalk did not evolve significantly over the last years, if not to say decades. For other languages, for instance Java, the available IDEs made tremendous progress as Eclipse or NetBeans illustrate. While the Smalltalk IDE served as an exemplar for many years, other IDEs caught up or even overtook the erstwhile leader in terms of feature-richness, usability, or code navigation facilities. In this paper we first analyze the difficulty of software navigation in the Smalltalk IDE and second illustrate with concrete examples the features we added to the Smalltalk IDE to fill the gap to modern IDEs and to provide novel, improved means to navigate source space. We show that thanks to the agility and dynamics of Smalltalk, we are able to extend and enhance with reasonable effort the Smalltalk IDE to better support software navigation, program comprehension, and software maintenance in general. One such support is the integration of dynamic information into the static source views we are familiar with. Other means include easing the access to static information (for instance by better arranging important packages) or helping developers re-locating artifacts of interest (for example with a categorization system such as smart groups).

Querying Runtime Information in the IDE

Code queries focus mainly on the static structure of a system. To comprehend the dynamic behavior of a system however, a software engineer needs to be able to reason about the dynamics of this system, for instance by querying a database of dynamic information. Such a querying mechanism should be directly available in the IDE where the developers implements, navigates and reasons about the software system. We propose (i) concepts to gather dynamic information, (ii) the means to query this information, and (iii) tools and techniques to integrate querying of dynamic information in the IDE, including the presentation of results generated by queries.

Assessing efficacy of different nucleos(t)ide backbones in NNRTI-containing regimens in the Swiss HIV Cohort Study.

BACKGROUND The most recommended NRTI combinations as first-line antiretroviral treatment for HIV-1 infection in resource-rich settings are tenofovir/emtricitabine, abacavir/lamivudine, tenofovir/lamivudine and zidovudine/lamivudine. Efficacy studies of these combinations also considering pill numbers, dosing frequencies and ethnicities are rare. METHODS We included patients starting first-line combination ART (cART) with or switching from first-line cART without treatment failure to tenofovir/emtricitabine, abacavir/lamivudine, tenofovir/lamivudine and zidovudine/lamivudine plus efavirenz or nevirapine. Cox proportional hazards regression was used to investigate the effect of the different NRTI combinations on two primary outcomes: virological failure (VF) and emergence of NRTI resistance. Additionally, we performed a pill burden analysis and adjusted the model for pill number and dosing frequency. RESULTS Failure events per treated patient for the four NRTI combinations were as follows: 19/1858 (tenofovir/emtricitabine), 9/387 (abacavir/lamivudine), 11/344 (tenofovir/lamivudine) and 45/1244 (zidovudine/lamivudine). Compared with tenofovir/emtricitabine, abacavir/lamivudine had an adjusted HR for having VF of 2.01 (95% CI 0.86-4.55), tenofovir/lamivudine 2.89 (1.22-6.88) and zidovudine/lamivudine 2.28 (1.01-5.14), whereas for the emergence of NRTI resistance abacavir/lamivudine had an HR of 1.17 (0.11-12.2), tenofovir/lamivudine 11.3 (2.34-55.3) and zidovudine/lamivudine 4.02 (0.78-20.7). Differences among regimens disappeared when models were additionally adjusted for pill burden. However, non-white patients compared with white patients and higher pill number per day were associated with increased risks of VF and emergence of NRTI resistance: HR of non-white ethnicity for VF was 2.85 (1.64-4.96) and for NRTI resistance 3.54 (1.20-10.4); HR of pill burden for VF was 1.41 (1.01-1.96) and for NRTI resistance 1.72 (0.97-3.02). CONCLUSIONS Although VF and emergence of resistance was very low in the population studied, tenofovir/emtricitabine appears to be superior to abacavir/lamivudine, tenofovir/lamivudine and zidovudine/lamivudine. However, it is unclear whether these differences are due to the substances as such or to an association of tenofovir/emtricitabine regimens with lower pill burden.

Ringier (Familie)

Famille de pasteurs, politiciens et entrepreneurs de Zofingue, attestée pour la première fois en 1527, lorsque leur aïeul Jean, tonnelier originaire de Nîmes, obtint la bourgeoisie de Zofingue. Michael (1521-1605), avoyer, l'un de ses cinq fils, est l'ancêtre de la branche des imprimeurs et éditeurs. Après lui, de nombreux R. consolidèrent durablement l'influence de la famille. A partir du XVIIIe s., divers membres firent des carrières politiques, tels Samuel (1706-1786), avoyer, et Rudolf Friedrich (1805-1886), président de la ville. Les R. furent aussi très liés à l'Eglise. Le fils de Michael, Moritz (1557-1615), fut pasteur et doyen à Zofingue. Jusqu'au XIXe s., la famille compta une trentaine d'ecclésiastiques, essentiellement des pasteurs officiant sur le territoire bernois, tels Johann Heinrich ( -> 3) et Michael ( -> 8). Les conseillers Beat (1712-1778) et Niklaus (1734-1766) furent les premiers R. actifs dans la production protoindustrielle de drap. D'autres négociants suivirent jusqu'au milieu du XIXe s. L'architecte Niklaus Emanuel (1744-1815) construisit l'hôtel de ville de Zofingue (1792-1795) de style baroque tardif. Johann Rudolf ( -> 4) se distingua sous la République helvétique (1798-1803). Samuel (1767-1826), conseiller municipal de Zofingue, créa les armoiries du canton d'Argovie en 1803. Les R. s'affirmèrent sur le plan cantonal avec Karl Ludwig ( -> 6), chancelier, et Arnold ( -> 1), conseiller d'Etat et plusieurs fois landamman, et sur le plan fédéral avec Johann Rudolf ( -> 5), conseiller national, et Gottlieb ( -> 2), conseiller aux Etats et chancelier de la Confédération. Johann Rudolf (1803-1874) fonda, en 1833, l'imprimerie Ringier à Zofingue, reprise par son fils Franz Emil (1837-1898). A partir de 1898, Paul August ( -> 9), représentant de la troisième génération d'imprimeurs, agrandit l'entreprise dont il fit la principale imprimerie et maison d'édition de Suisse. Cette expansion se poursuivit après 1960 sous son fils Hans (1906-2003). Avec les fils de celui-ci, Christoph (naissance1941, dans la firme jusqu'en 1991) et Michael (naissance1949), Ringier devint, à partir de 1985, une entreprise multinationale et multimédia. Bibliographie – F. Schoder, Ortsbürger von Zofingen, 1962 – P. Meier, T. Häussler, Zwischen Masse, Markt und Macht, 2009

Spy: A Flexible Code Profiling Framework

Code profiling is an essential activity to increase software quality. It is commonly employed in a wide variety of tasks, such as supporting program comprehension, determining execution bottlenecks, and assessing code coverage by unit tests. Spy is an innovative framework to easily build profilers and visualize profiling information. The profiling information is obtained by inserting dedicated code before or after method execution. The gathered profiling information is structured in line with the application structure in terms of packages, classes, and methods. Spy has been instantiated on four occasions so far. We created profilers dedicated to test coverage, time execution, type feedback, and profiling evolution across version. We also integrated Spy in the Pharo IDE. Spy has been implemented in the Pharo Smalltalk programming language and is available under the MIT license.

Systematic review of medication safety assessment methods

Purpose The accuracy, efficiency, and efficacy of four commonly recommended medication safety assessment methodologies were systematically reviewed. Methods Medical literature databases were systematically searched for any comparative study conducted between January 2000 and October 2009 in which at least two of the four methodologies—incident report review, direct observation, chart review, and trigger tool—were compared with one another. Any study that compared two or more methodologies for quantitative accuracy (adequacy of the assessment of medication errors and adverse drug events) efficiency (effort and cost), and efficacy and that provided numerical data was included in the analysis. Results Twenty-eight studies were included in this review. Of these, 22 compared two of the methodologies, and 6 compared three methods. Direct observation identified the greatest number of reports of drug-related problems (DRPs), while incident report review identified the fewest. However, incident report review generally showed a higher specificity compared to the other methods and most effectively captured severe DRPs. In contrast, the sensitivity of incident report review was lower when compared with trigger tool. While trigger tool was the least labor-intensive of the four methodologies, incident report review appeared to be the least expensive, but only when linked with concomitant automated reporting systems and targeted follow-up. Conclusion All four medication safety assessment techniques—incident report review, chart review, direct observation, and trigger tool—have different strengths and weaknesses. Overlap between different methods in identifying DRPs is minimal. While trigger tool appeared to be the most effective and labor-efficient method, incident report review best identified high-severity DRPs.

Two- to 9-year clinical results of alumina ceramic-on-ceramic THA

From June 1997 to June 2003 we performed 194 total hip arthroplasties on 173 patients using alumina ceramic-on-ceramic bearings as part of a prospective United States Food and Drug Administration/Investigational Device Exemption study. The average patient age at surgery was 49.9 years. Minimum followup time was 2 years (mean 4.3 years, range 2-9 years). We evaluated survival rate, implant- and nonimplant-related complications. Clinical outcomes included the Merle d'Aubigné score. We assessed radiographs for signs of osteolysis, component loosening, and implant wear. No patients had osteolysis and there were no hip dislocations. Implant survivorship for all hips with aseptic revision of any component was 96% (CI, 91-100) at 9 year; survivorship for hips without prior surgery was 99.3%, (CI, 98-100). There was a 1.7% incidence of implant-related complications. Our data help confirm two United States FDA/IDE studies on alumina ceramic-on-ceramic total hip arthroplasty that reported low aseptic revision rates and low revision rates for instability. Total hip arthroplasty using alumina ceramic-on-ceramic implants is a safe and reliable procedure in the comparably young and active patient.

Supporting Task-oriented Navigation in IDEs with Configurable HeatMaps

Mainstream IDEs generally rely on the static structure of a software project to support browsing and navigation. We propose HeatMaps, a simple but highly configurable technique to enrich the way an IDE displays the static structure of a software system with additional kinds of information. A heatmap highlights software artifacts according to various metric values, such as bright red or pale blue, to indicate their potential degree of interest. We present a prototype system that implements heatmaps, and we describe an initial study that assesses the degree to which different heatmaps effectively guide developers in navigating software.