owenSoft.net - Articles

Hardwiring: programming the design (tech) (Articles)

2008-03-24 20:22:45

There is a tendancy to write your use case directly into the low level design of the code. This pattern should be avoided as much as possible because it results in extensive "recoding" whenever high level design changes are made to the program. The highlevel design is not caved in stone and will most likely change as the system evolves but its core design rearly changes. It is important for the programmer to identify this core design.

For example an extreme case can be seen when the previous programmers wrote a screen for the 10 department types that are in the system - assuming that there would only be 10. As you can see hardcoding or hardwiring your use case rules into your code is not a good thing. The programmer wrote the code on the "business logic" instead of the "system layer".

It is important to notice that there is a system below the business logic. This system is what keeps the application simple and stable. The programer should seek to find the best way to rewrite the highlevel business logic into a stable sub system.

Take for instance the previous example: you can imagine that the programer got a use-case with 5 rows and 2 column of 10 items. The programmer looked at the first line of the use case and started coding right away (and in truth and in fact probably coded it in half the time that I would take to code it). The end result will work and will have the same output but the difference between the 2 approachs to the problem is night and day. Further down in the project the need MAY arise to add a new type of department. You should notice that the business logic in the use cases DOES NOT BREAK but the code that was written to implement the use case fails and the blame goes on the programmer even though the programmer did what the use case said should be done.

Another example: bank type. You notice that the use cases specify particular actions that occur on certain types of banks. And these types of banks are hard coded into the system. Business logic constants are bad design. This implementation is done like so:

BANK_TYPE1 = 1

SELECT * FROM BANKS, BANK_TYPE WHERE BANK.TYPE_ID = BANK_TYPE.ID AND TYPE =

IF BANK.TYPE == BANK_TYPE1 THEN

DO BUSNIESS LOGIC

END IF

The shortfall of this type of programming is the SAME as the 10 item example above. If for instance a new bank type is added that implements the same business logic as that of BANK_TYPE1 then the code will have to be CAREFULLY altered to facilitate the change to the design. Here is the new code:

BANK_TYPE1 = 1

BANK_TYPE_TWO = 3

SELECT * FROM BANKS, BANK_TYPE WHERE BANK.TYPE_ID = BANK_TYPE.ID AND TYPE = or TYPE =

IF BANK.TYPE == BANK_TYPE1 THEN

RETURN (BANK_TYPE1) BUSNIESS_LOGIC1()

END IF

IF BANK.TYPE == BANK_TYPE_TWO THEN

RETURN (BANK_TYPE_TWO) BUSNIESS_LOGIC1()

END IF

In the best case senario the same programmer will be able to remember how the program works and change all the places that need to be changed to fix the problem.

The solution to this problem requires a system level design change that will protect the code (the programmer) from changes/enhancements to the design. There are many ways that this can be done and the best way often takes more time and therefore the benefits of such an change must be evaluated during development by the programmer.

---

The point here is that it that the use cases are not low level designs. The progammer should ( whenever possible ) try to abstract the effects that changes have on the code which is written, by writing it in a way such that it is flexible enough to absorb business logic/design changes that may occur in the future.

By owen on Articles

How to tell if you are an IT person (Articles)

2007-11-25 19:47:55

Mesha this is for you. I will try to keep this simple and to the point because some of us like to argue and some of us don't. I will start out by listing the qualifications that either by themselves or combined will result is a person who can call themselves a techie or an IT person. This article is written because I've realized that now in Jamaica since it seems that people have started to call themselves "IT persons" without fully clearing the bits or understanding what it actually means. By IT I mean "Information Technology" or Computer Science or whatever related field you choose. So here now I start with a list.

You are and IT person IF;

You like lists.

You like to play games for long hours, develop habits easily and have at some point in your life completed a mario brothers game. Though not necessarily beat the game but have tried on multiple occasions. This is however not limited to video games but anything involving a winner and a loser such as card games and games of luck or skill. You should be able to play many games at least 3 - not just one that somebody taught you. And be up for playing ANYTHING that looks like a game that you can win. Games can include mind games, board games, random text messaging. Solitaire is not a game.

