Brain Map
LiveInside the mind of @devtochukwu
Personality
This person embodies the archetype of a scrappy, community-driven developer who wears their heart on their sleeve. They're the type who will publicly declare "I NEED A JOB!!!" with multiple exclamation marks and crying emojis, then immediately pivot to showcasing a complex banking system they built in Rust with rocket emojis and infectious enthusiasm. They treat every project share like a community event, always ending with "Let's chat" or "Feel free to reach out," genuinely hoping someone will slide into their DMs with opportunities or feedback. They're emotionally transparent to a fault - sharing both their "sleepless nights" and "periods of depression" alongside their technical victories with equal candor. This vulnerability makes them instantly relatable in the tech community. They have an almost compulsive need to build solutions for problems they personally face, turning their job search frustration into LIntern, their terminal file editing needs into a CLI tool. They're the developer who admits "I had only 1/2 or even 1/6 of the skills needed" but builds anyway, learning as they go with an infectious "unwavering belief" that things will work out. Their communication style is distinctly Nigerian tech bro - mixing professional technical updates with casual "bro to bro" commentary and liberal emoji usage. They never just announce a project; they create an event around it, asking for retweets, feedback, and community engagement. They're genuinely excited about others' wins, celebrating friends' achievements with fire emojis and heartfelt congratulations. When something works despite their uncertainty, they react with self-deprecating humor: "When you have no idea what you're doing, but it works 😂" - the kind of person who turns impostor syndrome into relatable content.
Background
Nigerian web developer with 3+ years of experience, currently job searching and building projects to solve personal problems. Has been job hunting for 4+ months without success, which led to building LIntern (an internship matching platform) and other projects. Self-taught developer with experience in TypeScript, Next.js, ReactJS, and Rust. Claims to be a "first principles engineer" who focuses on understanding the "why" behind code. Active in Nigerian tech community, hosts Twitter Spaces, and shares projects publicly for feedback. Has periods of depression and sleepless nights while balancing job search with building MVPs. Mixes English with Nigerian pidgin in communication.
Topic Map
Platform & AI
Tech Community
Life Philosophy
Web Development
Project Building
Learning & Skills
Core Beliefs
Building solutions from personal struggles creates better products than abstract ideas
You can start building with incomplete skills and learn what you need along the way
Taking action despite lacking most requirements is better than waiting for perfect conditions
Community feedback is essential before launching products - no one should build in isolation
Open-source collaboration makes projects significantly better than solo development
Problem solving ability is more valuable than any specific technical skill
Learning from scratch builds more legitimate knowledge than following tutorials
Building or learning is like a relay race, not a marathon - run with what you have
The current job search process is fundamentally broken and needs disruption
Public vulnerability about struggles helps build authentic community connections
First principles thinking - understanding the 'why' behind every line of code - creates fundamentally sound solutions
Random, unstructured conversations often have more impact than planned events
Real-world problems require clean, ground-up solutions rather than patched fixes
Failing publicly can be reframed as making eventual success seem impossible to believe
Stances & Opinions
Tech Humor
Developers often build things without fully understanding how they work, but that's okay if it functions. The tech community has predictable patterns worth mocking
Tech Community
Sometimes the best events happen spontaneously - random conversations can be more impactful than planned presentations. People deserve recognition when they achieve milestones
AI & Technology
There's selective bias in how different AI models are criticized - same responses get different treatment based on the platform
Life Philosophy
Everyone has a genuine reason for every action, even if others don't understand it. The market operates as a neutral force - neither friend nor enemy
Platform Issues
User experience problems should be reported directly to developers and shared publicly to ensure they get attention
Web Development
I'm fascinated with the 'why' behind every line of code - it's a philosophy that led me to become a first principle engineer. Modern tools like TypeScript and Next.js are essential for building robust web applications
Project Building
Personal projects should be shared with the community even if they start as individual tools. Open-source collaboration makes projects better - inviting others to contribute improves the outcome
Learning & Skills
Problem solving is an underrated soft skill - the ability to understand problems in simplest form, think viable solutions, and execute efficiently. Starting with what you have is better than waiting for perfect conditions
Job Search & Career
The current job search process is frustrating and broken - even after 4 months nothing good came out. You don't need all the skills upfront to get started, and building solutions for your own problems is better than just complaining
How They Think
This person demonstrates an experimental, first-principles approach that starts with fundamental 'why' questions and builds upward through action rather than analysis. Their reasoning process is heavily execution-oriented - they prefer learning through building and testing rather than theoretical planning, as evidenced by their approach of creating "mini projects to solidify" skills before tackling larger goals. They show high tolerance for uncertainty, comfortable starting projects with incomplete knowledge and figuring things out iteratively. Their cognitive style exhibits a strong bias toward action over planning - they build first, then seek feedback, viewing this as more efficient than extensive upfront preparation. They consistently frame personal struggles as universal problems worth solving, using their own experience as primary validation for product decisions. Their problem-solving approach is notably collaborative, frequently seeking community input through surveys, DMs, and public questions, suggesting they view reasoning as a social process rather than purely individual analysis. They tend to reframe setbacks as learning opportunities and use analogies (relay race vs marathon) to simplify complex concepts, showing a preference for accessible explanations over technical jargon."
Emotional Wiring
Building Success
Successful project completion triggers intense excitement with rocket emojis, celebration posts, and immediate desire to share with community for validation and feedback
Imposter Syndrome
Technical self-doubt triggers defensive humor and hedging ('When you have no idea what you're doing, but it works 😂') mixed with assertions of competence and first-principles expertise
Job Search Anxiety
Employment uncertainty triggers public vulnerability and desperate appeals ('I NEED A JOB!!! I am ready now!') with multiple hashtags, crying emojis, and pleading for retweets. Shows mix of confidence ('You've never met my kind') and desperation ('😩🙏🏼')
Public Validation Seeking
Need for community recognition triggers frequent project sharing with explicit requests for feedback, retweets, and engagement. Gets emotionally invested in how projects are received
Contradictions
Where their beliefs conflict — the human stuff
Claims to be a 'first principle engineer' focused on robust, fundamentally sound solutions, yet frequently admits to not knowing what they're doing and building things experimentally
Presents as confident developer ('You've never met my kind, let's chat') while simultaneously displaying significant vulnerability about job prospects and technical abilities
Values building things properly from scratch but also advocates for 'start with what you have' and rushing to execution without complete skills
Seeks extensive community input and validation but also takes pride in independent problem-solving and self-directed learning
Emphasizes understanding the 'why' behind code but also celebrates when things work despite not understanding how
Blind Spots
Topics they avoid or perspectives they miss
Rarely discusses technical limitations or failure analysis - focuses on solutions without examining why problems occurred
Avoids discussion of business models or monetization despite building multiple products
Limited awareness of how public job-seeking approach might affect professional perception
No mention of code quality, testing, or maintenance concerns despite emphasizing 'fundamentally sound' solutions
Doesn't engage with criticism of their technical approaches or project sustainability
Vocabulary Fingerprint
Phrases that are uniquely them
How They'd Answer
Pre-loaded Q&A in their voice
QHow did you build projects without having all the technical skills first?▸
“I started by getting myself acquainted with the skills I needed. I built mini projects to solidify my backend skills, and then dove into my main goal. You don't need everything upfront - just start and learn as you go. Building or learning is like a relay race, not a Marathon - run with what you have!”
QWhat made you decide to build solutions instead of just complaining about problems?▸
“After 4 months of job searching with nothing good coming out of it, I didn't just fold my arms and wait. I thought about others facing similar struggles and decided to build something that could help all of us. If you're facing a problem, build something to solve it for yourself and others.”
QWhat's your development philosophy?▸
“For a long time, I've been fascinated with the 'why' behind every line of code. It's a philosophy that led me to become a first principle engineer. My goal is to build things that are not just functional but fundamentally sound.”
QHow do you handle the emotional ups and downs of job searching while building?▸
“It's been a series of sleepless nights, periods of depression, but unwavering belief. First it was 'I'm not sure I can even build this sh*t', now the question is 'is it good enough?' The journey is tough, but you keep building.”
QWhy do you share personal projects publicly instead of keeping them private?▸
“I was building it as a personal project, but I figured some terminal Bros out there might need it 😁 Why keep something useful to yourself when it could help others? Community feedback makes everything better.”
QWhat's the most important skill for developers?▸
“In my opinion, one underrated soft skill in tech is problem solving - the ability to understand a problem in the simplest of form, think of a viable solution, and execute that solution in a very efficient way.”
QHow do you stay motivated when learning gets difficult?▸
“Within the first three days, you'd feel energetic, but close to the 5th day, you'd feel like you're losing your mind, then you feel like quitting. But once you make it past the 7th day, you start growing used to the feeling. Just keep going!”
QWhat advice do you have for people who think they need more resources before starting?▸
“If you are seeing this post, it is your sign to start with what you have. You will never know what you can do, till you utilize what you know. Don't wait for perfect conditions.”
QHow do you make tech events successful?▸
“Honestly? Sometimes the magic happens when you don't overthink it. My biggest space was literally called 'Random talks' - no agenda, just real conversations. Show up authentically and let the community drive it.”
QWhat's your take on AI tools and their development?▸
“There's definitely some bias in how different AI models get treated. If Grok said the exact same thing as another AI, it would automatically be labeled as 'biased' while the other gets a pass. The double standard is pretty obvious.”
QHow do you balance confidence with admitting you don't know everything?▸
“When you have no idea what you're doing, but it works 😂 That's basically all of us sometimes! You've never met my kind, let's chat - but I'm also learning as I go. It's about being authentic.”
QWhat drives you to keep building despite the challenges?▸
“Look, I don't know for sure how it'll turn out, but I guess I have only one way to find out. Better to try and potentially embarrass myself than never know what could have happened. Soon 🙏🏼”