Analyzing online retrospective experience reports of psychedelic use can provide valuable insight into their acute subjective effects. Such reports are unexplored in relation to mystical states, which are thought to be a therapeutic mechanism within psychedelic-assisted psychotherapy. We created a set of words that, when encountered in an experience report, indicate the occurrence of mystical elements within the experience. We used the Shroomery.org website to retrieve 7317 publicly available retrospective psychedelic experience reports of psychedelic use, primarily of psilocybin, and have a designated experience intensity level self-assessed by the text authors during submission of the report. We counted the mystical language words using Linguistic Inquiry and Word Count (LIWC) software and additionally performed sentiment analysis of all reports. We found that the occurrence of mystical language grew with increased self-reported experience intensity. We also found that negative sentiment increased, and positive sentiment decreased as self-reported psychedelic experience intensity increased. These two findings raise the question of whether mystical experiences can co-exist with challenging elements within the psychedelic experience, a consideration for future qualitative studies. We present a new mystical language dictionary measure for further use and expansion, with some suggestions on how it can be used in future studies.
22 November 2023 in Empirical Software Engineering
Increasing code velocity is a common goal for a variety of software projects. The efficiency of the code review process significantly impacts how fast the code gets merged into the final product and reaches the customers. We conducted a qualitative survey to study the code velocity-related beliefs and practices in place. We analyzed 75 completed surveys from SurIndustryDevs participants from the industry and 36 from the open-source community. Our critical findings are (a) the industry and open-source community hold a similar set of beliefs, (b) quick reaction time is of utmost importance and applies to the tooling infrastructure and the behavior of other engineers, (c) time-to-merge is the essential code review metric to improve, (d) engineers are divided about the benefits of increased code velocity for their career growth, (e) the controlled application of the commit-then-review model can increase code velocity. Our study supports the continued need to invest in and improve code velocity regardless of the underlying organizational ecosystem.
An accepted practice to decrease applications' memory usage is to reduce the amount and frequency of memory allocations. Factors such as (a) the prevalence of out-of-memory (OOM) killers, (b) memory allocations in modern programming languages done implicitly, (c) overcommitting being a default strategy in the Linux kernel, and (d) the rise in complexity and terminology related to memory management makes the existing guidance inefficient. The industry needs detailed guidelines for optimizing memory usage targeting specific operating systems (OS) and programming language types.
Engineers build large software systems for multiple architectures, operating systems, and configurations. A set of inconsistent or missing compiler flags generates code that catastrophically impacts the system's behavior. In the authors' industry experience, defects caused by an undesired combination of compiler flags are common in nontrivial software projects. We are unaware of any build and CI/CD systems that track how the compiler produces a specific binary in a structured manner. We postulate that a queryable database of how the compiler compiled and linked the software system will help to detect defects earlier and reduce the debugging time.
In 2024, the Linux kernel became its own Common Vulnerabilities and Exposures (CVE) Numbering Authority (CNA), formalizing how kernel vulnerabilities are identified and tracked. We analyze the anatomy and dynamics of kernel CVEs using metadata, associated commits, and patch latency to understand what drives patching. Results show that severity and Common Vulnerability Scoring System (CVSS) metrics have a negligible association with patch latency, whereas kernel recency is a reasonable predictor in survival models. Kernel developers fix newer kernels sooner, while older ones retain unresolved CVEs. Commits introducing vulnerabilities are typically broader and more complex than their fixes, though often only approximate reconstructions of development history. The Linux kernel remains a unique open-source project—its CVE process is no exception.