Community Challenge 3/52: 1 week to code an app
One week ago I couldn't build an app.
I don't know Python. I don't know JavaScript. I couldn't tell you the difference between a function and a variable.
But I had this idea: a habit tracker for the 53skills community.
Something simple where we could all track our weekly skill progress together, compete on leaderboards, and actually see our transformation over time. link at the end to try it :)
So the challenge of week 3: 7 days to learn coding and build.
Today, I'm writing this from an airport.
In a few hours I'll be in Santa Barbara, California, ready to start Week 4: talking to 50 complete strangers about this project.
But first, let me tell you what I actually learned this week.
Because it wasn't actually coding…
Lesson 1: You learn systems thinking, not syntax
Here's what surprised me most.
When you build this app, you have to ask questions like: What if a user misses a day? What if they want to change their skill mid-week? What if they need to add notes? What happens when someone logs in for the first time vs. the tenth time?
These aren't coding questions. These are product questions. Logic questions.
The AI wrote most of the code. It's honestly pretty good at it. But my job was knowing exactly what to ask for.
That's the skill.
Lesson 2: 1 hour of planning beats 10 hours of building
I made the classic beginner mistake.
I jumped straight into building. Talked to AI, got something that "worked,"
and it looked like garbage..
my senior developer friend gave me great advice that changed everything: "plan properly."
So I spent one hour going deep on the features I actually wanted. The user flow. The screens. The logic.
The next version was 10x better.
Same AI.
Same tools.
Different input.
The problem was my thinking. I made like 6 versions, each better than the last.
Lesson 3: AI codes. YOU THINK.
This is the part most people get wrong about AI-assisted development.
They think AI replaces the thinking. It doesn't. It replaces the typing.
You still need to know what you want. You still need to understand why something isn't working. You still need to debug your own logic before you debug the code.
I recommend using voice to interact, because you will realize how unclear you can be.
Lesson 4: Product thinking matters more than programming
I went into this week expecting to learn JavaScript.
I came out understanding user journeys, feature prioritization, authentication flows, and database structure.
I learned more about how products are built than how code is written. And honestly that's more valuable.
Because code changes. Frameworks change. Languages change.
But knowing how to think about what users need and how to deliver it is forever.
Lesson 5: Iteration beats perfection
My app went through 6 versions in 7 days.
Version 1 was boring. A basic tracker with no soul.
Version 3 had animations. Version 5 had the six growth paths. Version 6 finally had what I wanted: character profiles, stats, custom tips, and community leaderboards.
If I had waited until it was "ready," I'd still be planning.
Ship ugly. Fix fast. Repeat.
Aaaaaaaand:
The app is live. You can try it! 🙂
It's not perfect. But it works.
You can create your account, pick your skill for the week, check in daily, and see how you stack up against other Neohumans on the leaderboard.
Try it here: https://skills53.lovable.app/
It's free. Let me know what breaks.
What's next: 50 strangers in Santa Barbara
By the time you read this, I'll be in California.
Week 4 is Cold Approach: talk to 50 complete strangers about 53skills. Get feedback. Get rejected. Get uncomfortable.
This one scares me more than coding honestly.
I'll tell you how it goes. or follow on Insta:
See you next week,
Alex
P.S. If you're learning a skill this week, reply and tell me what it is. I read every response.
If you missed week 2, HERE are the 7 lessons for language learning.
#53skills
Reply to this email with all your questions, comments, or tips, I will answer.
Or share with friends who want to join.
- Alex
