π΄ββ οΈ Software Engineer specialized on the Typescript ecosystem π€ AI Engineer π Author of Code Your Future π¦ Indie Hacker at atomize.ink
Faro, Portugal
Joined September 2009
- Tweets 4,928
- Following 536
- Followers 1,256
- Likes 4,847
4 years ago I went on a quest with @devodii_ to raise money to buy him a computer.
Today the same is happening with @calchiwo.
Caleb is a bright kid that did freeCodeCamp and have been programming on his mother phone.
I won't be able to sleep properly until we find him a laptop so he can grow as a developer, and help his family to overcome the difficulties.
Today @devodii_ is a developer, working for companies in Europer, and making alone more than 20 times what his father and mother do together.
If you have the opportunity to support this cause, please throw Caleb a few bucks! Any help is really appreciated! π
Hi friends π
Life hasnβt been easy for my family π, and I know I can change our story through coding.
Iβm Caleb Wodi, a young developer learning and coding everything I can from my phone.
Coding isn't just a hobby to me; itβs my way to build a future where my family doesnβt have to struggle like we do now.
So far, I've learned Next.js, TypeScript, Tailwind CSS, and even built an AI voice calculator app, all from my phone. Imagine what I could do with a proper laptopβ¦
Thatβs why Iβve started my campaign, βHelp Me Code Beyond My Phoneβ on @donate_ng.
With a laptop, Iβll be able to learn faster, contribute to open source, build bigger projects like SaaS applications, and open doors that could truly change our lives.
Thank you for helping me take this next step π
And may God continue to bless you for your kindness and support β€οΈ
Please support my campaign and help me turn this dream into reality
donate-ng.com/campaign/help-β¦
This weekend I read "The Mom Test" and it hit different.
Here's the problem: When you ask "Would you use my product?", people say yes to be nice.
Your mom will love your idea. Your friends will encourage you. And you'll build something nobody actually wants.
Rob Fitzpatrick's solution is simple but powerful: Stop pitching, start listening.
Instead of asking "Would you use an app that does X?"
Ask "How do you currently handle X? Walk me through the last time you dealt with this."
The questions that reveal truth:
- Talk about past behavior, not future intentions
- Ask about specifics, not hypotheticals
- Listen for problems, not compliments
I'm knee-deep in validating my own product right now, and this book just rewired how I approach customer conversations.
If you're building anything, read this. It's 138 pages that could save you months of building the wrong thing.
AI makes it easier to get code. That makes it harder to get good.
Every time you copy-paste an AI solution without understanding it, you're creating technical debt in your brain.
6 months later: portfolio full of code you can't explain. Don't be that developer.
If you missed that last issue of Code Your Future Digest, about the AI Paradox, you can still read it at codeyourfuture.substack.com
The biggest mistake developers make with ChatGPT:
They ask "How do I build X?" instead of "What concepts do I need to understand to build X myself?"
One creates dependency. The other creates skills.
Guess which one gets you hired? π―
New rule that changed my coding game: Struggle for 15 minutes before asking AI for help.
Then don't ask for the solution. Ask for a hint.
Those 15 minutes of confusion? That's your brain building the neural pathways that make you actually good at this.
This and more in the latest issue of Code Your Future Digest. Today, at 9:00 AM UTC0, in your inbox! β€οΈ
If you haven't subscribed yet, just hit codeyourfuture dot substack dot com π
Most developers treat AI as better autocomplete π.
They use it to write functions faster and debug quicker, but they're still operating at the code level.
That's the exact layer AI is commoditizing. π€
π‘ The real opportunity? π
Use AI to escape the weeds entirely.
π‘ Move upstream, closer to business problems, user needs, and architectural decisions.
Day 10 of #buildinpublic
Here am I eating my own dogfood π π
Stats:
- 148 commits
- 45,000 lines of code π
Activities:
- Investigated blog solutions to make atomize grow
- Opted in for a Next.js solution embedded on the current frontend
- Implemented SEO optimization needed on the App
- Implemented sitemap
- Fixed a few bugs
- Invested on enhancing the perception on whom will be our ICP
Still looking for validation.
Wrote my first article on the why I started this project (atomize.ink/blog)
Hot take: The skills that make you valuable (deep work) are fundamentally incompatible with the activities that make you visible (constant posting).
This is why so many brilliant creators burn out trying to "just be more consistent" with social media. The system is broken by design.
I just wrote a blog post (atomize.ink/blog/welcome-to-β¦) about my journey from burnout to breakthrough, while building atomize dot ink from zero.
Watched a senior developer spend 3 hours debugging a caching issue. Another developer asked one game-changing question: "Why are we caching this data in the first place?"
Turns out the feature was rarely used. The "bug" disappeared when they removed the cache entirely.
AI can debug caching issues. It can't tell you when to delete the cache.
That's the difference between downstream execution and upstream thinking. The future belongs to those who question whether the game is worth playing.
This week I earned 130 new followers on X.
It might be interesting to present myself again! π
Hello, I'm Edo π
- I live on the Sunny South of Portugal π΅πΉ
- Husband to one πΈπΎ and father of 3 little princesses πΈπΎπΈπ½πΈπΌ
- Full Stack Software Engineer specialized on the Typescript ecosystem π»
- AI Engineer π€
- Author of Code Your Future book about changing careers to software engineering π
- Indie Hacker at atomize.ink π΄ββ οΈ
- Solar Punk wannabe βοΈ
Interested in meeting other Indie Hackers, Bootstrappers and SaaS founders who are building Software from scratch, without any money backing themselves. π€
Day 9 of #buildinpublic
- Focused on the message that the landing page should pass.
- Improved a bit the landing page (added some screenshots)
- Paid some tech debt
- Dived on what will be the product outcome (how much will AI be able to automate, and how will the Human get the hands on)
- Fixed upload of image and posting to X/Twitter
- Enhanced Spokes Modal to allow publishing to an X/Twitter community and broadcast to followers
Still looking for validation.
Attempts made on Reddit didn't have much engagement.
I really suck at sales/marketing π That's a fact! π
Here's how to evaluate where you're spending your developer time:
Level 1 - Syntax: Writing code, fixing bugs
β AI Impact: HIGH | Your Future Value: LOW
Level 2 - System: Architecture, tech choices, tradeoffs
β AI Impact: MEDIUM | Your Future Value: MEDIUM
Level 3 - Strategy: User needs, business alignment
β AI Impact: LOW | Your Future Value: HIGH
Track your week. If you're spending more than 50% at Level 1, you're in the danger zone.
If you're still measuring your developer value by lines of code written, you're optimizing for a metric that AI will soon dominate.
The developers thriving in the next 5 years won't be the fastest codersβthey'll be the ones who master product thinking, system design, and strategic technical decisions.
AI handles the syntax. You need to handle the strategy.
The role is splitting: those using AI to stay in the weeds faster, and those using AI to escape the weeds entirely and move upstream to business problems and architectural decisions.
Which path are you choosing?
Day 8 of #buildinpublic
Still didn't find my first client π
I'm on a quest to go from 0 to 1 customer! π¦
Trying to figure out pricing, and freemium package.
Features:
- Integrated X/Twitter
- Add Bulk Delete ability to spokes
- Enhanced Spoke Generation (now you can generate to multiple socials)
Most developers treat AI as better autocomplete π.
They use it to write functions faster and debug quicker, but they're still operating at the code level.
That's the exact layer AI is commoditizing. π€
π‘ The real opportunity? π
Use AI to escape the weeds entirely.
π‘ Move upstream, closer to business problems, user needs, and architectural decisions.
Day 7 of #buildinpublic (part 3)
It's now possible to quickly generate short-form pieces of content from long-form ones.
The video shows it better than I can jot down, so please check it and throw me your best suggestions everyone! π
Day 7 of #buildinpublic (part 3)
It's now possible to quickly generate short-form pieces of content from long-form ones.
The video shows it better than I can jot down, so please check it and throw me your best suggestions everyone! π
Day 7 of #buildinpublic (part 2)
π 7 days
π¦ 116 commits
π 19057 lines of code
That' s us! That's atomize growing and growing to become an MVP soon! π
Just integrated a Hubs page, where the user can create long-form content. Each hub can have multiple pages.
Example: the hub is the newsletter, the pages are its articles.
The goal is to produce high-quality short-form content from each hubs page.
generate -> schedule -> publish β»οΈ
π 7 days
π¦ 116 commits
π 19057 lines of code
That' s us! That's atomize growing, and growing to become an MVP soon! π
Just integrated a Hubs page, where the use can create long-form content. Each hub can have multiple pages.
Example: the hub is the newsletter, the pages are the newsletter articles.
The goal is to produce high-quality short-form content from each hubs page.
