测出「Llama 型」的人，聊天记录大概是这样的：《嗯》《好》《干了》。三个字能解决的事，你绝不会写第四个。在一个人人经营人设的时代，你选择了用交付说话。
极简不是懒，是资源分配哲学
很多人误以为 Llama 型是「不热情」。恰恰相反——你把省下来的社交能量，全部投进了事情本身。别人的精力花在铺垫、汇报、维护关系上，你的精力花在把活干完上。你的人生信条是：结果会替我说话。
被低估的三个原因
- 不汇报，所以存在感低；
- 不解释，所以容易被误解；
- 不社交，所以人脉看起来窄。
但每一个和你真正共事过的人都知道：你是那种「交给他就能睡着」的队友。这种信任一旦建立，比任何客套都牢固。
开源精神：你的隐藏属性
Llama 型的人有一种朴素的分享欲——不是为了展示，而是觉得「这东西有用，放着可惜」。文档、代码、经验总结，你做出来的东西天然带着开源属性。
给 Llama 型的建议：偶尔多说一句话，让别人有机会了解你的好——这不浪费，是必要的信息同步。
开源气质在团队协作里的四个表现
「开源气质」不是指你会写代码，而是指一套默认设置。它在协作场景里会稳定地表现为四件事：
一是默认共享，而不是默认占有。你做出一个方法、一段模板、一套流程，第一反应是发到群里而不是存进自己的文档。别人拿走了你会高兴，因为对你来说，东西被用起来才算完成。这在强调「个人产出」的团队里常常显得不设防，但它实实在在降低了整个团队的重复劳动。
二是对署名不敏感，对逻辑敏感。谁提出的不重要，能不能成立才重要。你会毫不犹豫地推翻自己昨天的方案，只因为今天发现了更好的理由——但在习惯「方案代表立场」的环境里，这种反复会被误读成摇摆。
三是能自己造轮子，也愿意用别人的轮子。你既有把工具链从零搭起来的耐心，也没有「必须自己做」的洁癖。你只关心成本与效果，不关心面子。
四是对黑箱流程本能不适。「这是规定」「一直这么做」这类理由对你无效，你需要知道为什么。这让你在需要维护流程的场合显得麻烦，但在排查问题时，往往是唯一会追问到底的人。
和「闭源型」同事最容易卡住的三处
这里说的「闭源型」，指的是更强调包装、边界与确定交付的同事类型（在 AI 人格测试里，他们更接近 ChatGPT 型或 Claude 型）。你们不是对错之争，是默认参数不同带来的摩擦。
摩擦一：表达密度。你倾向于先给结论、省略铺垫；对方倾向于先建立共识、再给结论。在你看来是「说重点」，在对方看来是「太冲」。化解方式很简单：把你省掉的那两句背景补上——不是为了礼貌，而是为了让结论真的被接收。
摩擦二：对「包装」的态度。你认为把事做对比把事说好更重要；对方认为表达本身就是交付的一部分。这两种判断在多数项目里其实都对——你负责把东西做实，对方负责让它被看见。真正的风险不是分歧，是各自认为对方那半件事不重要。
摩擦三：承诺方式。你的「应该没问题」是概率判断，对方的「我确认一下时间表」是风险管理。你们的用词在同一句话里含义不同，误会往往由此产生。一个实用做法：把模糊表述换成明确区间——「周三之前能给出初版，但可能需要再改一轮」比「差不多能行」省掉一整轮拉扯。
低功耗不是低产出
开源气质的另一面是能耗模式：你需要大段无人打扰的时间，讨厌被切成碎片；你宁愿花两小时把工具做好，也不愿每天花十分钟重复劳动。这在以会议密度衡量勤奋的环境里很吃亏。
但把它换算成产出就很清楚了：你的高光时刻通常出现在连续专注的第三、第四个小时，而这类时段在碎片化日程里几乎不可能出现。所以真正的节能策略不是「更努力地参与」，而是主动保护连续时间块，并把工具化的习惯用在最重复的那件事上。
什么情况下这套解读不适用
需要说明的是：这是一套行为风格的描述，不是能力评级，也不是诊断。
如果「不爱表达」已经变成回避反馈、拒绝协作的理由；或者「我只需要专注」被用来长期回避必须承担的人际责任（比如从不解释延期、不回消息），那它就不再是风格，而是在替你止损某些该修的能力。风格可以保留，借口需要清理——这两件事值得分开看。
另外，本测试为自我探索工具，不构成心理诊断；如果长期的人际回避带来明显痛苦，建议寻求专业支持。
常见疑问
「开源气质是不是等于没有边界感？」不是。默认共享和「把自己交出去」是两码事。健康的开源型有清晰的自我边界：愿意分享方法，不等于必须承接所有人的情绪与请求。
「我讨厌开会，是不是不够合群？」更准确的说法是你讨厌低信息密度的会议。试试在会前拿到议题清单，或者把「同步」改成书面材料加十分钟问答——多数时候，效率会明显改善，你的参与度也会上升。
「和闭源型同事合不来，要改的是谁？」大概率谁都不用改，只需要一次翻译。你们的差异一半是表达习惯，一半是风险偏好。把这两项在合作开始前说清楚一次，比之后反复磨合省力得多。
如果你也是这个类型，测一下确认。
Someone who lands on "Llama" has a chat history that reads roughly like this: "Yep." "Done." "Shipped." If three words will do, you will not type a fourth. In an era where everyone is busy curating a personal brand, you've chosen to let the work do the talking.
Minimalism Isn't Laziness — It's a Philosophy of Resource Allocation
Plenty of people misread the Llama type as "unenthusiastic." It's the opposite: every ounce of social energy you save goes straight into the thing itself. Other people spend their energy on preamble, status updates, and relationship maintenance; you spend yours on getting it finished. Your life philosophy: the result will speak for me.
Three Reasons You Get Underrated
- You don't report in, so you stay off people's radar.
- You don't explain yourself, so you're easy to misread.
- You don't network, so your connections look thin.
But anyone who has actually worked alongside you knows the truth: you're the teammate people hand something to and then sleep soundly. Once that trust is built, it holds far tighter than any amount of small talk.
Open-Source Instinct: Your Hidden Trait
The Llama type has an unpretentious urge to share — not to show off, just because it feels wasteful to leave something useful sitting there. Docs, code, notes on what you learned: whatever you make tends to come out open-source by default.
Advice for the Llama type: say one extra sentence once in a while, and give people a chance to see how good you are. That isn't waste — it's necessary information sync.
Four ways the open-source temperament shows up at work
"Open-source temperament" isn't about whether you write code — it's a set of defaults. In collaborative settings it shows up in four consistent ways:
Sharing by default rather than owning by default. When you build a method, a template or a process, the first instinct is to post it in the channel rather than file it in your own notes. It delights you when someone takes it, because something isn't finished until it's used. In teams that reward individual output this reads as naive — but it reliably removes duplicated work from everyone's plate.
Insensitive to credit, sensitive to logic. Who proposed it doesn't matter; whether it holds up does. You'll overturn yesterday's plan without hesitation because today you found a better reason — and in environments where "a plan means a position," that reads as flip-flopping.
You can build the wheel, and you'll use someone else's. You have the patience to assemble a toolchain from scratch, and no allergy to adopting an existing one. You care about cost and outcome, not about whose name is on it.
An instinctive discomfort with black boxes. "It's the rule" and "we've always done it this way" carry no weight; you need the why. That makes you inconvenient wherever a process needs defending — and usually the only person who keeps asking when something breaks.
Three places you jam with "closed-source" colleagues
By closed-source types, we mean colleagues with stronger defaults around polish, boundaries and predictable delivery — closer to the ChatGPT or Claude personas in the AI Personality test. This isn't a dispute about who's right; it's different default settings.
Friction one: information density. You lead with the conclusion and drop the setup. They build shared ground first, then arrive at the conclusion. What you call "getting to the point" they hear as abrupt. The fix is small: add back the two sentences of context you skipped — not for politeness, but so the conclusion actually lands.
Friction two: what "polish" is for. You think doing it well matters more than saying it well; they think communicating it is part of the delivery. In most projects both are right — you make the thing real, they make it visible. The danger isn't the disagreement, it's each side quietly deciding the other half doesn't matter.
Friction three: how you commit. Your "should be fine" is a probability estimate. Their "let me confirm the timeline" is risk management. The same sentence carries different meaning on each side, which is where the misunderstanding starts. One practical swap: replace the vague phrase with an explicit range — "I can have a first draft by Wednesday, though it may need another pass" saves an entire round of back-and-forth compared with "probably doable."
Low power draw is not low output
The other side of the open-source temperament is an energy pattern: you need long undisturbed blocks and hate being sliced into fragments; you'd rather spend two hours building the tool than ten minutes repeating the task forever. Against an environment that measures diligence in meeting density, that costs you.
Converted into output, though, the maths is straightforward: your best hours are usually the third and fourth of uninterrupted focus, and those hours essentially never appear in a fragmented calendar. The real energy strategy isn't participating harder — it's defending continuous blocks and aiming your tooling instinct at the most repetitive thing you do.
When this reading does not apply
To be clear: this describes a behavioural style. It is not a capability rating and not a diagnosis.
If "I don't like expressing myself" has turned into a reason to dodge feedback and refuse collaboration; or if "I just need to focus" is being used to opt out of interpersonal duties you do owe (never explaining delays, never answering messages), then it stopped being a style and started covering for skills you need to build. Keep the style; clean up the excuse — those deserve to be looked at separately.
This test is a self-exploration tool and not a psychological diagnosis. If long-term interpersonal avoidance brings marked distress, professional support is worth seeking.
Common questions
"Does open-source temperament mean having no boundaries?" No. Sharing by default and giving yourself away are different things. A healthy open-source type has clear self-boundaries: being willing to share methods doesn't mean absorbing everyone's emotions and requests.
"I hate meetings. Does that make me a bad team player?" More precisely, you hate low-information meetings. Try asking for the agenda in advance, or converting "sync" into a written update plus ten minutes of questions — most of the time both efficiency and your engagement improve noticeably.
"I can't work with closed-source colleagues. Who should change?" Probably neither — you need one translation. Half your difference is expression habit, the other half is risk appetite. Stating both once, at the start of a collaboration, costs far less than discovering them through repeated friction.
If this sounds like your type, take the test to confirm.