LWC). Instead of simply feeling satisfied with the work, they spend the next three hours repeatedly checking Slack and Jira to see if the Tech Lead or Product Manager has publicly praised them.
The Old/Bad Way: A developer constantly scrolls through LinkedIn, comparing their own career trajectory, salary, and certifications to tech influencers and former colleagues.
Why this fails: Their internal sense of self-worth violently fluctuates based on external, highly curated situations they cannot control.
The New/Good Way: The developer observes this toxic need for external validation, uncovers the insecurity driving it, and reframes their focus onto their actual daily craft.
The payoff: Their career path becomes driven by genuine curiosity and technical mastery, drastically reducing burnout and anxiety.
๐ง The Core Concept
In the AP Framework, the ego depends heavily on maintaining a specific, elevated image. Comparison is the ego's favorite tool to strengthen this image—the mind constantly creates a hierarchy, determining if you are "better" or "worse" than the senior dev sitting next to you.
Self-enquiry asks us to shine a spotlight on this process and examine why external validation exerts such a massive, unearned influence over our inner state.
Here is how the mind structures the trap of comparison:
Root: Social Comparison ├─ Measurement: "How does my code/salary/title compare to theirs?" ├─ Identity: "If they are better, I am inadequate. If I am better, I am superior." └─ Approval: "I need them to validate my superiority to feel safe."
๐ Key Points
- Comparison is the thief of joy: Measuring your behind-the-scenes debugging struggles against someone else's highlight reel will always leave you feeling inadequate.
- Approval is a moving target: If you depend on praise to feel good, you grant your coworkers the power to destroy your mood at any moment.
- Your code is not your identity: A highly optimized
SOQLquery makes you a good programmer; it does not dictate your worth as a human being.
Rule: Understand the psychological need for approval instead of blindly submitting to it.
Gain: Profound inner stability that is immune to office politics and peer reviews.
Price: You have to ruthlessly question your old habits of seeking validation.
Limits: Social comparison is deeply wired into human evolution; the urge to compare will happen in milliseconds.
Mirror (One Transaction): In a team standup, a colleague receives massive praise for a feature you also worked on. Observe your mind's immediate, jealous reaction without acting on it.
Later: You will notice how often you subconsciously fish for compliments.
At Volume: Your architectural choices and career pivots become entirely self-directed, free from the fear of others' opinions.
❓ Core Q&A
No. Enjoying a compliment is a natural, pleasant human experience. The core issue is whether appreciation is simply enjoyed in the moment, or whether your foundational identity depends on it to survive.
A: Because you have intertwined your personal identity with your technical output. If you believe "I am a flawless coder," then a reviewer pointing out an inefficient loop is subconsciously registered by your ego as an attack on your survival, rather than a simple correction of syntax.
A: The ego cannot measure its own worth in a vacuum; it requires a baseline. It uses your peers as a measuring stick to determine if you are "safe" and "successful." Recognizing this mechanism allows you to see your friends' success as data, rather than a threat to your own value.
A: Absolutely. In fact, you will achieve it faster. When you code for the sheer intrinsic joy of building great architecture (the "Flow State"), your work is innovative and bold. When you code just to please a manager, your work becomes safe, derivative, and exhausting.
A: Social platforms are literally engineered to trigger the ego's measurement systems. They display highly curated "wins" (certifications, job offers, flawless deployments) while hiding the late nights, burnout, and rejected interviews. Your brain unfairly compares your messy reality to their filtered highlight reel.
A: Notice your physical and verbal cues. Do you immediately agree with a dominant architect even if you spot a flaw? Do you laugh nervously at jokes that aren't funny? Do you feel tension in your stomach when you propose an idea? That physical tension is the ego bracing for potential rejection.
A: When you no longer need your coworkers to validate you, you stop competing with them. You transform from a defensive, insecure developer into a highly collaborative team player who can celebrate others' victories because they no longer threaten your own identity.
๐ Connecting the Dots (Follow-up Q&A)
A: Pair programming requires vulnerability. When you desperately need approval, you hide your ignorance, agree with bad architectural ideas just to seem agreeable, or compete to write the "smartest" line of code. Without the need for approval, you openly admit when you don't know syntax, ask "dumb" questions, and focus strictly on building the best logic together. It transforms from a performance into a genuine collaboration.
A: Focus the language entirely on the system, not the coder. Instead of saying, "Your logic here is flawed," say, "This SOQL query might hit governor limits at scale." Ask guiding questions rather than issuing edicts (e.g., "What happens to this data loop if the payload doubles?"). This invites the junior developer into an objective problem-solving mindset rather than backing them into a defensive corner.
A: Practice "Labeling the Log." At the end of the workday, review your unfinished Jira tickets. Instead of letting your brain think, "I failed to finish my work today," consciously relabel it: "These tickets carry over to tomorrow." Remind yourself daily that Agile points are merely a metric to measure time and complexity, not human value. Celebrate learning a new concept just as much as you celebrate moving a ticket to 'Done'.