IT people like to solve problems and hate doing the same thing twice. If an activity doesn't solve some kinda problem that will save somebody "work", time or money then more than likely you are a "packer". If you've done it before and are still doing it without improvement then you can't see the rabbit.

If you are disgusted by the behaviour of IT people and think that they are lazy, selfish and inconsiderate then you are most definitely not an IT person.

Having an IT degree or qualification or working with computers or teaching does not automatically give you the right to call yourself and IT person. You merely "associate" with IT people but you haven't crossed that line where you start avoiding people and not returning calls.

Working at an IT company doesn't not make you and IT person.

If you ever reach to a state where your too busy to brainstorm a solution to a problem or have a concept in your head that is called "work" such as can be compared to farming, manual labour or mining coal - then more than likely you are in it for the money are not an IT person but rather a slave to the money. Go and follow your dreams. No matter how far down the wrong road you've travelled - its never too late to turn back.

IT people do not like to use powerpoint or write lengthy essays. If you like to write multipage essays then chances are you are not an IT person.

Most IT people that I know like what they do, it might not seem that way but its true. On the other hand if you would rather be flying around the world, teaching kindergarden, or staring in a rock band then chances are you are not an IT person.

If your monitor is set to 800x600 then I really don't know what world your living in.

If you are confused or fail to see why I would list these things are behavioral patterns of IT people then chances are you cannot relate and are NOT AN IT PERSON.

This list that I have compiled more than likely is not complete and millions of ways could be found to argue around it. Whether depending on whether you are a woman or a man or your from the country or whatever - it doesn't really matter because most people either are who they say they are or are pretending to be a doctor. To each his own.

By owen on Articles

Quick: How to setup and run php-apache on win2k sp4 (Articles)

2007-07-01 15:17:15

Friday, May 18, 2007, 7:15:29 PM

"for people who have installed something before"

goto (link)

download the last "PHP x.x.x installer" it should be about 22 mb by now. Php has 2 streams; a 4.x stream and a 5.x stream. Check which version your web host will give you access to. If your only going to play with it on your machine then just go for the lastest version. But remember that if you start using features of 5 you might have a little difficulty running it on 4.

Downloading the Apache HTTP Server

Go to (link) and download the "HTTP Server". Which also has 2 streams but the instructions above still apply.

Start installing

Install the Http Server

Install Php

Run the php Installer. It might ask you to setup a server for ex appache and select the folder which contains the configuration files ( C:Program FilesApache Software FoundationApache2.2htdocs )

Do not enable all the php modules, pick the ones that you know you want because sometimes the modules have external requirements that may prevent you from starting,

Got to Start//Programs//Apache and then search the option to restart your http server.

Installation Done

Goto

C:Program Files/Apache Software Foundation/Apache2.2/htdocs

create a text file

call it "p.php"

Edit it with a text editor (preferable editplus from (link) )

add this code to the file;

phpinfo();

save the file.

OPen you browser and goto;

(link)

You should see a long purple table with the php logo. Your good to go. Setup was successful. That directory is now your webserver, so can only run php programs from the for now.

More stuff to do

(link)

►Another problem is that people many times use OLD PHP script that uses 'short tags'. That is when the PHP declarative starts with

Other

You might also want to install a database such as Mysql

If you run the Mysql 5 install do not enable "strict mode". Its really really really strict.

Might also want to get phpmyadmin

By owen on Articles

Gene find triggers baldness hope (Articles)

2007-05-22 06:51:01

Hair loss in humans might be reversible, suggest scientists who have helped create new hair cells on the skin of mice.

It was thought hair follicles, once damaged, could never be replaced.

But a University of Pennsylvania, US, team, writing in the journal Nature, says hair growth can actually be encouraged using a single gene.

By mad bull on Articles

The System Layer (Tech) (Articles)

2007-04-23 21:34:18

In this day and age of highly complex business applications, which encompass a wide array of solutions to real world problems, it is essential to note the importance of application logic. Application logic or The System Layer is the track on which the business logic of any system must be built so that it travels at a constant, steady and predictable pace. Applications built on business logic are roll-a-coasters of terror. It is often easy for a software developer to take the "customer is always right" approach to programming software. And in so doing build applications that are based entirely on the business logic of the client. This is a common pitfall which although creates wonderful entity relationship diagrams requires an extensive knowledge of the client business logic to maintain, upgrade and optimize. You end up in a situation where the application becomes a exquisite dish that must be prepared by a Tibetan monk.

