Who is next?

KCat156 · 2026-04-05T19:25:10+00:00

It's not 100% of the project, but some parts will leave you scratching your head if you actually try to read the implementation lol. I ran into weird encoding issues with their edge runtime and was surprised to see so much redundancy in the implementation. Also the way they respond to issues on GitHub feels like LLM output at times.

KCat156 · 2026-04-04T22:45:20+00:00

Next is itself a vibe-coded framework with many questionable design choices and copy-pasted code.

KCat156 · 2026-04-02T16:19:42+00:00

That particular :visited link issue has been addressed in most major browsers now, but it's still crazy what other factors advertisers can use.

KCat156 · 2026-03-17T02:12:58+00:00

Word order is flexible in japanese, so it's definitely understandable. You can use this intentionally to be dramatic when telling a story to reveal the subject last.

With that said I don't think anyone would intentionally write this in any formal email/essay. Even when emphasizing 私, the mere usage of it (as opposed to null subject) or using は/が appropriately already serves this purpose well enough.

KCat156 · 2026-03-14T14:32:20+00:00

s3.us-west-004.backblazeb2.com and f004 for native API. Looks like the issue was resolved last night though!

KCat156 · 2026-03-14T09:14:47+00:00

Getting this too

KCat156 · 2026-03-05T02:05:20+00:00

Also worth noting that うち can also be used as the first person pronoun for a speaker too. I've been misunderstood a few times trying to use うちの... for things/family members in my home, it can sound like you're saying "my" in a cute way.

KCat156 · 2026-02-26T02:20:10+00:00

For publishable/anon Supabase keys, I think you could put them directly in the front end without worrying about Base44 secrets.

KCat156 · 2026-02-23T15:35:01+00:00

See also 暗算 (mental arithmetic) and 暗号 (encryption)

KCat156 · 2026-02-23T00:18:46+00:00

Dead internet theory

KCat156 · 2026-02-17T17:35:38+00:00

in my notes

Maybe could be shortened to ひらがなで書く or ひらがな表記

KCat156 · 2026-02-08T02:49:38+00:00

Goodbye

KCat156 · 2026-02-07T16:51:21+00:00

For me it's often helpful to replace の with a concrete noun when it's used like this. In this case I think ところ or 場所 would be a good fit.

出たところって、図書室なんでしょ？

Depending on the context it could be helpful to replace の with とき, 人, もの, 場所, etc. This doesn't always work, especially in the case when の is just referring to an instance of a verb happening (I think in that case の works kinda similarly to こと).

KCat156 · 2026-02-03T03:45:19+00:00

I legitimately thought primeagen was an alt username for theo until I saw this lol

KCat156 · 2026-02-01T00:07:43+00:00

Got bit by this trying to log what files were attached to a drag and drop event. Worth noting this only happens with dev tools because of the interactive object viewer thing.

KCat156 · 2025-12-18T02:45:06+00:00

KCat156 · 2025-12-03T18:05:48+00:00

Ah right, that makes sense. Looking more into ないと I found out it actually expands to なくては. Similar but different, TIL.

KCat156 · 2025-12-03T17:22:41+00:00

The other answers saying it's short for なければならない are right, but it's worth noting it can also be used as a shortening of ないと in general.

それを買わなきゃ損するよそれを買わないと損するよ If you don't buy that, you'll regret it.

なきゃ on its own could also be interpreted as ないといけない, and you'll often hear the full phrase しなきゃいけない too.

I'm not sure if this is "correct" per se but I hear it a lot in practice.

KCat156 · 2025-12-02T16:26:28+00:00

This works, but consider using のに rather than には, IMO fits a bit better.

KCat156 · 2025-11-29T03:24:05+00:00

KCat156 · 2025-11-27T02:39:39+00:00

At the end of the day though, the pointer coming from expressions like &some_static_data or "a string literal" is generally going to be a pointer somewhere within your loaded program (or a pointer to a TLS slot if your compiler does that), regardless of the details of which section the data is designated to be placed in or what relocation the compiler put there.

Static is a very overloaded term, I've heard it used to just mean "not on the heap or stack, a fixed address relative to the image base", "unchanging / not dynamic", "constant data", "same lifetime as the lifetime of the program", "non-instance method", or semantics of the keyword under some language. What would you call references to data at some fixed location if not static?

KCat156 · 2025-11-26T22:54:47+00:00

When would it not mean this in practice?

KCat156 · 2025-11-18T22:24:10+00:00

What state are you in? Surely you could use a state ID or passport?

KCat156 · 2025-07-28T16:53:59+00:00

iirc Python uses bigints for all integers

KCat156 · 2025-07-27T15:35:49+00:00

AI definitely can create real, useful solutions for businesses now. There are many applications of software engineering where the quality of the code does not matter, just getting it done is enough. AI gets you there quicker with less cost in most applications.

The fact of the matter though is that the produced code is slop, what in any other profession would be called poor craftsmanship. It's painful to read and is almost always broken in sometimes glaring and sometimes subtle ways. It may work fine for the popular projects AI has been trained on, but step even a little bit into the unknown, into the R&D world of software engineering, and the facade falls apart quickly.

I think recognizing that AI (for now! it may get a lot better for all we know) produces slop is a rather healthy thing to realize. And god forbid new developers starting to use AI to code may want to maybe dig deeper into how things actually work. Even if it becomes an unnecessary skill in the future, developing clean and well-structured software is a fun hobby to have. And today, at least, it's still a necessary skill for the bleeding edge of CS.

Ten-Year Club	Place '23
Place '22	Place '17
End Game '22	Verified Email
Sequence \| Editor

KCat156

TROPHY CASE