
2025-07-11 09:50:11
Best Practices for Machine Learning-Assisted Protein Engineering
Fabio Herrera-Rocha, David Medina-Ortiz, Fabian Mauz, Juergen Pleiss, Mehdi D. Davari
https://arxiv.org/abs/2507.07547
Best Practices for Machine Learning-Assisted Protein Engineering
Fabio Herrera-Rocha, David Medina-Ortiz, Fabian Mauz, Juergen Pleiss, Mehdi D. Davari
https://arxiv.org/abs/2507.07547
Best practices are contextual.
https://www.garfieldtech.com/blog/best-practices
When Prompt Engineering Meets Software Engineering: CNL-P as Natural and Robust "APIs'' for Human-AI Interaction
Zhenchang Xing, Yang Liu, Zhuo Cheng, Qing Huang, Dehai Zhao, Daniel Sun, Chenhua Liu
https://arxiv.org/abs/2508.06942
Automated Visualization Makeovers with LLMs
Siddharth Gangwar, David A. Selby, Sebastian J. Vollmer
https://arxiv.org/abs/2508.05637 https://arxiv.org/pdf/…
Generative AI as a Safety Net for Survey Question Refinement
Erica Ann Metheney, Lauren Yehle
https://arxiv.org/abs/2509.08702 https://arxiv.org/pdf/2509.0…
»Crate Layout Best Practices: lib.rs, mod.rs, and src/bin«
Slowly, slowly, I'm learning what Rust uses for what in its coding.
🦀 https://dev.to/sgchris/crate-layout-best-practices-librs-modrs-and-srcbin-4abd
Issue Tracking Ecosystems: Context and Best Practices
Lloyd Montgomery
https://arxiv.org/abs/2507.06704 https://arxiv.org/pdf/2507.06…
Aligning LLMs for the Classroom with Knowledge-Based Retrieval -- A Comparative RAG Study
Amay Jain, Liu Cui, Si Chen
https://arxiv.org/abs/2509.07846 https://
Enhancing Quantum Software Development Process with Experiment Tracking
Mahee Gamage, Otso Kinanen, Jake Muff, Vlad Stirbu
https://arxiv.org/abs/2507.06990
Alt text - Why It's Important
- please use #AltText -
https://publish.obsidian.md/debbieohi/alt-text
Best practices for nonadiabatic molecular dynamics simulations
Antonio Prlj, Jack T. Taylor, Ji\v{r}\'i Jano\v{s}, Petr Slav\'i\v{c}ek, Federica Agostini, Basile F. E. Curchod
https://arxiv.org/abs/2508.05263
Fraudulent Publishing in the Mathematical Sciences
Ilka Agricola, Lynn Heller, Wil Schilders, Moritz Schubotz, Peter Taylor, Luis Vega
https://arxiv.org/abs/2509.07257 https://
GCVE-BCP-04 - Recommendations and Best Practices for ID Allocation version 1.1 published.
BCP Document https://gcve.eu/bcp/gcve-bcp-04/
PDF https://
At Berlin Buzzwords 2025, Kevin Liang discussed how Apache Solr/Lucene builds dense vector indexes and talked about how he and his team optimised their dense vector setup, sharing the challenges they faced and the best practices they learned along the way.
Watch the full session: https://youtu.be/cDiCX3mVAlQ?si=YWMkpEVpA-lWrH04
Berlin Buzzwords returns on 7-9 June 2026! Get 36% off with our Trust Us Ticket: https://tickets.plainschwarz.com/bbuzz26/c/8Hvk0ZvJA/
What doesn’t kill you makes you stronger: Do tougher practices equal tougher Cowboys? https://cowboyswire.usatoday.com/story/sports/nfl/cowboys/2025/08/01/tough-love-dallas-cowboys-brian-schottenheimer/85467254007/
Long; central Massachusetts colonial history
Today on a whim I visited a site in Massachusetts marked as "Huguenot Fort Ruins" on OpenStreetMaps. I drove out with my 4-year-old through increasingly rural central Massachusetts forests & fields to end up on a narrow street near the top of a hill beside a small field. The neighboring houses had huge lawns, some with tractors.
Appropriately for this day and this moment in history, the history of the site turns out to be a microcosm of America. Across the field beyond a cross-shaped stone memorial stood an info board with a few diagrams and some text. The text of the main sign (including typos/misspellings) read:
"""
Town Is Formed
Early in the 1680's, interest began to generate to develop a town in the area west of Natick in the south central part of the Commonwealth that would be suitable for a settlement. A Mr. Hugh Campbell, a Scotch merchant of Boston petitioned the court for land for a colony. At about the same time, Joseph Dudley and William Stoughton also were desirous of obtaining land for a settlement. A claim was made for all lands west of the Blackstone River to the southern land of Massachusetts to a point northerly of the Springfield Road then running southwesterly until it joined the southern line of Massachusetts.
Associated with Dudley and Stoughton was Robert Thompson of London, England, Dr. Daniel Cox and John Blackwell, both of London and Thomas Freak of Hannington, Wiltshire, as proprietors. A stipulation in the acquisition of this land being that within four years thirty families and an orthodox minister settle in the area. An extension of this stipulation was granted at the end of the four years when no group large enough seemed to be willing to take up the opportunity.
In 1686, Robert Thompson met Gabriel Bernor and learned that he was seeking an area where his countrymen, who had fled their native France because of the Edict of Nantes, were desirous of a place to live. Their main concern was to settle in a place that would allow them freedom of worship. New Oxford, as it was the so-named, at that time included the larger part of Charlton, one-fourth of Auburn, one-fifth of Dudley and several square miles of the northeast portion of Southbridge as well as the easterly ares now known as Webster.
Joseph Dudley's assessment that the area was capable of a good settlement probably was based on the idea of the meadows already established along with the plains, ponds, brooks and rivers. Meadows were a necessity as they provided hay for animal feed and other uses by the settlers. The French River tributary books and streams provided a good source for fishing and hunting. There were open areas on the plains as customarily in November of each year, the Indians burnt over areas to keep them free of underwood and brush. It appeared then that this area was ready for settling.
The first seventy-five years of the settling of the Town of Oxford originally known as Manchaug, embraced three different cultures. The Indians were known to be here about 1656 when the Missionary, John Eliott and his partner Daniel Gookin visited in the praying towns. Thirty years later, in 1686, the Huguenots walked here from Boston under the guidance of their leader Isaac Bertrand DuTuffeau. The Huguenot's that arrived were not peasants, but were acknowledged to be the best Agriculturist, Wine Growers, Merchant's, and Manufacter's in France. There were 30 families consisting of 52 people. At the time of their first departure (10 years), due to Indian insurrection, there were 80 people in the group, and near their Meetinghouse/Church was a Cemetery that held 20 bodies. In 1699, 8 to 10 familie's made a second attempt to re-settle, failing after only four years, with the village being completely abandoned in 1704.
The English colonist made their way here in 1713 and established what has become a permanent settlement.
"""
All that was left of the fort was a crumbling stone wall that would have been the base of a higher wooden wall according to a picture of a model (I didn't think to get a shot of that myself). Only trees and brush remain where the multi-story main wooden building was.
This story has so many echoes in the present:
- The rich colonialists from Boston & London agree to settle the land, buying/taking land "rights" from the colonial British court that claimed jurisdiction without actually having control of the land. Whether the sponsors ever actually visited the land themselves I don't know. They surely profited somehow, whether from selling on the land rights later or collecting taxes/rent or whatever, by they needed poor laborers to actually do the work of developing the land (& driving out the original inhabitants, who had no say in the machinations of the Boston court).
- The land deal was on condition that there capital-holders who stood to profit would find settlers to actually do the work of colonizing. The British crown wanted more territory to be controlled in practice not just in theory, but they weren't going to be the ones to do the hard work.
- The capital-holders actually failed to find enough poor suckers to do their dirty work for 4 years, until the Huguenots, fleeing religious persecution in France, were desperate enough to accept their terms.
- Of course, the land was only so ripe for settlement because of careful tending over centuries by the natives who were eventually driven off, and whose land management practices are abandoned today. Given the mention of praying towns (& dates), this was after King Phillip's war, which resulted in at least some forced resettlement of native tribes around the area, but the descendants of those "Indians" mentioned in this sign are still around. For example, this is the site of one local band of Nipmuck, whose namesake lake is about 5 miles south of the fort site: #LandBack.
Dredging up recollections of my experience as R6RS editor for my PLSS talk tomorrow.
https://2025.ecoop.org/details/plss-2025-papers/8/Do-Programming-Languages-Fulfill-Requirements-Should-They-
SHERPA: A Model-Driven Framework for Large Language Model Execution
Boqi Chen, Kua Chen, Jos\'e Antonio Hern\'andez L\'opez, Gunter Mussbacher, D\'aniel Varr\'o, Amir Feizpour
https://arxiv.org/abs/2509.00272
Im Rahmen der Vorbereitung auf ein Vorstellungsgespräch habe ich mich in ein sog. Framework aus Best Practices für die IT-Branche eingearbeitet und dabei Verblüffendes festgestellt:
Im Grunde sind dies Dinge des gesunden Menschenverstands, die jemand mal zusammengestellt hat. Bzw. Dinge, die eine aufmerksame Mitarbeiterin, die seit ein paar Jahre im Arbeitsleben steht (egal wo), kennen sollte. 1/2
So #Gentoo #Python eclasses are pretty modern, in the sense that they tend to follow the best practices and standards, and eventually deal with deprecations. Nevertheless, they have a long history and carry quite some historical burden, particularly regarding to naming.
The key point is that the eclasses were conceived as a replacement for the old eclasses: "distutils" and "python". Hence, much like we revision ebuilds, I've named the matching eclasses "distutils-r1" and "python-r1". For consistency, I've also used the "-r1" suffix for the remaining eclasses introduced at the time: "python-any-r1", "python-single-r1" and "python-utils-r1" — even though there were never "r0"s.
It didn't take long to realize my first mistake. I've made the multi-impl eclass effectively the "main" eclass, probably largely inspired by the previous Gentoo recommendations. However, in the end I've found out that for the most use cases (i.e. where "distutils-r1" is not involved), there is no real need for multi-impl, and it makes things much harder. So if I were naming them today, I would have named it "python-multi", to indicate the specific use case — and either avoid designating a default at all, or made "python-single" the default.
What aged even worse is the "distutils-r1" eclass. Admittedly, back when it was conceived, distutils was still largely a thing — and there were people (like me) who avoided unnecessary dependency on setuptools. Of course, nowadays it has been entirely devoured by setuptools, and with #PEP517 even "setuptools" wouldn't be a good name anymore. Nowadays, people are getting confused why they are supposed to use "distutils-r1" for, say, Hatchling.
Admittedly, this is something I could have done differently — PEP517 support was a major migration, and involved an explicit switch. Instead of adding DISTUTILS_USE_PEP517 (what a self-contradictory name) variable, I could have forked the eclass. Why didn't I do that? Because there used to be a lot of code shared between the two paths. Of course, over time they diverged more, and eventually I've dropped the legacy support — but the opportunity to rename was lost.
In fact, as a semi-related fact, I've recognized another design problem with the eclass earlier — I should have gone for two eclasses rather than one: a "python-phase" eclass with generic sub-phase support, and a "distutils" (or later "python-pep517") implementing default sub-phases for the common backends. And again, this is precisely how I could have solved the code reuse problem when I introduced PEP517 support.
But then, I didn't anticipate how the eclasses would end up looking like in the end — and I can't really predict what new challenges the Python ecosystem is going to bring us. And I think it's too late to rename or split stuff — too much busywork on everyone.
Green Computing: The Ultimate Carbon Destroyer for a Sustainable Future
Sayed Mahbub Hasan Amiri, Prasun Goswami, Md. Mainul Islam, Mohammad Shakhawat Hossen, Marzana Mithila, Naznin Akter
https://arxiv.org/abs/2508.00153
Best Practices and Considerations for Child Speech Corpus Collection and Curation in Educational, Clinical, and Forensic Scenarios
John Hansen, Satwik Dutta, Ellen Grand
https://arxiv.org/abs/2507.12870
Breaking Out from the TESSERACT: Reassessing ML-based Malware Detection under Spatio-Temporal Drift
Theo Chow, Mario D'Onghia, Lorenz Linhardt, Zeliang Kan, Daniel Arp, Lorenzo Cavallaro, Fabio Pierazzi
https://arxiv.org/abs/2506.23814
Recommendations for Best Practices for Data Preservation and Open Science in HEP
Simone Campana (CERN, Switzerland), Irakli Chakaberia (Lawrence Berkeley National Laboratory, USA), Gang Chen (Institute of High Energy Physics, China), Cristinel Diaconu (Centre de Physique des Particules de Marseille CPPM, France, CNRS/IN2P3 and Aix-Marseille Universit\'e, France), Caterina Doglioni (University of Manchester, UK), Dillon S. Fitzgerald (University of Michigan, USA), Vincent Garonne (B…
The Protesters' Guide to #Smartphone #Security
https://www.
CI/CD #Pipeline #Architecture: Complete Guide to Building Robust CI and CD Pipelines
https://
🌟 New SIGs Spotlight: SIG-AI 🌟
A new space for collaboration on Artificial Intelligence within the NREN community is here.
SIG-AI brings the Research & Education community together to share expertise, best practices, and explore practical use cases of AI in NREN context—from cybersecurity and High-Performance Computing (HPC) to network automation and next-generation networks.
📖 For more insights, read the full interview with Leonie Schäfer (@…
"DH Spaces: Freie Schaffensräume als multifunktionale Orte an Bibliotheken"
#DigitalHumanities
Optimal control driven functional electrical stimulation: A scoping review
Kevin Co, Micka\"el Begon, Fran\c{c}ois Bailly, Florent Moissenet
https://arxiv.org/abs/2508.02899
How to secure your phone before joining a protest
✅ The Protesters' Guide to Smartphone Security
https://www.privacyguides.org/articles/2025/01/23/activists-guide-securing-your-smartphone/
Practice Points: Best from Cowboys' final padded practice in Oxnard https://www.dallascowboys.com/news/practice-points-best-from-cowboys-final-padded-practice-in-oxnard
Virtual Reality User Interface Design: Best Practices and Implementation
Esin Mehmedova, Santiago Berrezueta-Guzman, Stefan Wagner
https://arxiv.org/abs/2508.09358 https://
Modeling the Mass Distribution and Gravitational Potential of Nearby Disk Galaxies: Implications for the ISM Dynamical Equilibrium
Vivek Vijayakumar, Jiayi Sun, Eve C. Ostriker, Enrico M. Di Teodoro, Konstantin Haubner, Chang-Goo Kim, Adam K. Leroy, Miguel Querejeta
https://arxiv.org/abs/2506.22381…
Meta-Metrics and Best Practices for System-Level Inference Performance Benchmarking
Shweta Salaria, Zhuoran Liu, Nelson Mimura Gonzalez
https://arxiv.org/abs/2508.10251 https://…
Tool-Assisted Conformance Checking to Reference Process Models
Bernhard Rumpe, Max Stachon, Sebastian St\"uber, Valdes Voufo
https://arxiv.org/abs/2508.00738 https://
The Perils of Chart Deception: How Misleading Visualizations Affect Vision-Language Models
Ridwan Mahbub, Mohammed Saidul Islam, Md Tahmid Rahman Laskar, Mizanur Rahman, Mir Tafseer Nayeem, Enamul Hoque
https://arxiv.org/abs/2508.09716
Practice Points: Best from Cowboys' final padded practice in Oxnard https://www.dallascowboys.com/news/practice-points-best-from-cowboys-final-padded-practice-in-oxnard
Are you running open-source databases on Kubernetes? At Berlin Buzzwords 2025, Peter Zaitsev discussed best practices for high availability, security, backups, and disaster recovery. Discover key pitfalls to avoid and learn how Operators can simplify database management for MySQL, MongoDB, and PostgreSQL in Kubernetes environments.
Watch the full session:
A Risk Assessment Framework for Digital Identification Systems
Allison Woodruff, Dirk Balfanz, Will Drewry, Mariana Raykova
https://arxiv.org/abs/2507.14755
SDBench: A Comprehensive Benchmark Suite for Speaker Diarization
Eduardo Pacheco, Atila Orhon, Berkin Durmus, Blaise Munyampirwa, Andrey Leonov
https://arxiv.org/abs/2507.16136
Our partner conference, MICES – Mix-Camp E-Commerce Search, takes place on June 18th at TUECHTIG in Berlin. Focusing on e-commerce search, MICES brings together experts from various fields such as IT, product management, UX design, search management, information retrieval, data science and search engine vendors to discuss challenges, share ideas, best practices and case studies in e-commerce search.
Register for free and learn more here:
Using LLMs and Essence to Support Software Practice Adoption
Sonia Nicoletti, Paolo Ciancarini
https://arxiv.org/abs/2508.16445 https://arxiv.org/pdf/2508.…
MCP2OSC: Parametric Control by Natural Language
Yuan-Yi Fan
https://arxiv.org/abs/2508.10414 https://arxiv.org/pdf/2508.10414
An Empirical Study of Complexity, Heterogeneity, and Compliance of GitHub Actions Workflows
Edward Abrokwah, Taher A. Ghaleb
https://arxiv.org/abs/2507.18062 https://
Ten Essential Guidelines for Building High-Quality Research Software
Nasir U. Eisty, David E. Bernholdt, Alex Koufos, David J. Luet, Miranda Mundt
https://arxiv.org/abs/2507.16166
WIP: Leveraging LLMs for Enforcing Design Principles in Student Code: Analysis of Prompting Strategies and RAG
Dhruv Kolhatkar, Soubhagya Akkena, Edward F. Gehringer
https://arxiv.org/abs/2508.11717
MetaLint: Generalizable Idiomatic Code Quality Analysis through Instruction-Following and Easy-to-Hard Generalization
Atharva Naik, Lawanya Baghel, Dhakshin Govindarajan, Darsh Agrawal, Daniel Fried, Carolyn Rose
https://arxiv.org/abs/2507.11687