Boost Your Tech Skills by Leveraging Cognition and Human Nature

In a recent internal sharing session, the author discussed how applying insights from cognition and human nature can elevate a developer's technical level, drawing parallels with product‑manager thinking while emphasizing empathy.

Understanding human nature helps improve cognition, and narrow technical skills (Java, PHP, Android, Spring, Vue, etc.) are merely tools that aid cognition, not cognition itself.

Two key concepts:

Grasping human nature can boost one’s cognition.

Technical skills are tools for cognition, not cognition itself.

Example 1 – Technology Selection

Problem: Evaluating Google’s cross‑platform framework Flutter for mobile development without being misled.

Cognition: Flutter enhances cross‑platform productivity and offers better performance than typical front‑end frameworks.

Explanation: Before Flutter, the author assumed client‑side would be overtaken by web frameworks like React or Vue. Recognizing the trade‑off between cross‑platform efficiency and performance led to choosing Flutter despite its immaturity.

Human nature: Companies often develop overlapping products due to competition and self‑preservation, reflecting natural human drives.

Example 2 – Debugging Online Issues

Problem: Struggling with slow, stressful online issue investigation.

Cognition: Debugging is the cheapest way to train logical thinking, more efficient than writing code.

Explanation: Effective debugging requires deep system knowledge and focusing on the “first scene of the incident,” similar to detective work, rather than chasing recent logs.

Human nature: People prefer low‑effort tasks and may undervalue debugging, but respecting its difficulty leads to better learning.

Example 3 – Technical Interviews

Problem: Interviewers often miss candidates’ true problem‑solving abilities.

Cognition: Independent problem‑solving ability determines interview success; technical depth mainly influences salary.

Explanation: Instead of asking many narrow technical questions, interviewers should explore candidates’ past projects and probe deeper until genuine problem‑solving skills surface.

Human nature: Laziness, face‑saving, and misplaced confidence affect both interviewers and candidates.

Example 4 – Severe Online Failures

Problem: Identifying root causes of critical production incidents.

Cognition: Individual mistakes rarely cause major outages; collective cognitive errors do.

Explanation: Misaligned team perceptions about configuration importance can cascade into failures; correcting collective cognition prevents future incidents.

Human nature: Overconfidence, herd behavior, and laziness contribute to systemic errors.

Example 5 – Code Reuse

Problem: Divergent views on when to abstract and reuse code.

Cognition: Reuse capabilities, not business logic; “separate long‑term abilities from short‑term business needs.”

Explanation: Core capabilities (e.g., payment integration) merit abstraction, while isolated features (e.g., login vs. registration UI) should not be forced into shared code.

Human nature: Rigid rules ignore the need for flexibility in a changing environment.

Example 6 – Open‑Source Significance

Problem: Why Chinese internet companies now heavily promote open source?

Cognition: Open source directly impacts company cost, revenue, and talent acquisition.

Explanation: Public open‑source projects raise a company’s technical reputation, attract top graduates, and can later be monetized through services or licensing.

Human nature: Open‑source contributors seek reputation and profit; adopters seek progress and cost savings.

Key Takeaways – Enhancing Cognition

Keep a Simple Mind

Simplicity in thought allows higher achievement; like the character Guo Jing, a simple, pure mindset leads to mastery.

Embrace Cross‑Disciplinary Insights

Innovation often arises from combining fields (e.g., iPod + phone = iPhone). Diverse interests enrich technical problem‑solving.

Follow Guidance from Higher‑Cognition Leaders

Leaders with broader knowledge can provide valuable direction; trusting their advice accelerates personal growth.

Practice Relentlessly

Only through sustained, real‑project practice can knowledge become true cognition rather than superficial facts.

Ultimately, the era rewards higher cognition over sheer knowledge volume; developers should treat languages, frameworks, and tools as means to train cognition, not ends in themselves.