In a client environment where business logic is often mapped to physical tasks that can range from a very simple process to a complex maze of activities, sustainable applications need to be built on a simple, predictable backbone aka a System Layer. The system layer is akin to how a computer works with 1s and 0s or in genetics with DNA. If you want to build an application you are essentially putting together some 1s and 0s. You use 1s and 0s because its a standard, easy to use and relatively simple setup that the computer and other people already understand. 1s and 0s are a part of what I refer to as "the system layer" - the basic rules on which software is built. The system layer aims to provide a layer of simplicity to an otherwise complex application. Keep the application simple at its base and complex in specific branches.

Maybe I am being a bit extreme when I chose to use 1s and 0s as an example. Say for instance a file in an operating system. A file at its basic level has no business logic - it can be anything at anytime and the operating system would not careless. This "carefree" attitude is why operating systems are the most widely used type of software. In operating systems "business logic" is often implemented at the GUI level. The act of forcing users to create files that consist of names and extensions is enforced In the "file-browser" but never are the core level. Operating systems provide a system layer in which your application can operate efficiently - you are a "client" of the operating system. The operating system can maintain its efficiency by maintaining a stable System Layer. Building an application on business logic is like building the whole operating system again, but your files are not just files - they are whatever the business logic dictates. This creates a situation in which a rabbit is never really a rabbit unless you know that it is a rabbit. And in most cases the people who "know" and the people who "want to know" aren't the same people - in said scenario a rabbit might swim or fly depending on a status, type table, or season.

Application Logic or A System Layer aims to improve stability, predictability, extensibility and maintainability of software application by creating a simple set of fundamental rules upon which business logic is implemented. All Files have a name, meta data and content. RABBITS DONOT FLY UNLESS TOLD TO FLY. Developing a system layer does require research and thought; you must be willing to stick with it FOREVER, through thick and thin, rain or storm. Bypassing the system layer even a little would be blasphemous. Unless such a time a rises that a piece of business logic should totally destroy your tracks. Well built tracks last forever, roads develop potholes. Keep it simple, open and efficient at its base and finding problems will be easier, isolated and less magical in other areas of the system.

By owen on Articles

The Sweetest Taboo (Explanation of blog post) (Articles)

2007-01-14 21:06:00

This is a sorta explaination of the post "The Sweetest taboo" since people didn't really get it. You should read that first before venturing off into this. Most of my posts - well all have 3 paragraphs which often times do not interact. Avoid trying to make sense of it as a whole. Sometimes I will make the effort and write a full essay but those times are rare and far between. Took a couple hours but I've managed to link every reference I could find. I'd like to thank Youtube.com, my mother and all the people who didn't annoy me. The notes are * emphased or highlighted in yellow on my site.

The explanation

The sweetest taboo *reference song The sweetest taboo by Sade Adu

*Taboo is noun meaning a social or religious custom prohibiting or restricting a particular practice or forbidding association with a particular person, place, or thing. Its also from one of my favorite artists Sade Adu. Its off an album called Promise by Sade. The "Best of Sade Album" was stolen from a roommate in New York in 2001 - I loved it so much. The album defined my entire trip. I was in the Bronx with my grandmother. Then the whole 9/11 thing happened and I came home a week later. Watched it live because the other public channels stopped working when they too out the tower.

submitted on 07th Jan 2007 to Logbook *first post of 2007

submitted by owen * I are di one

Its been sometime since we last spoke. *reference to a song called "Cupid's Chokehold" by the GymClassHeroes. In which the protagonist writes to his mother about his love life. Very good song and video.

When I was a young boy my momma said to me "There's only one girl in the world for you and she probably lives in Tahiti ". *From a song by Wreckless Eric called Whole Wide World which I found a review & mp3 from the Stranger Than Fiction - Original SoundTrack. Stranger Than Fiction is a movie I watched the week before about a Tax auditor who is hearing his life being narrated by a voice in the sky. Good movie.

Luckily, being as I am, I do not think of it much, illusions of grandeur are not entertained. Only fools rush in. *reference "Can't help falling in love" by UB40 It is hard to resist like spiked christmas sorrel. It had so much alcohol in it that it didn't even taste like sorrel. Being red was its only alibi. I poured it half full and attempted to over-power the spirits with ice water like an exorcist. *reference to year's week post Love is lame Little did it do. *Stranger Than Fiction I won't be your father figure, put your tiny hands in mine. *reference song "Father Figure" by George Michaels

* The entire second paragraph is about my taboo. Which ties into the title of the post. The title of the post usually has nothing to do with the content but this one seemed fitting.

As I look down in to her eyes and stare. In deep thought about nothing I look fixedly with my eyes wide open until she starts to giggle profusely [] *Something that is profuse is poured out or given freely, often to the point of exaggeration or excess. like a school girl at a fair. A fair that has a bounce-a-bout, merry-go-round and cotton candy. * Refers to Brooks park in Mandeville Jamaica, where I grew up as a child. You could only get cotton candy at fairs back them A confused look rolls over her face - trying to fathom my thoughts. *apparently I confuse people often At which point I break my silence and move towards her lips, thats all I wanted, its a little bit more than it seems. *reference to a song "More Than It Seems" mp3 by Citizen Cope Sad eyes turn the other way. * reference "Sad Eyes" by the Bee Gees Let me show you how much I care. *reference "The reasons Unknown" by The Killers As I watch the clock, time slowly drifts *water on, it becomes hard to concentrate. Something in the way she moves. * reference "Something" by the Beatles 1969 Sometimes I find myself lost in the glow of her shiny nose like a meteor drawn dangerously into the earth's path, emitting light as a result of being heated. As the separation anxiety *SNES video game with Venom and Spiderman begins to sink in *water, nothing is quite the same but if it makes you happy why are you so sad? *reference song "If it makes you happy" by Sheryll Crow It may take sometime to recover. This has been the worst December ever. *really Love me for who I am. *stop trying to figure me out, I'm not weird

It has been a stressful new year. Not counting the people who have been murdered so far. *25 in a week Being murdered I imagine would be more than stressfull. I was just getting accustomed to 2006 when it came to a hard, bitter and infuriating end. No Mavado watch. *christmas present mission influenced by Tash to get myself a watch from a girl for christmas by any means necessary - failed Children killing children while the students rape their teachers. We can't carry these sins on our back, we gonna swim to the ocean floor, crash to the other shore. *water *reference "Swim" by Madonna off the Ray Of light Album All we need is love * Beatles and snow * Snow falling in Jamaica would reduce the crime rate - its a theory, I pray for it nightly.

Conclusion

There you have it, took a while to compile but its done. Won't be doing that again.

By owen on Articles

The Voting Bathroom Analogy (Articles)

2006-11-09 16:13:43

Voting is like washing your hands in the bathroom, there is no "instant" benefit to it and the "I told you so" that you get is often not a direct fault of not washing you hands but is a fault of going to the bathroom. It would help if you could avoid the bathroom all-together but most people are born into the bathroom. Being born into a bathroom offers you advantages which you get because people wash their hands. Some people just like to wash their hands because it makes them feel good, others wash because they get a bad taste in their mouth when they lick their fingers and some don't wash at all and choose to live like rebels.

The existence of the bathroom is never really-actually-clearly-significantly defined to those that do not benefit from it. Worst yet only the people that benefit from the regular use of the bathroom and posses the knowledge of it can efficiently use the bathroom for social gain. So encouraging others to wash their hands is therefore crucial to these people. The more people that wash allow the bathroom operates to be in a better position to create social gain from the bathroom. Because the people who understand the bathroom the most are often the people who built it, they are ever present.

The importance of the bathroom is not understated but is known to almost half the population. The inner workings of the bathroom are important but the importance cannot be conveyed to the people who willingly or ignorantly do not was their hands. Lets say that everybody starts to wash their hands; in such a case it would be apparent that the ill effects of not washing you hands would totally disappear. If it is not possible for everybody to wash their hands and in fact doesn't matter if everybody washes their hands then the purpose of washing your hands becomes irrelevant. The proper use of the bathroom seems to be more important. Therefore, if the bathroom in used correctly then why wash your hands?

The answer to the question is multifaceted. Apparently either nobody trusts the bathroom or the bathroom is setup in such away that you have to make a choice. The choices are always limited. Limiting the choices seems to be a trend that existed since the beginning of the bathroom itself. Polar choices are setup, choices are often re-shuffled upon each entrance to the bathroom, the choices are or may appear to be different but you still wash your hands the same way. The choices are often make to seem obvious but have little to do with the actual outcome in the worst cases.

By owen on Articles

The Bleach Incident (Articles)

2006-02-09 19:41:56

NK says: hi

NK says: you there ?

owen says: sup?

NK says: I was hospitalized for 2 days... for the first time in Canada

NK says: that too... with an Ambulance pickup

NK says: yesterday, I came out of Hos...

owen says: :O

owen says: man, what happened?

NK says: I was inhaled strong and punget... smell of bleach / Javex

NK says: which I was not aware .... when I was doing some cleaning in the bathroom

NK says: unfortunately, because of winter all the doors and windows were closed...

NK says: and I fell short of breath....

owen says: oh,

NK says: had to run of the house for air.... in - 12 centigrade..., snow

NK says: for 30 - 40 min.

NK says: and finally ran into Hypothermia

NK says: next door neighbour called the ambulance

NK says: to rescue the situation

owen says: man you almost killed you self!

NK says: I guess....

NK says: yes

NK says: it was very unfortuante situation

owen says: you doing better now?

NK says: Yeah... I am

NK says: I still feel fragile...

NK says: Luckily,... I have healthcard...

owen says: you'll be back up to strength in a couple a days

NK says: and did not incur and bills

NK says: yes, you are right

NK says: that would be fair enough time , i guess

owen says: just rest

NK says: I want you to post a message on your site - saying that some smart people have to be alert all the time

NK says: no matter who they are...

NK says: Lot of intelectual do know certain circumstances...

owen says: what doesn't kill you makes you stronger

NK says: absolutely

NK says: post message and hep people by alerting.... once in a life time

NK says: i think you can do that....

NK says: a simple bleach can put us ... dangerous situation

owen says: true

By owen on Articles

How to build a heirarcy with one query (Articles)

2005-11-19 19:41:26

Generating a tree list / heirarcy without a hundred queries is a problem that I have had since way back in 2002 when I started building the forum. Running a query for every node in the tree seemed malign to all things database. Even doing it once and caching the result was not something I would consider a 'good fix'.

I discovered how to solve this problem back in August of 2004 using 'by reference' pointers. Using this method a very large tree can be generated using one query, an array, recursion, and some programming kung-fu. There is a down fall to this method however i.e. the query has to bring back all the nodes in the tree or else you will end up with missing sections. A enchanced version is implemented in the sitemap of this website.

The technique involves a table which has 3 or more columns; id, name, parent. The 'parent' column would be a reference to an id in the same table. I created the table this way because it makes for simpler queries. Firstly you run your query and get all your records from the table (downside!).

select * from sitemap

The second step is to loop through each record while placing each item into a array using the id column as the array key. The section step is to check the parent value and to add a child array to the parent node. Then whenever a node which has a parent appears a reference is added to that parent node's child node.

The following code is written in php a C like language. It should be easily portable to most other language.

$os->execsql2(" select * from sitemap ", 'CACHE');

$struct=array();

while( $row = $os->fetch_array() ) {

if( !isset( $struct[$row] ) ) {

$struct[$row]=array( 'id'=>$row, 'name'=>$row, 'parent'=>$row, 'data'=>$row );

} else {

$struct[$row]=$row;

}

if( $row != 0 ) {

if( !isset($struct[$row]) ) $struct[$row]=array('id'=>'undefined','name'=>'undefined',

'parent'=>'undefined', 'data'=>'undefined');

if( !isset($struct[$row]) )

$struct[$row] = array();

$struct[$row][$row]= &$struct[$row];

}

I could do a part 2 of this article but anyway. Print the results involves looping through nodes which have parent set to 0. Then printing the child nodes if any. You need 2 functions;

function write_select_struct( $struct, $name ) {

print('');

}

function write_option_struct($a, $path) {

print('

$path .= $a . ' » ' ;

print $path . '';

//$a

if( isset($a) ) {

foreach ( $a as $key => $value)

{ write_option_struct( $value, $path ); }

}

Finally you simple call the function;

write_select_struct( $struct, 'category_id' );

which prints out you tree in a drop down list which can be modified into a tanle list or whatever you please.

The original program was implemented in 86 lines total. Thats it. Watch your memory.

DisAdvantages

In most cases you have to load the entire list in order to biuld the tree. So very large lists are personally discouraged if you are using it in real time.

Missing Parent keys will create undefined links in the tree.

Multiple functions are annoying.

The function that initially builds the list is kinda cryptic

Advantages

Simple, quick and manageable meaning that once you understand how the code works you can use in varied situations with fewer special attacks.

By owen on Articles

Standard ASP .NET Namespaces (Articles)

2005-10-29 01:55:20

The classes contained in a select number of namespaces are available in your ASP.NET pages by default. (You must explicitly import other namespaces.) These default namespaces contain classes that you use most often in your ASp.NET applications:

System

Contains all the base data types and other useful classes such as those related to generating random numbers and working with dates and times.

System.Collections

Contains classes for working with standard collection types such as hash tables, and array lists.

System.Corrections.Specialized

Contains classes that represent specialized collections such as linked lists and string collections.

System.Configuration

Contains classes for working with configuration files (Web.config files).

System.Text

Contains classes for encoding, decoding, and manipulating the content of strings

System.Text.RegularExpressions

Contains classes for performing regular expression match and replace operations.

System .Web

Contains basic classes for working with the World Wide Web, including classes for representing browser requests and server responses.

System.Web.Caching

Contains classes used or caching classes for performing custom caching operations.

System.Web.Security

Contains classes for implementing authentication and authorization such as Forms and Passport authentication.

System.Web.SessionState

Contains classes for implementing session state.

System.Web.UI

Contains the basic classes used in building the user interface of ASP.NET pages

System.Web.UI.HTMLControls

Contains the classes for HTML controls.

System.Web.UI.WebControls

Contains the classes for Web controls.

By KMT on Articles

ASP .NET Repeater - rock star hack (Articles)

2005-09-26 18:38:45

This article assumes that you are either good at some language and new at ASP.NET. Or, you are good at ASP.NET and never written anything or whatever. Anyway I refer to this piece of that I am going to tell you about as a "hack" because I am not very good at ASP.NET and I could not get expert advice on the subject. So after weeks of mental juggling, reading useless/redundant articles and playing around with Web Matrix, I finally got the Repeater object to work.

Basically the code uses the repeater object to create an array of input fields with which I can dynamically add, update or delete rows while still using ASP.NET web controls which are tied to a 2 dimensional data-source. In other web development languages you could simply create an array of input fields but I found some issues with doing that in ASP.NET.

The Code

The first step is to create a repeater onto a blank page.

Edit the repeater code in source view and add a item tag. Within the item tag your add web controls etc that you want to be repeated. Note that the IDs of my web controls are the same as the columns of my data-source. I use the IDs when I am updating the data-source. My data-source is a "DataTable" object which is stored in a session variable but it could be a "Arraylist" or something else that is "Bindable".

Set the web controls to values from your data-source. Note that Text='value' uses single quotes. If you use double quotes then you are going to get a parse error from aspx.

Add event functions to your web controls. These events need to be monitored so that the appropriate actions can be taken when they are fired. They work exactly as did before but figuring out which row the event is being fired on is the tricky part. You will notice that all my text boxes fire the same change event - this is optional.

Write the event code. You will need a function to delete a row and to update your data-source with changes from the web-controls. You will also need a function to find out the index of the row on which the event is being fired on. Once you have the index you can use that to update or delete the corresponding index in your data-source.

That is basically the gist of it. Only thing left to do is to save your DataTable to somewhere permanent. In this example I loop through and print the values in my data-source when you click the save button. You might (and should) be using something more sophisticated.

Download

repeater.zip - zip file

Other Info

Eventually you might end up working on a datasource which is "live". Inorder to keep track of the records which are live and ones that are just added to the form aka "new". You might need to have some sort of flag on each row.

if you need to refer to controls in a row using javascript use this code;

<%# Container.uniqueid %>:control_name

By owen on Articles

Getting started in computer programming (Articles)

2005-04-13 07:13:45

Computer programming in general is about solving problems and avoiding errors. It is defined as; creating a sequence of instructions to enable the computer to do something

Computer programs are written by programmers. Whom spend most of their time trying to figure out the best way to solve a problem using the tools or languages which they know. Knowing a language is crucial because a programmer will never be able to solve a program problem unless he or she knows how to solve the problem. So the next question is how does a programmer learn to solve problem?

Problems usually have many solutions

The more problems you have solved in the past the easier it is to solve future problems. In effect the more expirience you have solving problems and writing code - the better programmer you become over time. Most problems are solved in a number of ways

Trail and error - spend an amount of time trying different bits of code until you come up with an answer.

Research - finding somebody or some information on how to solve a problem.

Experience - you did something similar before so this problem can be solved basically the same way.

Step 1: Getting started

You need to find a nice little language in which to write your code. Finding a nice language is important. You should be able to setup and run you program without any help from anybody. Some people may need programming books or tutorials. Make sure you have the help files that come with the language so that you can look up the meanings of errors you will encounter. Nice languages have nice help files that you can read and understand. Some errors are not in the help and you have to ask a human to explain it. Seek professional help.

Step 2: Find a problem to solve

Once you up and running with one or two simple programs you learned in class, tv or got from somebody, you should find yourself a problem to solve. It is important for you find a problem of your own choosing so that you will be committed to solving it. It could be a calculator, game or operating system it does not matter - everything starts somewhere.

Step 3: write the program

Start writing your program. It may take you 2 days, 2 months or 2 years to solve the problem depending on how big the problem is or how quickly you learn. In some cases problems are never solved and are left waiting in a file somewhere. It is important not to rush through when writing your program - keep a steady pace. If a problem come up often times it is best to just shutdown you machine and go to sleep.

Step 4: Re-write the program

A program usually never comes to a state of completion. You will realise that the closer you come to completing it the more new solutions appear. So you either stop writing the program at some point or you keep messing with it indefinitely.

Step 5: Find another problem

After you reach a point in your first program and your show it off to your friends, you will need to find a new project to work on. The more problems you solve the better you will become. Note that sometimes a problem cannot be completely solved.

By owen on Articles

How to think like a programmer (Articles)

2005-03-29 07:14:59

A good program starts in the head of a programmer. You first consider whether the problem you are about to solve (aka the program) is impossible to write or not. In a class situation a teacher will usually give you a solvable problem.

When given a problem, a lab assignment or whatever, try to break it up into parts. So parts of a program have to completed before other parts and from this you should be able to figure out where to start writing your program. Think of it as a river (flow chart) that runs from the top of a mountain down until it reachs the sea. It is not a lake.

In most cases your program will involve some sort of menu. Think of the menu as a series of IF_STATEMENTS. If one thing happens THEN another thing happens and so on and so forth. Sometimes only after you start writing the program you will be able to finish it.

Things to do

Most new programmers often make the mistake of trying to put the entire program into their head - this is not good. Write little parts of the program one at a time ( in a logical order ).

Do not write the entire program then try to compile it. A program works one line at a time. Start out by writing the first 5 line of the program - then compile. if java sucks, compile after every 10 lines. This will help build up your skills and ensure that by the time you reach the end, the program will actually run with out errors. FIND AND FIX ERRORS AS YOU GO ALONG. Errors will be harder to find after to finish typing 500 lines.

Look at other peoples code.

Start writing the program

Copy and paste. If you have written a similar piece of code before copy it and use it in you new program. Donot waste time writing it again.

Ask questions though they maybe stupid, its a learning process. Programmers become better through constant research.

Donot wait until the last minute, the sooner you start - the better.

By owen on Articles

Software Programming Patterns (Articles)

2005-01-26 21:51:34

It is important to understand why some programmers write code differently from other programmers and the reasoning behind each block or section of code. This article is not directed at any particular language or style of programming, it is a discussion of the differences computer code which is written to solve various problems. The patterns may overlap but nothing is ever defined specifically and are to be considered as a general overview.

Error Reduction

At some point code may be written in order to reduce errors that may arise at a late point in time. In a computer program a error can arise at any point in anytime and for any random reason. In order to reduce the effects of such an occurrence some parts of a program might be written in order to reduce the effect of such an error.

Read Ability

The code is written so that it is easy to read by anybody that may happen to decide to read it at some point in the future. Sometimes also referred to as clean code but clean code is also relative to the experience of the reader.

Efficiency

The code is written so that it can make the best use of computer resources. This does not necessarily mean it is fast, easy to read or reduces possible errors.

Speed

Falls under 2 forms speed of execution and speed of development. Speed of execution involves writing the program so that it can run as fast as possible in the expected operating environment. Speed of development means it is written so the application can evolve or change at a high rate.

Simplicity

The code is written so that it is simple. Simplicity is relative but usually it spreads rapidly. Simple to read, update, integrate, extend etc.

Stability

The code is written so that it does not crash easily either by internal or external forces. Usually maximizing scalability and robustness.

Reusability

The code is written so that it can not only be used to solve the current problem but many future problems as well.

Friendliness

Code usually falls into 2 forms programmer friendly and user friendly. The first form is code written in order to make it easier to re-write or update. While the second form is directed towards code written in order to improve user interface efficiency. Code can also be language friendly, hardware friendly, etc.

Dependency

Often times code is written so that it is very dependent or very independent for whatever reason.

Conclusion

The patterns outlined are usually not mutually exclusive and it is often not possible to maintain a constant pattern through out an application. As to whether a pattern is more advantageous than another is dependent on several variables.

By owen on Articles

Online Infidelity or Cyber affair (Articles)

2004-12-07 14:09:53

We have all experienced the joys of online communication, where we communicate with friends, family and meet new people from near and far without leaving the comfort of our homes or offices. There is a growing trend for people in relationships to create intimate relations through cyberspace, this includes; cyber sex, e-mail and cheating via on-line chats, this is called Online Infidelity/Cyber affair. A survey done by MSNBC and Elle Magazine of people using the internet found that 10 percent of women and 19 percent of men, when online say they are single although they are not. Another study conducted by Psychologist Dr. Beatriz Mileham showed that approximately 30 percent of cyber affairs end up in a real-world affair. These online relationships start as innocently as, “How are you?” and can escalate from there to "are you spending the night?”.

The number of victims of Cyber Affair is on the rise, that is why I must share with you three Tell-Tale Signs that may be present if your partner (spouse) is having a Cyber affair, they are; (1) a change in your partner’s sleep patterns (2) a demand for privacy when using the PC and (3) ignored household chores. I will now explore these signs in detail.

(1) Change in your partner’s sleep patterns - Chat rooms and meeting places for cyber sex don't heat up until late at night, so the cheating partner will tend to stay up late to be a part of the action. Often, the partner suddenly begins coming to bed in the early-morning hours, and may leap out of bed an hour or two earlier in the mornings and bolt to the computer for a pre-work quickie.

(2) A demand for privacy when using the PC- With cyber affair cheaters usually search for greater privacy and secrecy surrounding their computer usage. The computer may be moved from a visible place to a secluded corner, password may be changed, and all online activities conducted in secrecy. If interrupted when online, the cheating partner may react with anger, defensiveness or quickly close the pages.

(3) Ignored household chores - When on-line time increases, household chores often go undone. That's not automatically a sign of a cyber affair, but in a relationship those dirty dishes, piles of laundry, and un-mowed lawns might indicate that someone else is competing for your partner’s attention. When your partner begins to invest more time and energy on-line and fails to keep up their end of the household bargain, it could signal that an on-line relationship is going on.

In closing, Cyber affairs are becoming very prominent so ladies and gentlemen if you see a change in you partner’s sleeping habits, a demand for privacy while using the PC and household chores been ignored, chances are “you a get bun online”. My friends open your eyes to these signs, and don’t be like Paul a friend of mine who saw the signs and choose to ignore them, he is now single not by choice but because of a cyber affair, don’t let this happen to you.

By Daimion on Articles