As I said, how I do this is to bring in the code for my hobby projects.
> The artist's history of work itself is how they get more work; the programmer's isn't.
It's just a recommended strategy, not a requirement. In general, it's a great idea to identify a customer's pain points and reduce them. When you're looking for a job, the companies you're talking to are the customers. The easier you make things for the interviewer, the more you can reduce their pain points, the better your chances for the position.
The person you replied to is annoyed they have to do that when it seems like others don't. They think they shouldn't have to and it isn't fair they do. Explaining how to do it fundamentally does not address their point.
If you're trying to explain how they can do it with the least amount of extra work, to minimize the impact of the extra expectation, please consider that not everyone has hobby projects. Even fewer people's hobby projects are presentable, and even fewer still can trust the other person not to draw some wild conclusion based on anything that might be in there.
I think everyone is clear on how the situation works, but not everyone is happy with it working that way.
> The artist's history of work itself is how they get more work; the programmer's isn't.
It's just a recommended strategy, not a requirement. In general, it's a great idea to identify a customer's pain points and reduce them. When you're looking for a job, the companies you're talking to are the customers. The easier you make things for the interviewer, the more you can reduce their pain points, the better your chances for the position.