Most YouTubers show you a single path into AI work: start an automation agency → take clients → sell automations. It works. I know because I built an AI automation agency and sold it. But it's not the only way in, and for a lot of you it's not even the best one. I made this video to break down the two real paths: The AI Career Opportunity Nobody is Talking About in 2026 Here's the quick version: Path A is the agency play. You go independent, take clients, build your own practice. Path B is the employment play. You become the most AI-fluent person in the room, and that's who companies want to hire or promote for AI work. If you're already employed, you become the obvious pick when an AI role opens. If you're looking to get hired, or move somewhere better, you walk in with real work instead of just claims. It's the less obvious path, but it's actually the more common one. The employment numbers (see the video) are shocking actually. Watch the full breakdown in the video. Then do one thing for me in the comments because I'm super curious: Tell me which path you are on. A, B, or both. And one line or so on why. I'll be reading these. Nate

Day 1 of my AIS Challenge: building a newsletter as the first step toward a larger project I want to develop. The project integrates multiple APIs to create a market analysis bot that delivers relevant news and insights around a predefined and tested trading strategy (Pre-Catalyst Sonar). One of the key lessons I learned today is how important token usage is when working with Claude Code. Managing tokens efficiently can have a significant impact on performance and cost. Looking ahead, I'd like to expand the bot's capabilities so it can adapt to different trading strategies by adding specialized skills and continuously updating its trading-related knowledge.

Let's get to know each other! Comment below sharing where you are in the world, a career goal you have, and something you like to do for fun. 😊

Subagents are one of the most powerful features in Claude Code, and most people barely scratch the surface. In this video I break down exactly what a subagent is, how it keeps your main context clean, when you actually need one versus when you don't, and how to build your own custom agents that get invoked automatically. By the end you'll know how to delegate work to a team of cheap specialist agents while one smart model runs the show, saving you money and getting better results.

Just submitted my capstone. I built an executive assistant in Claude Code, and its first skill is a morning planning brief. I ask for it, and it pulls my real Outlook calendar and inbox, then combines them with my priorities and deadlines into a short, skimmable brief: focus for the day, deadline countdowns, schedule, emails that need a reply, what to push. Next up: Giving it more skills and letting it grow. I will challenge myself to try using it for everything.