Marcus Aurelius ran the Roman Empire from 161 to 180 AD — roughly nineteen years — and somehow found time to write one of the most enduring books on Stoic philosophy while doing it. He also fought the Marcomannic Wars on the northern frontier, survived a co-emperor who’d siphoned off half his authority, dealt with the Antonine Plague that killed five million people, and trained seriously in philosophy every single day regardless. When historians ask how he managed all of it, the answer is strange for a man with that much power: he was one of the most aggressive refusers in antiquity. He turned down invitations emperors were supposed to accept. He ended meetings before they concluded. He delegated, without apology, everything that wasn’t irreplaceable. His journals — Meditations, written for no audience but himself — return again and again to one obsessive question: is this worth my time?
Not because he was lazy. Because he understood something most men never grasp, even now: time doesn’t renew and attention isn’t elastic. Every hour spent on something mediocre is an hour permanently subtracted from something excellent. And the discipline that kept his hours pointed at excellent things wasn’t willpower in the generic sense. It was a trained, systematic refusal to let the unimportant in.
Two thousand years later, in a different empire entirely, a man named Cal Newport sat in his office at Georgetown and started tracking where his colleagues’ time actually went. The data was embarrassing. Highly educated professionals at a research university were spending, on average, more than sixty percent of their working hours in meetings, email, and administrative churn that produced nothing they’d be proud of in five years. The people who published, who built reputations, who created lasting work — they’d found ways to protect the hours that mattered. Everyone else was busy. Constantly, exhaustingly, impressively busy. And had almost nothing to show for it. Newport called the distinction deep work versus shallow work, and the separator between the two groups was simple: one had learned to say no, and one hadn’t.
This is about the discipline of saying no — the Priority Gate System — and why it might be the single most important skill going unbuilt. The neuroscience of why the brain fights this, the research on what the refusal gap costs across a career, the specific method for building the reflex, and the three failure modes that destroy men who understand the concept perfectly and still can’t live it. Calendar full, life hollow. Keep reading. That’s the exact symptom being treated here.
The Neuroscience of Why Saying No Feels Like a Threat
In 1966, psychologist Julian Rotter published his foundational paper on locus of control in Psychological Monographs. Decades of follow-up research held the core finding steady: people with an internal locus of control — those who believe their choices shape their outcomes — consistently outperform people with an external locus on every metric studied: income, career advancement, relationship stability, physical health, speed of recovery after setbacks. The internal-locus crowd is also, unsurprisingly, much better at saying no. They’ve internalized that their choices belong to them, which means every yes is a deliberate allocation and every no is a deliberate protection.
But building that internal orientation runs straight into a deeply wired social threat response. Naomi Eisenberger at the University of California, Los Angeles, ran a series of fMRI studies published in Science in 2003 showing social rejection activating the same neural circuitry as physical pain — specifically the dorsal anterior cingulate cortex and the anterior insula, the regions processing the distress component of pain. The brain doesn’t cleanly separate “they rejected my friendship” from “this is physically hurting me.” Both register as threat. Both trigger the same cascade: amygdala fires, cortisol releases, the body braces for defensive action.
Which is why saying no produces a physical sensation of dread wildly disproportionate to the actual stakes. Decline a meeting invitation and the stomach tightens. Tell a colleague the project can’t be taken on and the conversation gets rehearsed six times beforehand. Say no to the mother-in-law about Thanksgiving plans and the heart rate climbs. The primitive brain is screaming expulsion from the group, and the rational brain — which knows perfectly well that declining a calendar invite won’t get anyone expelled from anything — has to fight that signal just to hold the position.
Roy Baumeister at Florida State University added another layer with his ego depletion research, published in the Journal of Personality and Social Psychology in 1998. Self-regulation — the mental act of choosing the strategically correct response over the emotionally automatic one — draws from a finite cognitive resource that depletes through use. Every override of an impulse, every held boundary, every resisted default yes draws down the account. By late afternoon, after dozens of micro-decisions requiring some degree of self-control, capacity for strategic refusal is measurably lower than it was at 8 AM. Which is exactly why the meetings that produce bad commitments always happen at 4 PM, and why the impulse yes is hardest to stop right before dinner, when the willpower tank is running on fumes.
Martin Seligman at the University of Pennsylvania showed what happens once the threat response dominates long enough: learned helplessness. His 1967 experiments exposed dogs to inescapable electric shocks; placed later in environments where escape was trivially easy, those same dogs didn’t try. They’d encoded, at a pre-verbal level, that effort doesn’t change outcomes, and carried that encoding into every new situation. Humans build the same pattern in environments where boundaries get systematically violated — volatile households, coercive workplaces, relationships where no is not accepted. The result isn’t weakness. It’s adaptation. The brain stopped attempting what never worked. The cost is that it stops attempting in new environments where it would absolutely work.
Baumeister’s colleague Kathleen Vohs extended the depletion research to show that decision fatigue — cognitive exhaustion from making too many choices — degrades the quality of every decision after it. A 2011 study in the Proceedings of the National Academy of Sciences analyzed 1,112 parole hearings in Israeli courts and found judges granting parole about 65% of the time at the start of the day and right after breaks, and less than 20% immediately before a break. Same judges. Same case types. The only variable was when in the day the hearing landed. Decision fatigue pushed judges toward the conservative default — deny parole — because it took less cognitive effort. For a man trying to say no to low-priority requests, this means the battle is hardest exactly when it most needs to be easy: late in the day, when the requests are piling up and the tank is empty.
The practical implication is structural, not motivational. Nobody wills their way through an architectural problem. “Just be tougher” doesn’t work when the amygdala is screaming threat and the prefrontal cortex is running on empty. The fix is system-level: front-load the hard nos to the morning, make the default response to late-day requests a delay rather than a yes, and build decision rules that convert as many refusal decisions as possible from active choices into automatic outcomes. The Priority Gate System below does exactly that.
One more finding worth sitting with: Teresa Amabile at Harvard Business School tracked the daily work lives of 238 professionals over multiple years, published in Harvard Business Review in 2011. The single strongest predictor of creative output and subjective wellbeing at work, she found, was what she called “the progress principle” — the feeling of making meaningful progress on meaningful work. People spending their days in reactive mode — responding to others’ requests, attending meetings they didn’t initiate, handling other people’s emergencies — reported the lowest wellbeing and produced the least original work, even while objectively busy for more hours. The people protecting blocks of uninterrupted time for deep work, even small blocks, showed dramatically higher output quality and reported their days as meaningful. Saying no isn’t an act of selfishness. It’s the structural prerequisite for doing anything that matters.
The Priority Gate System: How to Build the Refusal Reflex
The problem with most “say no more” advice is that it’s motivational rather than mechanical. It tells you to decline more without handing you a system that makes declining automatic. The Priority Gate System converts refusal from a willpower exercise into a decision architecture. Here’s how it gets built.
-
Write your three non-negotiable outputs — not goals, outputs. Not “be healthy” but “four training sessions a week.” Not “grow the business” but “three hours of deep work on the core product every morning before 10 AM.” Not “be a present father” but “dinner with the family, no devices, five nights a week.” These are the gates. Every request that shows up gets measured against whether it threatens these outputs. If yes, the answer is no by default — no deliberation required. Most men skip this step and then wonder why the system doesn’t work. It doesn’t work because without gates, every decision is a fresh negotiation, and fresh negotiations are exhausting and lossy. The gates need to be defined before the request arrives, not while standing in front of the person asking.
-
Create a 24-hour buffer on all non-urgent requests. The yes-reflex fires fastest under social pressure — someone physically present, a voice on the phone, waiting for the answer. The single most effective structural intervention: stop answering most requests in the moment they arrive. “Let me check my schedule and get back to you.” “I need to look at what I’ve got on before committing to that.” That buys the time to run the request through the gates without the cortisol spike of live social performance. Whoever genuinely needs an answer urgently will say so. Everyone else waits twenty-four hours without incident, and there’s suddenly mental space to make a clean decision. Cal Newport calls this a “slow yes” protocol and reports that it cut his own yes rate on requests he’d later regret by over sixty percent. The discomfort of the pause lasts about three seconds. The benefit is enormous.
-
Run the three-gate check on every request. Gate One: does this serve one of the three defined outputs? No — stop here, the answer is no. Gate Two: would the best version of you, operating at full capacity and full alignment, say yes to this enthusiastically? If the honest answer is “kind of” or “I guess” or “it seems bad to say no” — that’s a no. The enthusiasm bar is real and it matters. Fill a life with lukewarm yeses and there’s no room left when a genuine yes shows up. Gate Three: would the person most respected — a mentor, an elder, the highest-functioning future self — call this a wise use of time? If the answer would be embarrassing to admit out loud, don’t say yes. Three gates. All three must pass. One failure and the answer is no.
-
Build a script library and practice it out loud. The moment the language of a no gets improvised under social pressure is the moment the people-pleasing reflex takes over and the apology train starts rolling toward yes. Practiced scripts eliminate the improvisation window. The five most useful: (1) “I appreciate you thinking of me — I’m fully committed right now and can’t take this on.” (2) “That’s not mine to own. You need [specific person].” (3) “I can look at this in [specific future month] — is that timeline workable?” (4) “If I take this, which of my current commitments should I drop? I want to be clear on the trade-off.” (5) “I’m going to pass. Thank you.” Not five interchangeable options — sequenced for context. Practice saying them without explanation, without excessive apology, without the trailing clause that invites negotiation. One sentence. End. Pushback gets the same sentence at the same volume. No second argument required. Hold the first one.
-
Do a weekly inventory of yes commitments. Every Sunday, list every active commitment on the calendar and task list. For each: starting fresh today, would this get a yes? If the honest answer is no — the energy’s changed, the context shifted, the project went sideways — that’s a dead commitment, and it needs cancelling or renegotiating. Most men carry ten to twenty dead commitments at any given time: the committee seat accepted six months ago that produces nothing, the client relationship running at a loss for two years, the friendship maintained out of guilt rather than genuine affinity. Dead commitments are the most expensive kind, because they don’t just consume future time — they create ongoing cognitive overhead, the low-grade mental hum of something owed that gets resented. Kill them directly rather than letting them decay.
-
Protect the highest-output hours with hard calendar blocking. Bill Gates’s “Think Weeks” are famous, but the underlying principle works in two-hour increments too: block time structurally inaccessible to other people’s requests. Not “I’ll try to keep this time free” — actually block it, mark it unavailable, treat it with the same non-negotiability as a flight or a surgery. Cal Newport’s research at Georgetown found knowledge workers protecting four uninterrupted hours a day for deep work producing roughly four times the meaningful output of those who didn’t, even when the latter group logged longer total hours. The math isn’t mysterious: an interrupted hour produces about fifteen minutes of actual cognitive output. An uninterrupted hour produces about fifty-five. The discipline of saying no to everything that could claim that blocked time is what makes the output difference. The blocks make the nos structural instead of volitional — not “I don’t want to” but “I’m not available, it’s in my calendar.”
One note on implementation: don’t try all six at once. Pick whichever addresses the biggest failure mode — probably the 24-hour buffer for a compulsive in-the-moment yes, probably the weekly inventory for someone drowning in dead commitments — and work that one for thirty days before adding the next. The system compounds. Each component makes the others easier. But the learning curve on all six simultaneously is steep enough that most people abandon it inside a week.
Steve Jobs Killed 70 Percent of Apple’s Products: A Case Study in Strategic Refusal
Jobs killed thirty of the forty-three. In the first year. He kept four: a desktop and a laptop, each in a consumer version and a professional version. A two-by-two grid anyone could explain in twenty seconds. The engineers who’d built the dead products were furious. Some left. Jobs was unmoved. He understood something the previous management never grasped: the products getting killed weren’t just bad products. They were the reason the good products weren’t great. Every engineer on the Newton was an engineer not working on whatever would become the iMac. Every meeting reviewing Pippin roadmaps was a meeting not spent making the core machine extraordinary. The subtraction was the strategy.
Between 1997 and 2011, Apple went from near-bankruptcy to the most valuable company in the world by market capitalization. iMac, iPod, iTunes, iPhone, iPad — an unbroken run of category-defining products, from a company that said no to almost everything else. Walter Isaacson, who spent years interviewing Jobs for his biography, asked him to name what he was most proud of at Apple. Not the iPhone. The things they didn’t build. The focus came from the nos, not the yeses.
Greg McKeown, who studied Jobs’s approach extensively while writing Essentialism, identified the core principle: “If you don’t prioritize your life, someone else will.” Every hour not deliberately allocated to actual priorities gets claimed by someone else’s priorities — not out of malice, just because unallocated resources get absorbed. Jobs didn’t protect Apple’s focus by working harder. He protected it by making “no” the default and building an organization where “yes” required extraordinary justification.
The individual application lands the same way. Time is the limited product line. Roughly 2,000 waking hours a year aren’t already committed to sleep, basic biological maintenance, and the irreducible demands of work and family. Those 2,000 hours are the inventory. Everything said yes to is a product being built. Forty-three mediocre things, or four excellent ones. The discipline of saying no is the mechanism for making that choice deliberately instead of by accident.
Warren Buffett has been direct about this math. His method, described by longtime business partner Charlie Munger, involves writing down the twenty-five most important things in professional and personal life — and then actively avoiding the bottom twenty. Not the worst five. The bottom twenty. The good-but-not-essential commitments are the most dangerous ones, because they feel reasonable, and they consume exactly as much time as the unreasonable ones while producing a fraction of the value. Buffett calls them “the seductive distractions” — not bad enough to obviously refuse, not good enough to justify the opportunity cost. His entire career has been a sustained refusal of seductive distractions.
The Three Ways Smart Men Wreck the Priority Gate System
Trap One: The “just this once” bypass. The Priority Gate System fails when applied to policies rather than individual cases. The gates don’t say “decline most requests that don’t serve my outputs.” They say “decline requests that don’t serve my outputs.” But the moment a specific request lands, the mind starts generating reasons this particular request is different. The specific colleague who’ll be hurt. The one-time opportunity. The special circumstance. The people-pleasing alarm fires and immediately starts building a case for why the rule doesn’t apply here. This isn’t a sign the request is actually special. It’s a sign the brain is sophisticated enough to construct exceptions on demand — which it will do for every single request, because every request is specific and therefore feels exceptional. The fix: treat “just this once” as a red flag, not a valid argument. “This one’s different” is almost always the people-pleasing reflex in disguise. Run the gates anyway. If the request doesn’t pass, that thought isn’t a fourth gate. It’s the noise the first three gates exist to filter.
Trap Two: The articulate yes-man. There’s a specific type of overcommitted man who’s read every book on focus and productivity, can explain the Eisenhower Matrix, the essentialism principle, deep work, the 80/20 rule, and the neuroscience of decision fatigue with real fluency — and said yes to three things he shouldn’t have before lunch today. Familiar territory for a lot of guys who’d never admit it. The reading feels like progress. The explaining feels like having your act together. Neither is related to the actual behavior. Understanding a concept and living it have about as much in common as owning a gym membership and being able to do a pull-up. The gap between them is where intellectual self-help addiction lives: always consuming frameworks, never building the refusal muscle, surrounded by ideas that get articulated fluently and never once applied under pressure. The only way out is one concrete no today, delivered to a real person in a real interaction. Not another article. Not another podcast. One actual no, today.
Trap Three: Selective application under low stakes. The Priority Gate System runs fine on the big requests — the board seat, the major project, the three-month commitment — while every small daily friction gets a free pass without ever hitting the gates. The impromptu meeting eating an hour. The “quick” review that takes forty minutes. The Slack message that derails an afternoon. The lunch invitation accepted before thinking because declining seemed rude. These never get the gates because they feel too small to bother with. But small requests are where the refusal reflex actually gets built. They’re the reps. Can’t hold the gates when someone asks for fifteen minutes? The gates won’t hold when someone asks for three months. The deliberate practice principle applies directly: skill develops through repetition on the target behavior, not through understanding the behavior. A man practicing small nos fifty times a day builds a fundamentally different refusal reflex than a man deliberating carefully on large nos twice a year. The small ones are the training. Don’t skip them.
There’s a diagnostic for all three traps, uncomfortable but useful: if the Priority Gate System can be explained clearly and availability still hasn’t changed, the system is decorative. A framework to be proud of that’s doing nothing. The only corrective is behavioral: track the yes-to-no ratio for one week without changing anything, then look at the pattern honestly. Most men discover they’re saying yes to around 80-90% of requests regardless of priority. That number is the starting line. Getting it to 50-60% for requests outside the gates is the first milestone. Below 30% is where the actual time freedom lives.
The Counterintuitive Truth: Saying No Makes You More Valuable to People Who Matter
Say yes to everything and two things happen to relationships at once. First, the quality of presence degrades. At dinner but mentally at the three things agreed to that shouldn’t have been. In the conversation but part of the bandwidth is on the project taken on out of guilt. The people who matter most get a fractured, depleted version — not because they’re loved less, but because attention is divided among too many obligations. Second, resentment accumulates. Yes gets said to things nobody wants to do, and then the person who asked gets quietly resented, even though the obligation was entirely self-created. That resentment leaks. People feel it even when they can’t name it. The relationship deteriorates not because a request got declined, but because it got accepted while being resented.
John Gottman’s research at the University of Washington found the ratio of positive to negative interactions needed for a stable relationship runs roughly 5:1. Resentful compliance doesn’t register as positive. It registers as negative, sometimes as strongly as open conflict, because the withdrawal and distraction it produces get felt by the other person as absence. A man who says yes but shows up hollow is, by Gottman’s metrics, worse for a relationship than a man who says no and shows up fully present the times he does appear.
The people who build the deepest professional reputations are also, consistently, the ones who say no most often. Paradoxical until the mechanism gets examined. Someone who says yes to everything is fungible — anyone can help with anything, which means nobody is specifically valued for a distinct capability. Someone who says yes selectively, who declines most requests and commits fully to the few they accept, becomes associated with excellence in those few domains. The yes carries weight precisely because it’s rare. The commitment is credible precisely because a willingness to decline has already been demonstrated. The most sought-after collaborators, advisors, and senior professionals in any field are almost universally people who are difficult to get. Not difficult in a hostile way — difficult in the sense of clear standards for engagement, standards that are known and respected.
Connects directly to working the problem over narrating the problem: a man who says no to the unimportant has actual capacity left for the important, which means the engagement produces results instead of good intentions and apologetic half-measures. A relationship that survives a no and deepens through a subsequent wholehearted yes is stronger than one sustained by a thousand guilty yeses delivered at diminished capacity. Most people, once the trade is clear, would prefer the former. The discipline of saying no is, underneath everything, a form of respect — for the self, for the people receiving the yeses, and for the work that actually matters.
How the Priority Gate System Connects to the Broader Discipline Stack
The Priority Gate System sits at the base of almost every other discipline tool. Internal locus of control is what makes the gates feel legitimate in the first place — belief that choices actually shape a life, and are therefore worth protecting. Without that belief, building gates feels presumptuous. With it, building gates feels like basic maintenance. The locus of control work and the Priority Gate System reinforce each other in a direct loop.
Deliberate practice — the mechanism behind all real skill development — requires exactly the kind of uninterrupted focused time that saying no is designed to protect. Deliberate practice doesn’t happen in fifteen-minute windows between meetings. The research on expert performance, from Anders Ericsson’s work forward, consistently shows the accumulation of focused hours as the primary predictor of skill development. The Priority Gate System is what creates those focused hours. Without it, deliberate practice stays theoretically understood and practically unavailable.
The excellence over perfectionism framework connects directly to the “hell yes or no” gate. Perfectionism tends to accumulate commitments — the feeling that everything could be done better, that one more can be handled, that declining is a form of failure. Excellence, properly understood, requires ruthless selectivity. Nobody is excellent at forty-three things. Maybe four. The Priority Gate System is the mechanism for getting from forty-three to four.
For a structured container to build the refusal reflex over time, the chronic stress elimination framework addresses the downstream effects of chronic overcommitment directly, and the four-step unbreakable process gives the broader resilience architecture the Priority Gate System slots into. The discipline of saying no is not a standalone skill. It’s the mechanism that makes everything else possible — the space where actual building happens.
What People Ask About Discipline Saying Busy About the Discipline of Saying No
What is the Priority Gate System and how does it differ from just “setting boundaries”? The Priority Gate System is a three-gate decision architecture applied to every incoming request before responding. Gate one: does this serve one of the three defined non-negotiable outputs? Gate two: would this get an enthusiastic yes, not just a tolerable one? Gate three: would the most respected mentor consider this a wise use of time? All three must pass for the answer to be yes. This differs from “boundaries” framing in that it’s mechanical rather than emotional — not defending against requests, but routing them through a filter that makes most decisions automatic rather than deliberated. Julian Rotter’s locus of control research and Teresa Amabile’s progress principle research both support the underlying pattern: people making deliberate allocation decisions, rather than reactive ones, produce more meaningful work and report higher wellbeing.
How do you say no to your boss without damaging your career? Don’t say no to the boss directly — redirect to a prioritization conversation. When a new request lands: “I want to deliver this well. Here’s what I’m currently committed to — which of these should I deprioritize to make room?” This does three things: demonstrates willingness, surfaces a capacity constraint the boss may not have known about, and makes the trade-off explicit. Most managers will make a sensible prioritization call once they understand there’s a real constraint. The ones who don’t — who just add the work to an already-overflowing pile — are managing badly, and the worst outcome of that conversation is now visible and named. Baumeister’s ego depletion research confirms that high performers who protect their cognitive capacity deliver disproportionately better results than those who don’t. Making this case clearly to a boss is resource management, not insubordination.
Why do I feel guilty after saying no even when I know I made the right call? Because guilt and correctness run on different circuits. The guilt reflex comes from the social threat response described in Eisenberger’s 2003 fMRI research — the brain registered a potential threat to belonging and fired the associated discomfort. The correctness assessment comes from the prefrontal cortex evaluating the decision against actual priorities. Both can be simultaneously true: the right call was made AND the primitive brain is treating it as a threat. The discipline is feeling the discomfort without acting on it. It fades, reliably, within hours. Every time it’s tolerated without reversing the decision, the reflex weakens slightly. Sixty to ninety days of consistent exposure produces a measurable reduction in the intensity of the guilt response — which is why Phillippa Lally’s habit formation research, averaging 66 days for automation, maps directly onto this practice.
What’s the actual cost of chronic overcommitment — is it really that significant? Amabile’s progress principle research found reactive, overcommitted professionals working significantly more hours than focused professionals while producing substantially less meaningful output. The mechanism is attention fragmentation: each context switch costs roughly twenty minutes of recovery time before full cognitive engagement resumes (Gloria Mark, University of California, Irvine, 2005). Someone interrupted or task-switching four times in an afternoon loses over an hour of effective work time from fragmentation alone, before even accounting for the reduced quality of output produced while cognitively depleted. Over a career, the compounding effect is enormous: decades of fragmented work produce a fraction of the meaningful output that decades of protected focus would generate, even at lower total hours.
How do you handle someone who keeps pushing back after you’ve said no? Broken record technique: repeat the same sentence at the same tone, no new arguments, no new explanations. “I’m not able to commit to that” — once. Pushback: “I’m not able to commit to that” — again, same sentence, same delivery. The impulse when pushed is to add more justification, which is a mistake — more justification supplies more material for negotiation and signals that reconsideration is still on the table. One clear sentence, held calmly, ends most pushback within two to three repetitions. Beyond that, the dynamic has stopped being about the specific request. It’s a test of whether pressure can force a reversal. The correct response is to hold the sentence and, if necessary, end the conversation. A relationship that can’t survive a politely held no was never a healthy one.
How long does it take to build the Priority Gate reflex so it feels automatic? Phillippa Lally’s 2009 research at University College London found new automatic behaviors taking an average of 66 days to form, with a range of 18 to 254 days depending on complexity. The Priority Gate System is moderately complex — six components, multiple application contexts — so expect full automation to run 90 to 120 days of consistent practice. Most people notice the first significant shift around week three, when the impulsive yes starts getting caught before it leaves the mouth rather than recognized only after the fact. The early-stage metric worth tracking isn’t the quality of individual decisions but the pause rate: is there a pause before responding, or is the answer still happening in the moment? The pause is the mechanism. Once the pause is reliable, the gates do the rest.
Isn’t ruthlessly saying no just selfishness dressed up as productivity philosophy? The distinction is between the resource being protected and who benefits from the protection. Selfishness protects resources for personal consumption at others’ expense. Strategic refusal protects cognitive resources for high-quality outputs that serve both the individual and others more effectively. A surgeon declining social commitments the night before an operation isn’t being selfish — the cognitive state being protected is what the patient on the table needs. A father declining a committee seat that would consume his evenings isn’t being selfish — he’s protecting the presence his children need. Amabile’s research supports the pattern directly: people who protect deep work time produce more meaningful contributions to their organizations and relationships than those who don’t. The net effect on others is positive, not extractive. The people most likely to call this selfishness are usually the ones who’ve been benefiting from an inability to say no — which is information about their interests, not a critique of anyone’s values.
Related: Stoicism vs. Christianity: Discipline in Two Traditions
References