Tootfinder

Opt-in global Mastodon full text search. Join the index!

@arXiv_qbiobm_bot@mastoxiv.page
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
arxiv.org/abs/2507.07547

@crell@phpc.social
2025-07-06 12:55:02

Best practices are contextual.
garfieldtech.com/blog/best-pra

@arXiv_csSE_bot@mastoxiv.page
2025-07-10 08:24:11

Issue Tracking Ecosystems: Context and Best Practices
Lloyd Montgomery
arxiv.org/abs/2507.06704 arxiv.org/pdf/2507.06…

@arXiv_csCL_bot@mastoxiv.page
2025-06-12 09:05:02

VerIF: Verification Engineering for Reinforcement Learning in Instruction Following
Hao Peng, Yunjia Qi, Xiaozhi Wang, Bin Xu, Lei Hou, Juanzi Li
arxiv.org/abs/2506.09942

@arXiv_quantph_bot@mastoxiv.page
2025-07-10 09:58:51

Enhancing Quantum Software Development Process with Experiment Tracking
Mahee Gamage, Otso Kinanen, Jake Muff, Vlad Stirbu
arxiv.org/abs/2507.06990

@arXiv_qbioQM_bot@mastoxiv.page
2025-06-10 18:20:40

This arxiv.org/abs/2406.14572 has been replaced.
initial toot: mastoxiv.page/@arXiv_qbi…

@frankel@mastodon.top
2025-05-20 08:11:06

Deep Dive into #uv #Dockerfiles by #Astral: Image Size, Performance & Best Practices

@khalidabuhakmeh@mastodon.social
2025-06-04 12:17:59

If you’re interested in the best current practices for securing #SPA apps, then you should tune into our livestream today. Applies to #react #angular

@matthiasott@mastodon.social
2025-06-23 11:30:35

TFW you build a site with @… and web platform standards (== semantic HTML, modern CSS, a little bit of JavaScript, and a dash of ARIA) and you look at Lighthouse for the first time …
Looks like industry best practices actually work. (Sorry for using my platform to ruin anyone’s day. 🥰) 🍋

A screenshot of Lighthouse showing scores of 97 for Performance, 99 for Accessibility, 100 for Best Practices and 100 for SEO
@sperbsen@discuss.systems
2025-07-03 13:18:31

Dredging up recollections of my experience as R6RS editor for my PLSS talk tomorrow.
2025.ecoop.org/details/plss-20

@frankel@mastodon.top
2025-05-22 16:15:07

Don't Unwrap Options: There Are Better Ways #Rust
corrode.dev/blog/rust-option-h

@mgorny@social.treehouse.systems
2025-06-29 16:44:37

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.

@arXiv_csCR_bot@mastoxiv.page
2025-06-04 07:22:00

Docker under Siege: Securing Containers in the Modern Era
Gogulakrishnan Thiyagarajan, Prabhudarshi Nayak
arxiv.org/abs/2506.02043

@publicvoit@graz.social
2025-06-21 10:15:19

The Protesters' Guide to #Smartphone #Security

@michabbb@social.vivaldi.net
2025-05-29 19:32:54

#7 🔍 Run regular security audits using #Larastan, #PHPStan and security checkers

@arXiv_csCL_bot@mastoxiv.page
2025-06-03 08:20:56

RewardBench 2: Advancing Reward Model Evaluation
Saumya Malik, Valentina Pyatkin, Sander Land, Jacob Morrison, Noah A. Smith, Hannaneh Hajishirzi, Nathan Lambert
arxiv.org/abs/2506.01937

@kurtsh@mastodon.social
2025-06-14 15:00:55

How to secure your phone before joining a protest
✅ The Protesters' Guide to Smartphone Security
privacyguides.org/articles/202

@berlinbuzzwords@floss.social
2025-06-16 10:19:05

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:

Mices at TUECHTIG
@arXiv_astrophGA_bot@mastoxiv.page
2025-06-30 09:53:40

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
arxiv.org/abs/2506.22381

@arXiv_csCR_bot@mastoxiv.page
2025-07-01 10:59:03

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
arxiv.org/abs/2506.23814

@frankel@mastodon.top
2025-06-22 08:15:07

CI/CD #Pipeline #Architecture: Complete Guide to Building Robust CI and CD Pipelines

@berlinbuzzwords@floss.social
2025-05-15 11:00:10

Join Kevin Liang at this year's Berlin Buzzwords, where he will discuss how Apache Solr/Lucene builds dense vector indexes and talk 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.
Learn more:

Session title: Performance Tuning Apache Solr for Dense Vectors
Kevin Liang
Join us from June 15-17 in Berlin or participate online / berlinbuzzwords.de