How to think like a programmer

There are two standard methods of program design: the top-down approach and the bottom-up approach. Top-down programming involves writing code that calls functions you haven't defined and working through the general algorithm before writing the functions that do the processing. Top-down programming is, to a good degree, a very abstract way of writing code because it starts out by using functions you haven't designed, and that you perhaps do not know how to design. The bottom-up approach to programming is the opposite: the programmer writes the basic functions she realizes will be necessary at some point in the programming and then work up to the more complex parts of the program.

Are you good in the lame-doh-calc-ya-ass?

Lame doe, calc your ass.

she
Haha, no.

top down = stactic/compiled languages
bottom up = dynamic/interpreted languages

OP is either a girl in which case congratulations on learning to read and use a computer OR is using she as a way to subvert the patriarchy is which case he is a faggot

>>5
Yes, interpreted languages like Scheme and Python are notorious for having weaker mechanisms of abstraction than compiled languages like C. ( ´ω`)

TOP DOWN, BOTTOM UP, THAT'S THE WAY WE LIKE TO develop software

I think the top-down approach can get very messy.

Plus you can't test shit as you go along.

BOTTOM UP - looks messy and is taxing on systems, however can be very legible and removes a lot of needless decleration

Top down - neat but overly wordy

What's the matter?  Cant learn to program like a woman?

>>11
what a waste of air and doubles

bampu pantsu