Remote

Nat Pryce

@natpryce@mastodon.social

mastodon 4.8.0-nightly.2026-10-06

Co-author of Java to Kotlin: a Refactoring Guidebook, and Growing Object-Oriented Software Guided by Tests

0 Followers

0 Following

9 Posts

Joined August 13, 2018

Nat Pryce @natpryce@mastodon.social

· 2mo ago

Companies are scraping GitHub to train LLMs. I hope they filter out my repositories of deliberately bad code for refactoring tutorials.

Nat Pryce @natpryce@mastodon.social

· 6mo ago

Coding agents are going to give us lots of data about the correctness of Bram’s Law: “The easier a piece of software is to write, the worse it is implemented in practice.”

Now lots more software is much easier to write.

Nat Pryce @natpryce@mastodon.social

· 10mo ago

Replying to

@emilybache@sw-development-is.social Have you seen this paper? https://arxiv.org/abs/2509.26204 It reports on analysis of human written tests and compares them to the properties of automatically generated tests.

arXiv.org

Hamster: A Large-Scale Study and Characterization of Developer-Written Tests

Automated test generation (ATG), which aims to reduce the cost of manual test suite development, has been investigated for decades and has produced countless techniques based on a variety of approaches: symbolic analysis, search-based, random and adaptive-random, learning-based, and, most recently, large-language-model-based approaches. However, despite this large body of research, there is still a gap in our understanding of the characteristics of developer-written tests and, consequently, our

Nat Pryce @natpryce@mastodon.social

· 4mo ago

Kotlin coroutines do not compose, and as a result type-checked programs can fail at runtime. Local lifetime checking can solve this, and will remove the need for marking functions with the “suspend” modifier, meaning no “coloured functions” problem in a future version of Kotlin! #KotlinConf

mastodon.social

Mastodon

Nat Pryce @natpryce@mastodon.social

· 4mo ago

Inspired by announcements in the #KotlinConf keynote, I rebuilt all Fork Handles modules with unused result value checking enabled, annotated the few methods that needed it with IgnorableReturnValue, and published as version 2.25.6.0. If you use Fork Handles, you can turn on unused result checking in your build.