Shareable analysis for @Nakamoto_days

Personality Dossier55 posts analyzed
@Nakamoto_days avatar

Nakamoto Days

@Nakamoto_days

The Iterative Maker (product-minded engineer documenting progress)

Builder-analyst in public: pragmatic, improvement-driven, lightly self-deprecating

Confidence

73/ 100
x
Overview

@Nakamoto_days reads as a technically oriented builder who publicly tracks day-by-day progress, actively seeks feedback, and optimizes for shipping an MVP. The tone mixes pragmatic problem-solving (stack choices, validation, analytics) with occasional philosophical prompts and humor about debugging, producing a profile that is conscientious and curious but not highly socially expressive.

Big Five (OCEAN)
OpennessCuriosity & imagination
74High
x

High openness shows up in curiosity about new concepts (e.g., GEO, AI tooling), comfort with abstraction, and desire to differentiate aesthetically despite relying on common templates.

ConscientiousnessOrder & self-discipline
78High
x

Strong conscientiousness is reflected in routine progress logs, MVP focus, and systematic emphasis on validation/testing—even when plans fall short.

ExtraversionSociability & energy
44Moderate
x

Moderate-to-low extraversion: the account engages the community for feedback and recommendations, but self-disclosure is sparse and interaction is mostly task-focused rather than socially expansive.

AgreeablenessWarmth & cooperation
62Moderate
x

Moderate agreeableness: generally cooperative, helpful, and encouraging, with occasional blunt critique (e.g., tool comparisons, AI frustrations) expressed without hostility.

NeuroticismEmotional volatility
52Moderate
x

Moderate neuroticism: visible frustration and self-critique during technical setbacks, balanced by humor, persistence, and quick reframing toward solutions.

Enneagram
3

The Achiever

Wing 3w4Tritype 3-5-1

67/100 confidence

Core motivation

To be effective and demonstrably competent—shipping, improving, and being seen as capable through real outputs.

Core fear

Being ineffective, failing to deliver, or having work seen as unoriginal/without impact.

Type 3 fits the strong output orientation (daily progress tracking, MVP acceleration, waitlist building, impact metrics) and performance framing (“mistakes to avoid,” shipping quickly, validating demand). The 4-wing shows in the recurring concern with sameness and the push for a distinctive ‘twist’ in design/identity. A 5 fix appears in the technical depth and analytical focus (stack decisions, subnet metrics, AI analysis), while a 1 fix shows in improvement language and standards around validation, UX simplicity, and doing things ‘properly’ (self-hosted/no-KYC, control over auth).

Alternative read

Type 5 The Investigator. The account is heavily centered on systems, tooling, analysis, and technical competence; if the public progress logging is more about documenting knowledge than achievement/status, a 5 (likely 5w6) could explain the same behavior.

Communication style

Concise, builder-log style: short status updates, checklists, product positioning bullets, and pragmatic Q&A replies; uses light humor and occasional philosophical prompts to vary the feed.

Emotional tone

Mostly steady and solution-focused; brief spikes of frustration or disappointment during bugs/setbacks; generally optimistic persistence.

Core values
Pragmatism and iteration (ship MVP, test, refine)Autonomy/control over stack (self-hosting, owning auth/payment choices)Simplicity (UX simplicity, preference for simple designs)Learning in public and feedback loops (community input, validation)Competence and measurable impact (metrics, progress proof)
Interests & themes
SaaS building in publicDeveloper tooling (auth, payments, deployment)AI applications and limitations (Qwen, dashboards, AI analysis)Crypto/Bitcoin and Bittensor ecosystem ($TAO, subnet analytics)Design/UX and product differentiation
Strengths
  • High follow-through and iterative execution under uncertainty
  • Practical product thinking (validation, MVP, UX simplicity)
  • Comfort with technical complexity and systems integration
  • Good use of community as a feedback/learning channel without over-sharing
  • Resilience: reframes failures into debugging/analysis workstreams
Potential blind spots
  • Over-ambitious scoping and timeline pressure (to-do lists that outgrow available time)
  • Perfectionism around originality/design could slow shipping or satisfaction
  • Oscillation between many tools/features (payments, auth migrations, AI features) may increase cognitive load
  • Occasional frustration with imperfect tools (AI, APIs) could bias decisions toward control-heavy solutions
Notable quirks
  • Tracks work as ‘Day#’ reports with mini-retrospectives
  • Uses playful ‘debug, create bugs’ humor to narrate stress
  • Mixes highly technical posts with small lifestyle notes (gym, cooking, adopting a puppy)
  • Explicit skepticism about template-driven sameness in SaaS dashboards

This assessment is limited to public, short-form posts that are heavily project-centric; offline behavior, deeper relationships, and stable long-term patterns can’t be verified. Low follower count and a niche build-in-public context may amplify performance/marketing language relative to the person’s broader personality.