Week 15 of #100DaysOfCode: 100 Days of Learning, Building, and Becoming a Better Engineer
Introduction About 100 days ago, I reached out to my mentor because I was confused about my career and wasn't really sure what direction I was heading in. I was already learning software engineering, building projects, applying for opportunities, and trying to figure out how to move forward. But I felt like I was doing all of that quietly, and I wasn't sure if anyone was even seeing the work I…
Week 15 of the #100DaysOfCode challenge has seen Onatade Abdulmajeed Adeyincka, a software engineer from Nigeria, reach a significant milestone. His journey began as a quest for direction, but it evolved into a commitment to share his learning experiences and build a presence in the tech community. The initial months were challenging, with low engagement on his posts and struggles with coding and debugging.
However, his perseverance paid off as he completed a portfolio website using Next.js, Tailwind CSS, and Motion. This project served as a comprehensive showcase of his skills and journey, consolidating his various GitHub projects into a single platform. Simultaneously, Onatade delved into the technical aspects of Continuous Delivery (CD), learning about automated deployment pipelines, Continuous Integration (CI), Automated Acceptance Testing, and Configuration Management.
He recognized that CD is not just about faster deployments but also about creating a more consistent, reliable, and manual-free process. While facing technical setbacks, such as a broken phone screen, Onatade persevered, borrowing money to repair his device so he could continue posting updates. Most importantly, he credits his mentor for his continued motivation during these tough times.
The 100-day challenge was not merely about coding daily but about maintaining momentum despite uncertainty and finding solace in the support of his mentor. Looking back, Onatade acknowledges that the true value of the #100DaysOfCode challenge lies in the resilience built through the process.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
