nyaomaru | Game Developer

Funny frontend engineer (React / Vue / TypeScript)
I made a tiny game about running away from work
👇Let's Play

[nyaomaru | Game Developer @nyaomaru_dev]

unknown type is unknown.

So, if you want to use correctly, you should do type narrowing.

Then, you can use is-kit.
https://t.co/ZbTYBhfeTT

[nyaomaru | Game Developer @nyaomaru_dev]

Published a new article! 😺

I wrote about why CHANGELOG.md still matters in the AI era, and how changelog-bot helps automate it.

It supports Git history, PRs, GitHub Release Notes, OpenAI, Anthropic, Gemini, and fallback generation without AI.

https://t.co/9qjl8ii7a2

[nyaomaru | Game Developer @nyaomaru_dev]

Contributors rarely forget to write code.

They often forget to explain what changed.

That's why CHANGELOGs drift over time.

[nyaomaru | Game Developer @nyaomaru_dev]

One thing I noticed:

AI is much better at understanding a project when a good CHANGELOG exists.

A release history is surprisingly valuable context.

[nyaomaru | Game Developer @nyaomaru_dev]

Published a new article! 😺

I wrote about why CHANGELOG.md still matters in the AI era, and how changelog-bot helps automate it.

It supports Git history, PRs, GitHub Release Notes, OpenAI, Anthropic, Gemini, and fallback generation without AI.

https://t.co/9qjl8ii7a2

[nyaomaru | Game Developer @nyaomaru_dev]

A stale CHANGELOG is almost worse than no CHANGELOG.

People assume it's accurate.

Then discover it stopped being maintained 6 months ago.

[nyaomaru | Game Developer @nyaomaru_dev]

I think most developers agree that CHANGELOG.md is important.

The problem is:

it's manual work.

And manual work tends to be skipped.

[nyaomaru | Game Developer @nyaomaru_dev]

CHANGELOG.md is boring.

But it's surprisingly important.

* users read it
* maintainers read it
* AI agents read it

When I'm triaging Dependabot updates with AI, I often feed CHANGELOG.md into the context.

The problem?

Most projects stop maintaining it.

[nyaomaru | Game Developer @nyaomaru_dev]

Recently, my brain has been exploding. 🤯

[nyaomaru | Game Developer @nyaomaru_dev]

I don’t think the real risk of AI in software is “humans vs AI.”

The real risk is humans using AI to avoid responsibility.

Avoiding design decisions.
Avoiding trade-off discussions.
Avoiding long-term thinking.

AI is powerful, but it amplifies our habits.

[nyaomaru | Game Developer @nyaomaru_dev]

ls
ls -al

[nyaomaru | Game Developer @nyaomaru_dev]

You can’t avoid technical debt.

But you can slow it down.

Start with one check today:

Does your "atoms" contain domain logic?

https://t.co/KF2aZkI5Kr

[nyaomaru | Game Developer @nyaomaru_dev]

Red flags:

- "Ver2" / "Copy" in filenames
- domain terms inside UI components
- hooks inside atoms

If you see one, debt already started.

[nyaomaru | Game Developer @nyaomaru_dev]

Better structure:

ui/ → reusable UI
features/ → domain-specific components

Separate them early.
Or pay later.

[nyaomaru | Game Developer @nyaomaru_dev]

@barkin_cat I think so too.

If AI costs increase over time, blindly relying on it may become harder.

So it’ll probably become even more important to have solid fundamentals and use AI intentionally.

In the end, I don’t think the basics ever disappear.

[nyaomaru | Game Developer @nyaomaru_dev]

I’m not against using AI for software development.

But I’m worried that AI can make old anti-patterns look new.

- Shipping fast without clear design.
- Accepting bugs as a cost of speed.
- Assuming future tools will clean up today’s mess.

We have seen this pattern before.

[Dor Moshe @DorMoshe]

📰👨‍💻 I just published #TypeScript Trends #271 https://t.co/8SR6LGHU6Z @nyaomaru_dev @thepracticaldev @ErikCH @leptronix @dormoshe #dormosheio #frontend #webdev

[nyaomaru | Game Developer @nyaomaru_dev]

The scary part of AI-generated code is not only that it can be wrong.

The scarier part is it look clean while hiding poor decisions.

Good names.
Nice comments.
Reasonable structure.
Maybe even types.

Broken code used to look broken.
Now it can look polished.

[nyaomaru | Game Developer @nyaomaru_dev]

AI is not magic.

If we skip design decisions and use AI only to move faster, we may just create technical debt at a much higher speed.

Before, it was:
“We’ll fix it later because deadlines are tight.”

Now, it is:
“We’ll fix it later because future models will be better.”

[nyaomaru | Game Developer @nyaomaru_dev]

Thanks for featuring my article! 😺

I compared openapi-typescript, hey-api, Orval, and Kubb from a frontend TypeScript perspective.

https://t.co/3MN2K0W45l

[Dor Moshe @DorMoshe]

📰👨‍💻 I just published #Angular #TypeScript Trends #420 https://t.co/gNLP7wEw8o @ahmershah29 @thepracticaldev @nyaomaru_dev @leptronix @dormoshe #dormosheio #javascript #frontend #webdev

[nyaomaru | Game Developer @nyaomaru_dev]

AI can speed up implementation.

But it does not automatically take responsibility for design, maintainability, or long-term thinking.

We should delegate tasks to AI, not design responsibility.