How does algebra apply to computer programming

I can see college level algebra skills being very applicable to the mobile application development field. Being able to look at different problems and actually seeing equations is a good beginner level skill for computer programmers. By being able to translate actual problems into math, solving those problems becomes more possible.

It is important to note that some beginning computer programmers can look at some entry level computer programming code and see algebraic equations. This is a common misconception. Sadly this can have a potential negative impact on potential future computer programmers.

While some terms can have similar meanings, like laws, functions, and systems, a solid understanding of some programming terminology can assist with any confusion. A good discussion on the definition of variables, how assignment works, and defining programming and programs can go a long way.

I can’t see becoming a successful computer programmer as a reality for myself without an understanding of algebra. Algebra is about being able to utilize mathematical and scientific principles to recognize patterns and then utilizing those patterns to solve problems.  

Flowcharts or Pseudocode

Each student individually would need to decide whether flowcharts or pseudo code as a technique for learning programming is better. Each student will find different pros and cons to either tool. As to whether or not a tool is better, that is a matter of opinion.

Initially, I would think that I would be more successful learning using pseudo code. However, I know from past experience doing network and systems design that drawing an idea out is a very good place for me to start. I could also see using a combination of the two techniques for optimal learning.

A typical advantage that pseudo code has is that it is closer to the finished product. There are no rules to writing pseudo code, so we are free to write the code as needed. Flowcharts are capable of showing both a very detail oriented view, as well as a very high level overview of processes at just a glance.

Event driven programs versus procedural programs

The differences in development procedures for event-driven programs differ from an event-driven program. The primary reason for these differences is that event-driven programs run differently than procedural programs. Procedural programs execute by proceeding logically through the program’s code, line by line. The statements in an event-driven program are only executed when a defined event occurs and that event calls a section of the program’s code assigned to the event.

Event-driven programming is defined as: “programming where the primary activity is reaction to receipt of semantically significant signals (aka ‘events’).” The primary activity of Procedural Programming is “planning and actuation towards a goal”.

Event-driven programs might be Object-Oriented, but they may not be Object-Oriented, this is not a requirement. Event-driven programming is very well suited to GUI programming. The development of these programs would need to be different, since one program is more reactionary than logical. Of course, when all is said and done, everyone has their own way of developing programs.