CodeWithChris

Hey it's Chris here! Just want to say that I'm working on the next lesson for the 8 day beginner series (Lesson 6) with a target release date of this Friday. Sorry for the delay. We'll get back to regular scheduling!

1 day ago | [YT] | 10

CodeWithChris

What to expect when you join CWC+?

You won’t just learn how to code. You’ll learn how to think like a developer.

Because when AI coding tools fall short, real-world skills and foundations will be the ones that’ll keep you moving.

Now’s the best time to ramp up your foundations with our Black Friday Sale!

Get $130 off your annual CWC+ membership.

Offer ends soon. Click the link below to join the future of iOS dev.

cwc.to/bf2025

Skip the Carousel

1 2 3 4

1 day ago | [YT] | 10

CodeWithChris

Hey folks!

The early bird period for our Black Friday sale will end in 3 hours.

This means that this is your last chance to join CWC+ at our lowest price of the year.

Join CWC+ before 11:59 PM EST tonight and get $149 OFF!

cwc.to/bf2025

4 days ago | [YT] | 6

CodeWithChris

Hot take: Vibe coding isn't the problem—how you use it is.

(For those wondering: "vibe coding" = using AI to generate your entire app with minimal human oversight)

Recently I've been seeing more news about vibe coded apps mishandling sensitive information, being prone to security issues, and being a nightmare to maintain.

It seems like people are waking up to the fact that human software engineers are still needed lol

But does this mean you shouldn't vibe code your app?

Not at all. There's still a perfect use case: prototyping.

Here's the strategy:

Simplify your app idea to minimize the risk of bad code while still allowing you to test your idea in the market.

Vibe coding saves you massive amounts of time that you can redirect to distribution and validation.

Just know the trade-off: You might have to rewrite it from scratch later.

In conclusion… vibe coding isn't bad. Just understand the limitations of the tool you're working with and use it strategically.

What's been your experience with AI-coded apps? Drop your thoughts below 👇

3 weeks ago | [YT] | 22

CodeWithChris

OpenAI's new Agent Builder just launched and it allows you to visually build workflows for your AI agents to perform.

It's made even more powerful if given access to to use more tools via MCP.

Guess what, I just released a intro video to Zapier MCP :)
https://youtu.be/8_zse1sy80I

1 month ago | [YT] | 11

CodeWithChris

Resharing the story of Michael, who tried learning to code for YEARS but kept giving up!

When COVID hit, he found CodeWithChris, and everything changed 🔄

The struggle was real:

Multiple false starts with coding. Toured with live shows. Hit major roadblocks with API calls. Almost quit (again!)

The breakthrough happened when:

- He found CWC's hands-on approach
- Used AI as a debugging assistant
- Built and published TWO apps

Today, Life Tracker and Butterfly AI Stories are live in the App Store, and he's learning Android development!
The right learning approach and persistence really made the difference.

Read his full journey here: codewithchris.com/success-story-michael-olson/

2 months ago (edited) | [YT] | 39

CodeWithChris

Last week, I showed you how to use source control with GitHub so you never lose your work.

But what if you want to experiment with new code without risking your main project?

That’s where branches come in 👇

—

When you create your repo, by default, you have a single branch: the main branch.

But you can create more!

A new branch is just a copy of your project where you can safely test new ideas.

You can name it after the feature you’re building — like feature-xyz.

—

When you create a branch, you can copy your project from the latest state or even from an older snapshot.

Then you switch your workspace to that branch and experiment freely.

Your main project stays untouched.

—

On your feature branch, you can keep making commits just like normal.

It works the same way as your main branch, but separate.

That’s what makes branches so powerful.

—

Once you’re happy with your changes, you merge your feature branch back into main.

After merging, you can delete the branch or keep it around.

That’s the full workflow.

—

Sometimes you’ll run into merge conflicts if both branches change the same code.

Don’t worry — you just open it in a text editor and decide which version (or both) to keep.

That’s how you resolve conflicts.

—

The big takeaways:

- Branches let you experiment safely.
- Your main project stays stable.
- You only merge the good stuff back in.

This is how professionals (and big teams) work — but it’s just as useful for solo devs.

—

If you want to see a step by step demonstration of this, check out my latest YouTube tutorial!

https://youtu.be/0vzYWyHmcY8

2 months ago | [YT] | 37

CodeWithChris

Xcode 26 is available to download from the Mac App Store!

2 months ago | [YT] | 86

CodeWithChris

Just sharing some recent testimonials for CWC. Happy to see results and progress from our students ❤️

If you're looking to master the fundamentals of iOS app development, check out our CWC+ program!

codewithchris.com/plus

Skip the Carousel

1 2 3 4 5

2 months ago (edited) | [YT] | 19

CodeWithChris

Here are some highlights from my new GitHub tutorial (beginner friendly!) on YT.

I think this is especially relevant in this vibe coding era bc I encounter many people who constantly have to restart their project from scratch.

It doesn't have to be that way!
--
Ever wish your project had a giant undo button?

That’s what source control is. And the best part: you can use it even if you’ve never coded before.

--
Picture this:
- AI breaks your project
- Undo doesn’t work
- Multiple copies scattered across folders (if you even have that..)

Source control is the answer.

--
Source control = snapshots of your project you can roll back to anytime.

Think of it as a time machine for your files.

--
The vault where your project lives is called a "repository" (or repo).

Inside it, you save snapshots (commits).

And you can always restore an old snapshot if things go sideways.

--
GitHub is the online vault.

It’s free, easy to set up, and it keeps your projects:

- Backed up
- Synced across computers
- Ready for collaboration

--
Getting started is simple:

1. Create a free GitHub account
2. Download GitHub Desktop
3. Sign in and create your first repo

--
From there, you can:

- Save commits as you go
- Publish your repo to GitHub for cloud backup
- Revert to older versions when needed

--
You can even create "branches."

Branches are safe copies of your project where you can try new ideas without breaking your main version.

--
If you use source control, you’ll never have to start a project over from scratch again.

Want to see how it works step by step?
Check out my full GitHub tutorial that I just released:
https://youtu.be/v5gnvDUWqFM

2 months ago | [YT] | 20