Hacker News: TheFirstNubian

New comment by TheFirstNubian in "Who owns the code Claude Code wrote?"

TheFirstNubian — Tue, 28 Apr 2026 13:04:28 +0000

The elephant in the room, of course, is what constitutes “meaningful human authorship.” However, I cannot shake off the feeling that all user interactions with these AI models are being logged. Perhaps this may turn out to be the bigger concern in a potential legal battle than code authorship.

New comment by TheFirstNubian in "Microsoft and OpenAI end their exclusive and revenue-sharing deal"

TheFirstNubian — Mon, 27 Apr 2026 21:19:57 +0000

That seems to be the general direction, at least from my daily dose of cope on X (Twitter). Regardless, conscious design will never go out of style.

New comment by TheFirstNubian in "Microsoft and OpenAI end their exclusive and revenue-sharing deal"

TheFirstNubian — Mon, 27 Apr 2026 21:03:35 +0000

Lol! Wrong choice of word, maybe. I meant to say that we don’t seem to be putting much thought into how we’re outsourcing thinking to the LLMs.

New comment by TheFirstNubian in "Ask HN: Why is Rust still hard to use as a scripting language?"

TheFirstNubian — Mon, 27 Apr 2026 21:00:25 +0000

I’ve used Rust daily for the last 6 years; from writing compilers and WASM runtimes to writing smart contracts and SDKs… and the experience has been nothing short of amazing.

I’m not sure what you mean by a “casual setup,” but I find Cargo to be very easy to use. Granted, compilation can be pretty slow, but it’s a small price to pay for the runtime performance.

If by “faster feedback” you mean something that looks and feels like Python’s REPL, then I think you’re missing the point here. Rust is a compiled language.

New comment by TheFirstNubian in "Microsoft and OpenAI end their exclusive and revenue-sharing deal"

TheFirstNubian — Mon, 27 Apr 2026 20:38:06 +0000

I’m a little conflicted on this, as I see a slippery slope here. LLMs in their current state (e.g., Opus-4.7) are really good in planning and one-shot codegen, which I believe is their primary use case. So they do provide enough leverage in that regard.

With this new workflow, however, we should, uncompromisingly, steer the entire code review process. The danger here, the “slippery slope,” is that we’re constantly craving for more intelligent models so we can somehow outsource the review to them as well. We may be subconsciously engineering ourselves into obsolescence.