Tuesday, August 23, 2016

how to build good student behaviors


atRifF

you want to be a good student. to be a good student you have to do something that's good. these are student behaviors.

let's translate this into program rhetoric. now, you understand the idea of a program. there are good and bad programs.

a good program solves a problem, improves functionality, enhances self-defense. 
a bad program makes things worse by adding unnecessary problems to existing problems.

your life is a program.

we all come "already programmed," what people call "baggage": DNA, behavioral dispositions, psychosomatic products and byproducts (parents, neighborhood, school peers, associations, physico-biological outcomes of previous dispositions and interactions with the environment, etc).

you get the picture.

imagine each moment of your life as "inputs" of your overall life "program" being automatically realized into all the different social tasks you are engaged into as "subprograms" for instance, being a student, a worker, a father, a friend, a brother, etc.

let's talk now about bad programs. they:

1- overwhelm the host and the system,
2- reduce functionality, and therefore, 
3- worsen security, usability, maintainability, productivity, predictability, quality, etc

do you want this? of course not.

running the best program is your most important goal. 

have you not felt some times so ridden with bad "subprograms" that your life was about to "crash"?

i have.

on the other hand, our lives necessarily run with many bad subprograms ("bad code" we come with, for example: genes, parents, social conditioning, etc.

at any moment, when one less expects it, a bug appears, making our overall life program miserable. this is a design problem we all come with. don't panic.

we need to LEARN HOW TO FIX OURSELVES. how?

constantly debugging and testing our overall functionality. 

grade wise: moving from a C to a B

it means better functionality. it means better student behaviors and overall self-sufficiency. remember we don't have a programmer debugging our programs, we have to do it ourselves!

let's talk about a "good student" program.

this is the best program you can build for yourself. but you need patience and follow instructions.

let's translate this into class/behaviors for our PHI 2010 class:

1- punctuality, (in program: 9am means 8:50 am),
2- attendance, (in program: zero absences as goal),
3- hard work: homeworks and assignments, (in program: understanding homeworks, turning assignments on time, etc), 
4- participation (in program: being publicly proactive with your knowledge), 
5- leadership, (in program: helping not only yourself, but also your classmates succeed ), 
6- productivity (in program: studying conscientiously for your tests to achieve A's and B's).  
7- sustainability, (learn to detect your own "bug" on time and seek help). 

a "good student" subprogram can only help your "life program." isn't is obvious?

No comments: