How I stay consistent with my 365 Days of Code challenge. A lot of people have been asking me how I manage to show up every day, write code, build projects, and share updates everyday. Here’s what has helped me: 1. I don’t wait for motivation. Some days I’m excited to code. Other days, I just want to rest. I’ve learned not to depend on how I feel. I show up regardless. 2. I work on real projects. I’m not just coding for the sake of completing the challenge. I work on products, experiment with new technologies, fix bugs, and build features. Having something meaningful to work on makes it easier to keep going. 3. I document my progress. Sharing what I’m building publicly gives me a way to track my growth. When I look back at older posts, I can see how far I’ve come, and that motivates me to keep going. 4. I don’t try to do everything in one day. I don’t just wake up and start coding randomly. I create a plan for what I want to build and break it down into features I can implement step by step. This gives me direction and helps me stay focused. 5. I focus on showing up, not being perfect. There are days when things don’t go as planned. I’ve learned that consistency isn’t about having a perfect routine; it’s about finding a way to keep moving forward. I’m currently on this journey, and one thing I’ve learned is that consistency becomes easier when you build a system around it instead of relying on motivation alone. You don’t have to do something extraordinary every day. Just make sure you’re moving forward. If you’re working on a long-term goal, start today. Document your progress, stay accountable, and keep going. I’m currently building Coddle Learn, an open source platform for developers and techies to learn, practice and build their portfolio.

Happy New Month everyone 🎉 Welcome to October, the first month of Q4. Q3 was a really productive quarter for me. I built, shipped, learned, and stayed consistent. Here are some highlights from Q3: 👉 Got a new workspace to improve my productivity 👉 Built and launched Coddle AI in public 👉 Scaled Coddle AI to 300+ users 👉 Built and completed Fastpay, a fintech mobile app 👉 Pitched successfully at a hackathon 👉 Stayed consistent with my 365 Days of Code 👉 Got new contracts to work on for different clients For Q4, the goal is simple: execute better, build more, and stay consistent. One thing I’ve learned about consistency is that you don’t always need motivation. Here are some tips: 1. Set clear goals. 2. Show up even when you don’t feel like it. 3. Make progress every day, even if it’s small. 4. And most importantly, don’t break the chain. Here’s to a productive Q4.

4 weeks ago, I started building Fastpay, a fintech mobile app, in public. I’ve worked on fintech applications for companies before, so the idea of building another fintech app wasn’t because I wanted to learn what a wallet, card, or transfer flow looks like. I wanted something I could put in my portfolio that actually shows how I approach building a complete fintech product, from the mobile interface to the backend systems behind it. So I started Fastpay from scratch. The first few days were mostly about getting the foundation right: setting up the Flutter application, authentication, OTP verification, PIN sign-in, and the Go + Gin + PostgreSQL backend. Then the project started becoming much more interesting. I began building the actual financial flows one by one, though I focused on internal wallet infrastructure and mocked external payments: sending and requesting money, deposits, QR payments, cards, transactions, currency exchange, IBAN and SWIFT transfers, phone top-ups, and scheduled transfers. And with every feature, I had to think beyond the screen. How should the API handle the transaction? What happens if a request is sent twice? What data should the backend store? How should the mobile app respond to different states? How should authentication and authorization be handled? At the same time, I paid a lot of attention to the UX. I wanted Fastpay to feel better to use, not just function correctly. I spent time simplifying flows, reducing unnecessary steps, improving how information is presented, and making different parts of the app feel consistent. That has probably been one of the most valuable parts of building Fastpay: taking the fintech patterns I’ve already experienced and rethinking how I would design and build them myself. I’ve also built the less visible parts of the product: analytics, notifications, security and privacy settings, device and session history, personal details, notification preferences, language settings and other account management flows. I’ve been sharing the process almost every day for the last 4 weeks, documenting how the product has evolved feature by feature. Fastpay is still a portfolio project, and I’m not building it with the intention of launching it as a fintech company. I’m building it to push my engineering skills, experiment with different approaches, and have a project that represents the kind of software I’m capable of building, both technically and from a UX perspective. I’m wrapping up the Fastpay build this week, and I’m looking forward to sharing the final result and everything that went into building it. I’m Ahiakwo John, a fullstack web and mobile app developer with over 4 years of experience, passionate about using technology and AI to build useful products. I’m open to collaboration and opportunities.

100 days of code to go 🥳 Consistency.