The latest articles on DEV Community by Termuze (@termuze). https://dev.to/termuze https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1833351%2F0497eb6c-b710-4948-b076-7e6c8b561c64.png https://dev.to/termuze en Termuze Thu, 01 Jan 2026 06:14:49 +0000 https://dev.to/termuze/the-150-day-challenge-building-4-full-stack-apps-from-scratch-53a8 https://dev.to/termuze/the-150-day-challenge-building-4-full-stack-apps-from-scratch-53a8 <h1> The 150-Day Challenge: Building 4 Full-Stack Apps from Scratch </h1> <p>Today is <strong>Day 1</strong>.</p> <p>I’ve spent enough time reading documentation and watching others build. It’s time to stop "preparing" and start shipping. I am officially committing to a 150-day marathon where I will build and deploy <strong>four full-stack applications</strong> from the ground up.</p> <p>No more tutorial hell. No more half-finished repositories. Just code, and live URLs.</p> <h2> Why 150 Days? </h2> <p>Consistency is the hardest part of software development. By setting a hard deadline of 150 days (roughly 5 months), I am giving myself enough time to go deep into complex features while maintaining the healthy pressure needed to keep moving.</p> <p><strong>The Rule:</strong> I have exactly <strong>30 days</strong> to take each project from <code>git init</code> to a live, production-ready deployment.</p> <p>My goals for this challenge are simple:</p> <ol> <li> <strong>Master Multiple Ecosystems:</strong> Prove I can build with different paradigms and languages.</li> <li> <strong>Build a Real Portfolio:</strong> End this journey with four high-quality, functional apps.</li> <li> <strong>Public Accountability:</strong> Documenting this here on Dev.to ensures I stay on track.</li> </ol> <h2> The Tech stack </h2> <p>To maximize my learning, I won’t be sticking to just one stack. Over the next 150 days, I’ll be rotating through:</p> <ul> <li> <strong>MERN Stack</strong> (MongoDB, Express, React, Node.js)</li> <li><strong>Vue.js</strong></li> <li> <strong>Django</strong> (Python)</li> <li> <strong>Laravel</strong> (PHP)</li> </ul> <h2> Project #1: DevLift </h2> <p>I’ve already decided on the first step of this journey. Project #1 is <strong>DevLift</strong>.</p> <p><strong>DevLift</strong> is a platform built to help developer projects gain the visibility they deserve. It allows developers to submit their work, track real-time engagement, and reach a wider audience through a curated discovery system. </p> <p>The goal is to move away from the "void" of empty GitHub stars and actually help great tools find their users.</p> <ul> <li> <strong>GitHub Repo:</strong> <a href="https://github.com/termuze0/DevLift" rel="noopener noreferrer">termuze0/DevLift</a> </li> <li> <strong>Current Stack:</strong> MERN (MongoDB, Express, React, Node)</li> <li> <strong>Deadline:</strong> Day 30</li> </ul> <p>The clock starts now. I’m diving straight into the architecture.</p> <h2> Help Me Choose Project #2 </h2> <p>While DevLift is currently under construction, the rest of my calendar is open. I want Project #2 to be a challenge that pushes me into a completely different environment—using either <strong>Vue, Django, or Laravel</strong>.</p> <p><strong>I have a question for the community:</strong><br> Since I’m working with these four stacks, what should I build for <strong>Project #2</strong>? </p> <p>If you have a great idea—whether it's a SaaS MVP, a real-time collaboration tool, or a data-heavy dashboard—drop it in the comments. I’ll be picking the most interesting suggestion to start on Day 31!</p> <p>Let’s get to work. </p> buildinpublic devjournal sideprojects showdev