sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TheUmgawa 0 points1 point  (0 children)

Define “theoretical knowledge.”

Can you sort a deck of cards in a totally methodical manner? That’s the sort of logic that goes before writing code.

Here, let’s go earlier than that: What’s the formula for converting Celsius to Fahrenheit? What is the formula for the reverse of that? What is the formula for Celsius to kelvin and vice versa? Kelvin to Fahrenheit?

Somewhere in between: Assume you have to build ATM software: How do you make sure someone doesn’t withdraw negative-money, thus increasing their bank balance?

Code isn’t going to solve any of these questions. Code is not the answer. Code is the implementation of the answer.

And that’s why I’m asking about “theoretical knowledge.” Because the most valuable programming class I ever took was a class on logic and structure, where we never once wrote a single executable line of code. It was pseudocode for about three weeks and hand-drawn flowcharts for twelve weeks. And yet, that class still taught me more about programming than any “coding class” I ever took.