I Put My Laravel Course on Hold to Build THIS - Meet CodeArch

Hey everyone, Gio here. I know it's been quiet on this channel for a while. No new uploads, no new learnable the right way episodes and not much of an activity on Twitter or X either. So today I want to catch you up on what I've been doing, introduce my new project called Code Arc and talk about where this channel is heading next. So grab a drink and stick around for a few minutes if you can. Short version, limited time, too many ideas, and a giant AI wave hitting all of us. Between family and a full-time job, I only get some evenings and some weekends for this. So, I had to choose between recording videos or hacking on some side projects. I decided to work on a project called Code Arc. Was it the right choice? Maybe, maybe not. But I had a lot of fun building it and also learned a few new things along the way. Think of Code Arc as a gamified Trello for dev side projects. It isn't a full-blown project manager or Tudo app, and it's not one of those type an idea and let AI do everything type of project either. We have plenty of those around already. Codeark is all about curated projects that are broken down into bite-sized tasks. Kind of like having a mix of tech lead and product owner in one. In addition to some of the projects being curated by me and broken down into tasks, you can also create your own projects or use AI to generate a project from your idea and have codec break it down for you into tasks. Now, picture working at a company that uses scrum. Stories show up in the backlog, each with a clear acceptance criteria. Your job as the developer is to review those tasks and build them. Codeark essentially gives you that kind of structure for side projects. It gives you that guidance, gives you those tasks that you can follow and slowly chip away at it while staying motivated because of the gamified elements. You earn XP as you complete tasks. You earn skill points depending on different uh task types. And yes, there are different task types on Codark. We have research type tasks where you would have to go and research the topic or the concept. We have implementation type where you would actually be writing code or implementing something. We have deployment type, testing, QA, review and so on. There are three main problems that I see with side projects. First is overwhelm and analysis paralysis. We often start with enthusiasm, ready to build the next big thing, but get lost in the endless possibilities leading to overthinking and inaction. Second is unclear direction. Without a clear road map, we often end up going in circles unsure what to build next or how components should connect. And finally, motivation fades. The initial excitement wears off and without clear milestones or rewards, we eventually abandon the project. Codark attempts to tackle those problems by giving you a road map and gamification elements to keep you motivated like XP points, skill points, stamina caps so you don't burn out, and a community helpline when you're stuck. Now, what does all of this mean for this channel? Videos are coming back. Instead of huge theoryheavy playlists, I'm going to be doing and focusing more on projectbased builds that plug straight into code. You'll see me create project plan inside code. Then we'll code it together on screen. If you get stuck, you can open the same task on code, ask for help, and keep going. Now, what does this mean for the learn laravel the right way series? Short version, the series didn't land the way I hoped. Tons of prep, work, deep dives into the source code, and not much of an interest around for it in the community. This was a bit demotivating to keep working on it hard because I really was spending a lot of time prepping and recording each video. It was part why I chose to work on a side project rather than continue on videos that were only getting a few hundred views at the time. Maybe it was too long. Maybe it was too detailed. Or maybe it was just plain boring. Who knows? So, I'm parking that course for now. Not killing it forever. Just hitting a pause. I believe project-driven Laro content will be more fun and useful. So, that's what I'm shifting to and also want to try some other ideas and not be held by a commitment to a huge playlist. It's all an experiment. Will it work? Maybe, maybe not. I don't know. But I think the message is clear that some kind of change was needed. All right, so this is it. Just wanted to give you a quick update. Check out codearch.app when you have some time. Sign in with your GitHub account, spin up the project, or enroll in one of the existing ones and let me know what you think. Drop your feature ideas or feedback in the comments below or join our Discord and drop it there. Thanks for sticking around while I've been heads down. really hope to make it up by sharing some new projects and videos this