I knew what dinner would be when my mom came home from the dakjip (닭집) with a chopped, bone-in chicken.

The butcher had already done the work, cleaving through bone and cutting the pieces smaller than they seemed they should be. Even the legs were split, as if left whole they would be too large. The cuts were rough, sometimes leaving small splinters of bone, but that was part of it. It meant the sauce could reach everything.

Spicy, garlicky, salty, a little sweet, something between a soup and a stew. The chicken would simmer with potatoes, carrots, and onions, the sauce thickening as it cooked. It was never meant to be eaten on its own. I would pull a piece into my bowl of rice, letting the red, oily broth soak in, the grains turning glossy as they absorbed it.

This way of cooking, bone-in chicken chopped through and simmered until the sauce thickens, is not unique to Korea. There is a reason for it. It simply tastes better. I’ve tried making it with boneless chicken, without skin or fat, thinking it would be healthier, but it never tastes quite right.

I’ve seen similar cuts in chicken curries across Asia. The pieces are handled in much the same way, bones left intact, skin left on, allowing the sauce to cling and deepen as it cooks.

It is different from what I often see in Western cooking, where chicken is more often left whole or neatly separated from the bone and skin. The cuts are cleaner, the portions more defined. What I grew up with felt less precise, but more integrated, the bone, the sauce, and the rice working together.

I don’t cook it that way anymore, partly because it is hard to find a butcher who will cut it like that. But I still remember the rhythm of it. So whenever I come across a version that looks familiar, I find myself curious, and quietly glad to recognize it in another place.

Although I was taken aback when I came across a recipe on The New York Times Cooking. It called the dish dakdoritang (닭도리탕). The surprise caught me off guard. Growing up, I had been taught not to use that word. Around the time I began to love the dish, I was told to call it something else: dak-bokkeum-tang (닭볶음탕).

Like most Koreans, I know the dish by both names. Still, I carried the sense that one of them was the right one. In 1992, the National Institute of Korean Language promoted a new name as a “pure Korean” alternative, and that framing shaped how my generation learned the word.

Dakdoritang was the name I learned first. But the “dori” became controversial, often believed to come from the Japanese tori (chicken). Given Korea’s colonization by Japan, even a hint of Japanese origin carries weight.

The newer name, dak-bokkeum-tang, was introduced as a replacement: dak (chicken), bokkeum (stir-fried), tang (stew). The shift reflects an effort to reclaim language through “pure” Korean terms.

Still, the situation is not so clear. Some linguists argue that “dori” may come from the Korean verb dorida (도리다, to cut), not Japanese. At the same time, the newer term combines two cooking methods and feels slightly forced. In that sense, the older name feels natural but remains questionable, while the newer one is official but not entirely intuitive. The correction never fully replaced the original.

In practice, the two names coexist. Official menus and media tend to use Dak-bokkeum-tang, and many people of my generation learned to follow that. But in everyday speech, Dakdoritang remains common. It appears in unexpected places, in international recipes, design templates, and casual conversation, suggesting that some words resist being fully rewritten.

I remember ordering French fries in the Netherlands. The server smiled and asked, “You mean patatje?” It was a small correction, almost casual, but I felt it. I had used a word that was perfectly understandable, yet not quite right for that place. The difference was subtle. “French fries” would not confuse anyone, but “patat” was what people actually said. The correction pointed to local habit, not correctness.

In Korea, the shift from an older name to a newer one for the same chicken dish feels different. It is not just about what people say, but what they are told they should say, and why. The difference is not linguistic. It is historical.

To this day, I catch myself saying odeng (오뎅) before correcting to eomuk (어묵), or udon (우동) instead of garak-guksu (가락국수). The older word comes first, almost automatically, and the correction follows. It is not that I do not know the standard term. It is that the other one is already there.

Some words have fully disappeared. The pickled yellow daikon that always accompanies jjajangmyeon (짜장면), dakkwang (다꽝), now feels distant, something from my grandparents’ generation. It has been replaced completely by danmuji (단무지).

Still, some words resist translation altogether. Seukkidasi (스끼다시), believed to come from the Japanese tsukidashi, refers not just to side dishes, but to a specific dining culture in hwetjib (횟집), where food arrives in a particular rhythm and abundance. Alternatives like what Koreans would call gyeotdeuri-chan or mitbanchan describe the function, but not the experience.

The same is true of places like dajjijip (다찌집), where the word captures a style of eating shaped by multiple influences. It is not simply a matter of translation. The concept itself does not fully exist in either language, which is why attempts to replace it never quite take hold.

And then there is chikin (치킨), the word Koreans use for fried chicken. No one questions it. We say it without hesitation, “치킨 먹자” or “치킨 시킬까?” — let’s get chicken, should we order some? There is a word for it, dak-twigim (닭튀김), literally “fried chicken,” but no one really calls it that. It comes from English, just as clearly as some of the words we were taught to avoid come from Japanese. But it was never corrected, never replaced with something more “pure.”

Depending on the word, the outcome is different. Some are replaced. Some coexist. Some persist unchanged. In some cases, both forms are accepted.

In North Korea, the approach goes further. Foreign-derived words are systematically replaced with native ones, sometimes to the point where they feel unfamiliar even to Korean speakers. I have come across terms like kkoburang-guksu (꼬부랑국수) for ramyeon (라면), descriptive and even charming, but distant from the words I know.

Just as table etiquette has changed, what was once considered impolite, like making noise while eating, is now embraced in forms like meokbang (먹방) and myeonchigi (면치기), the way we name and talk about food also evolves over time.

I still hesitate sometimes. Not because I don’t know the words, but because I know too many of them. Dakdoritang comes to mind, then dak-bokkeum-tang follows. Neither feels entirely wrong, but neither feels entirely settled.

The words I use are no longer just names. They carry traces of where they came from, who taught them to me, and what I was told to replace.