Pffft. If you only start debugging after so many lines, you’re asking for it. Always test small parts as much as possible.

Feeld mild today are we? I would give him five, but only if I could resist throwing him out myself.

Much like the classic.

“Boss, I damaged the mirror of the car and now I can’t make it in time.”

“Why not? It’s just a mirror.”

“The rest of the car is on top of it.”

I understand why you ask this question, but really the fastest way to learn is to decide what you want the computer to do and start looking for that.

One thing will lead to another and you’ll learn lots of things that way, while you’re immediately using it.

Tutorials and courses can work, but usually it works best if you use whatever you are learning.

So come up with an idea for a program, and start building. There will be mistakes, anger, frustration and cursing involved, but you will learn a lot.

First at the lower level, and later on you will probably start wondering how to structure it all. And then you’ll learn about that too.

My point? Just dive in, fall on your face a couple of times and you’ll learn a lot in a short time.

I knew this one, but I enjoy it everytime. Because it’s true, we add way too much stuff we don’t need, and that page loads instantly and gets the point across. It’s perfect.

Isn’t that what most printers do anyway? They have one job and they fail at that?

I hate printers :(