Korean developers have a word for a certain kind of work: sapjil (삽질), which literally means “shoveling.” It’s slang for hard, grinding effort that may lead nowhere, close to what English speakers call spinning your wheels, but it also carries the sense of digging into something. When you actually look, they’re working hard at something, so why call it “shoveling”? My feeling is that developers in general have a strong self-deprecating tendency. I suspect it comes from a sense of responsibility for the product they shipped. When a feature breaks, it’s easy to think that it’s ultimately my fault for writing the code that broke.

Before a developer actually builds something, they need sufficient knowledge and supporting evidence. And even during the actual development period, additional research (learning) may be needed because of problems and exceptions the developer didn’t know about beforehand. Developers usually describe this period as “shoveling.”

Since the term “shoveling” is used as an idiom for “doing useless work,” it has a strongly negative image. Depending on the manager, this period gets treated as worthless time, and the longer the shoveling goes on, the more it gets judged as a lack of ability as a developer.

In fact, as described above, “shoveling” is learning and research. And the knowledge accumulated during that period becomes a valuable asset of the company. Just as you quickly forget what you studied if you don’t write it down, the knowledge gained during the “shoveling period” becomes really worthless time if it isn’t recorded.

If a manager really cares about the product and the business, they should turn the developer’s shoveling into a company asset before it turns into really useless time. Build a culture where shoveling is not a bad thing, record the research results with various tools, organize them so they can be found easily and not forgotten, and leave references in various places. If there is no such culture, in an atmosphere where “shoveling” is worthless time, developers will hide that time, and the research results will vanish forever.

If that feels difficult, let’s try a proven framework. Scrum and XP have a term called a “spike.” A spike is work that doesn’t add value to the product itself but avoids risk or finds a better approach. By adopting a framework like this, the period called shoveling can be turned into time that is respected, and through a proper process, the research results can be made known to everyone.

A lot of effort is needed to keep “shoveling” from becoming really meaningless time. If you want to change a culture that belittles developers’ shoveling, I suggest starting by using a different term, like “research” or “spike,” instead of “shoveling.”