Is my code affected by slop? May. 18, 2026

To be or not to be, that is the question.

Intro

In these months, I’m finalizing my toy projects, after that I’m going to take a break from coding.

As I live in a environment that “AI tools” are inevitable, some of my projects contains AI generated code (a.k.a. “slop”).

Below is an analysis.

Those not affected by slop

Some of these can be found in the projects page.

I promise to don’t affect them with slop in the future. I may add a “human contributions only” note in them if I actively maintain them in the future.

Those affected by slop

fscrypt

fscrypt is a cryptography library, which should be taken special care to make.

Sadly, I’m not security expert. But I shouldn’t ship security holes to users.

In v0.2.1, I’ve used certain AI tools to detect and fix holes, it’s more robust, but now it contains slop.

I’m not actively using it, and maintainance is up to you. To de-slop it:

osudb

osudb is a toy project to read osu!lazer database. Also the server osudb-native.

The overall idea is human-made, but the code contains a handful of slop.

It has nothing to do with official osu!, which explicitly states human contributions only.

voicevox-cli-demo

voicevox-cli-demo is a command-line tts demo.

I’m very busy in real life and this is quick test for an idea. Most of it is vibe coded.

If the idea is interesting and you reject slop, feel free to re-develop “vfox.”

The only important human code for you to take away:

// Returns first path exists on disk, otherwise returns empty string.
template<typename T, typename... Args>
const std::string first_exists(const T& head, const Args&... tail) {
	if (std::filesystem::exists(head)) {
		return head;
	}
	if constexpr(sizeof...(tail) > 0) {
		return first_exists(tail...);
	} else {
		return "";
	}
}

Ending

I must have a life and AI tools are still inevitable. If you feel it unacceptable, just take away my idea, and throw away the slop.

See also: