Corey Knowles

You're going slowly.

Maybe you sometimes vibe code something, but often you don't expect to just merge the vibe coded thing if it's a hard, complicated task.

I expect it to merge.

When I wrote that prompt, I'm like, this is for sure going to work.

Right.

But the more complex the task is, then the more you're not expecting to just like merge a live code of thing.

You're expecting to like use that to massively accelerate yourself.

But you're still going to be involved to make sure that like architecturally it sounds so you don't get stuck.

Yeah.

I mean, the question is like, yeah, how much knowledge do you need about programming?

I mean, this is a common question.

It's like, is it worth learning software engineering and computer science?

And I definitely think it is worth learning computer science still.

And I still think if you want to build something like really meaningful, then you still want to understand like the underlying systems that you're going to be working with.

And you still want to be an expert.

The difference is that you just are a massively accelerated expert.

You know, or as I think,

you know, I don't think we're going to reach the point where it's, I don't think we even want to reach the point where, you know, there's no point in learning computer science anymore because learning computer science is fun.

It's just like learning computer science was like, let's say like, let's go back like five years.

Like what learning computer science was five years ago is different than what it was 20 years ago.