# Just Make It Nice The Junk Drawer · JUNK_134 · 2026-08-18 On the Moment the Instructions Run Out --- When I was twelve, there was a local Italian restaurant owned by a family from my church. It was the kind of place that belonged to the neighborhood before anybody thought to call that a brand strategy. Kids could bus tables, carry things, clean things, and occasionally get pulled into whatever needed doing because it was the 1980s and apparently twelve was considered a perfectly reasonable age to be introduced to commercial kitchen logistics. One night the kitchen was short-staffed, and the family grandmother put me to work making dishes. She was the quintessential little old Italian woman who had probably assembled more trays of food than I had completed homework assignments. The first thing in front of me was lasagna. I knew what lasagna was, obviously, but knowing what something is and knowing how to build one for actual paying customers are two different levels of responsibility. So I asked her what to do, expecting quantities, sequence, layer count, an approved sauce-to-cheese ratio, maybe a small diagram indicating where the ricotta was expected to report for duty. She looked at me and gave me one of the most durable sets of instructions I have ever received: “Just make it nice.” At that precise moment, this was not the procedural documentation I had been hoping for. She had apparently reviewed the situation and decided I possessed enough basic intelligence to construct the lasagna both horizontally and vertically. The sentence has followed me ever since because it sounds almost useless until the moment you understand what it is actually asking. She was not telling me that there were no rules. Lasagna still has structural expectations. Sauce matters, multiple cheeses matters, and pasta should be involved somewhere. There are limits beyond which you are no longer making lasagna and are instead conducting an unauthorized casserole experiment. What she was telling me was that the rules could only carry me so far, and eventually I had to look at the thing in front of me. Was the layer too dry? Did it need more sauce? Was the cheese distributed well enough that somebody was not going to receive a depressing corner consisting mostly of noodle and regret? Did the tray look like something we would be comfortable putting in front of another person and calling dinner? The final instruction was not another measurement. It was attention. That is what I hear now when I tell myself to just make it nice. It is not permission to wing everything. It is permission to stop waiting for the universe to produce one more page of instructions after I already understand enough to proceed. There is a point where asking for more procedure is not preparation anymore; it is avoidance wearing sensible shoes. We like instructions because instructions distribute responsibility. If the recipe says three cups and I use three cups, then whatever happens next has at least one documented witness. Processes are comforting for the same reason. Checklists, templates, examples, standards, best practices, and step-by-step guides can prevent enormous amounts of unnecessary failure. I am strongly in favor of people reading the instructions before deciding they have transcended them. But every worthwhile activity eventually reaches the edge of the instructions. The recipe cannot see the pan in front of you. The template cannot know exactly what this sentence needs. The process cannot account for every room, every person, every constraint, every odd little variation in the ingredients, or the fact that somebody bought the wrong cheese and dinner is still expected at six. That edge is where judgment begins, and judgment is uncomfortable because it removes the ability to point at the page. You have to decide whether the thing is ready. You have to know when something needs another pass and when another pass will only make it worse. You have to choose between two acceptable options without receiving confirmation from a higher authority. Sometimes you have to make the call before you feel fully qualified to make it, which is one reason people can keep asking for instructions long after the instructions have stopped being the missing piece. “Just make it nice” is a surprisingly humane instruction for that moment because it does not demand brilliance. It does not say make it perfect, innovative, impressive, award-winning, optimized, or unlike any lasagna Central Jersey has previously encountered. Nice is a modest standard with serious implications. It means take care with it, make it coherent, think about the person who will receive it, and do not hand over something you know could have been better simply because nobody gave you an explicit rule requiring the improvement. Nice also leaves room for reality. A kitchen that is short-staffed does not need a culinary thesis. It needs dinner. There is a practical generosity in knowing the difference between care and perfectionism, because perfectionism can keep working long after the work has stopped getting better. Care wants the thing to be good enough that it respects its purpose and the person on the other side. That distinction has become more useful to me with age. A lot of adult life takes place in situations where the instructions are technically available but emotionally inadequate. There are books about marriage, parenting, leadership, grief, writing, friendship, cooking, money, creativity, and almost every other recurring human problem. Some of them are excellent. None of them can stand in the exact room with you and tell you what this particular moment requires. Eventually you have to know enough about the principles to make a local decision. That may be what expertise looks like more often than we admit. Beginners need rules because rules make invisible structure visible. More experienced people still use rules, but they begin to understand why the rules exist, which means they can recognize the moment when strict compliance would produce a worse result than thoughtful adjustment. The goal was never to memorize the recipe forever. The goal was to become the person who can look at the tray and know what it needs. This is also why taste matters, and I do not mean taste in the fancy sense where somebody explains that your kitchen backsplash is morally incorrect. Taste is the ability to recognize when the pieces belong together. It is developed through repetition, mistakes, observation, comparison, and the slow accumulation of examples. Nobody can transfer taste by handing you a laminated card. They can teach principles, but judgment only becomes useful when you practice using them. There is risk in that, of course. “Use your judgment” can become an excuse for carelessness when the person has neither knowledge nor interest in developing any. Some rules exist because generations of people already discovered what happens when everybody decides to freestyle the electrical code. The point is not that expertise makes structure unnecessary. The point is that structure and judgment are partners. A good framework gets you close enough to see the remaining problem clearly, and then the final few percent often requires a human being to notice what does not fit. That is where “just make it nice” has become one of my favorite answers to uncertainty. When I do not know exactly how to finish something, I am often not actually missing information. I am hesitating at the handoff between procedure and judgment. I know the purpose, I understand the material, and I can see what is in front of me. What remains is the uncomfortable little act of deciding what good looks like here. The phrase helps because it collapses the drama. I do not need to solve the universal theory of the thing; I need to make this version nice. That might mean removing something instead of adding more, fixing the crooked part nobody else would complain about but I would know was there, stopping before a simple thing becomes overworked, choosing the warmer sentence, the clearer layout, the extra spoonful of sauce, or the version that makes another person’s experience slightly easier. The word nice has been badly underestimated because we often use it to mean bland, harmless, or merely pleasant. In this instruction, nice means cared for. It means somebody was present during the making. The thing was not simply completed; it was considered, which is a higher standard than it sounds. There are plenty of technically finished things in the world that nobody bothered to make nice. Forms that work but punish the person filling them out. Rooms that contain every required object but feel hostile. Writing that is grammatically correct and completely dead. Food assembled exactly according to procedure with no attention paid to whether anyone would want to eat it. Completion is easy to measure, which is why systems love it. Niceness is harder because it asks whether the result actually feels finished from the receiving side. A twelve-year-old in a restaurant kitchen could not have articulated any of this. I mostly wanted to avoid ruining somebody’s dinner. But that may be why the lesson landed so cleanly. There was no lecture, no philosophy, and no framework diagram with arrows pointing toward Discernment. There was a tray, a job that needed doing, and a woman who had done the work long enough to know that she could explain every layer or teach me something better. She trusted me to look and to care. I still hear the instruction whenever the next step is not completely obvious. I can gather more information if I truly need it. I can find the recipe, read the documentation, study the examples, and ask better questions. But eventually all of that has to become a decision made by the person standing in front of the thing. When the instructions have done everything they can do, there is still one job left. Just make it nice. --- ProbleMattic is written and maintained by Matthew Kulcsar, a software engineer, project manager, technologist, platform builder, emergency-services-trained helper, grandfather, and lifelong collector of broken systems, odd behaviors, and useful nonsense.