owenSoft.net

The Miniature Earth (Video Blog)

2008-10-14 11:25:13

the earth summarized down to 100 people;

http://www.youtube.com/watch?v=rvTFKpIaQhM

By owen on Video Blog

new leaf blue tea (Pimp Juice)

2008-10-10 13:51:46

with pure cane sugar

this is rare

usually it's high fructose corn syrup

which I am allergic to

By Gods Child on Pimp Juice

54 - 46 (was my number) (Logbook)

2008-10-08 12:08:14

Its not that I have a problem with waiting, I just have things to do, except when there is a hurricane. Which is why I like hurricanes so much. Ideas come to me in my sleep like nightmares - suddenly and sporadically like a monkey. I have to rid myself of them or they'll fester. People will then notice that I'm not listening to what they have to say, but instead writing little notes on the back of my hand.

People tend to say the same things, over and over, in slightly different ways. Like flashing lights. Don't be surprised that I'm not surprised when you say that you got kicked in the ovaries - you had it coming. Karma Police. Your a bueatiful child. Someone is trying to tell you something. They are writing messages on the walls and sidewalks of the places we live. We can dance if we want to, we can leave your friends behind, 'Cause your friends don't dance and if they don't dance, Well they're no friends of mine.

Yesterday my sedentary lifestyle was interrupted by an extended meeting up at the water pond. Followed by a "lunch road trip". Followed by a post meeting road trip. Followed by a transportation detour. All these accompanied by indefinite periods of waiting. All I have to say is that I'm not pleased. Compounded by the fact that I have to be staying up late at night getting high like paper.

By owen on Logbook

Black Picture Frames (The random photo journal)

2008-10-04 16:55:55

can do no evil

By owen on The random photo journal

buy low sell high? (Questions)

2008-10-01 11:43:41

so now that markets are crashing wouldn't it be a great time to buy some stocks and real estate?

By GC on Questions

Sagi (The high life)

2008-09-29 22:27:07

ugly logo

By owen on The high life

GunMetal Bently (The wheels project)

2008-09-29 22:25:29

florida

By owen on The wheels project

Yellow Car (The wheels project)

2008-09-29 22:23:16

florida

By owen on The wheels project

Silver Car (The wheels project)

2008-09-29 22:22:35

florida

By owen on The wheels project

Green Car (The wheels project)

2008-09-29 22:19:38

florida

By owen on The wheels project

So males do you after females that ignore you? (Questions)

2008-09-29 20:26:34

Individuals have a tendency to say that males dont really like females who push themselves unto them. They most times think that they are easy and take them for a one night stand. The pay more attention to the females who ignore them. And that they put more effort into getting her. So males do you or do you not go after females that ignore you?

By crazychick on Questions

How To Get The IT Department To Do Their Job (Video Blog)

2008-09-26 10:58:27

NB: The opinions expressed in this video are not those of this website, its authors, comments, IT department or hence forth stereotypes there of.

http://www.youtube.com/watch?v=5Pr3L6H80dw

By owen on Video Blog

Managing complexity in Software Development (Articles)

2008-09-26 10:56:20

In programming, sooner or later you will come up with a solution to a problem that is somewhat "complex". The said solution may be advantageous to the program in various ways. The thing to note is that you should ensure that his complexity is "contained". Far too often software developers let a complex solution to a simple problem seep in to the body of the program itself. As a result making the entire program unecessarily complex. Miracle solutions are proposed to increase productivity through various catch words that end with "-ibility".

For example the index page of my website is probably the most complex page in the entire website. Yet the website itself is quiet simple. The index page was not quite as complex as it was now. Originally it was a series of IF statements that directed the visitor to a requested page based on various parameters. IF PAGE == ABOUT THEN LOAD ABOUTPAGE. It was really REALLY simple. One day I realised that if I could find a uniformed way of determining the next page then I could replace all the IF statement was a controller or MVC (as they call it now a days). The new solution required careful thought.

As with every line of code or function created there are things to consider;

How is changing this page going to make the other existing pages BETTER.

How is changing this page going to make the other existing pages WORST.

how is changing this page going to affect the quality of code as a whole.

Will changing this page make the other pages more complex or less complex.

These are important points to consider when dealing with complexity. You should always beware of things that may unessarily complicate the entire program offering shortterm benefit but long term headache. If I had suddenly woke up and decided to change the index page to use a random MVC without considering how the actual MVC would affect the complexity of the program itself then I would have made a grave mistake which leads to people discontinuing software a year after it was implemented.

All things must be considered in light of the shortterm and the longterm when developing software. A piece of software that starts out complex will not get simpler as you develop it.Keep the simple parts simple It will only get more complicated until it collapses under the wieght of its own complexity. In the same light something very simple can be complicated by a misplaced bottle neck in the system that was implemented on a "whim". Implementing features on a "whim" or ad hoc without considering its benefits is the fastest way to complicate what was once a simple program. Keep your eye on the important parts of the program to ensure that it remains simple and that any complex algorithms and concepts are "Functionalized" away from the program's core purpose.

In the case of my index page (which loads all the other pages) it may seem to be against what I just said - a very complicated concept deep within the core of the application. The thing to note is that the index page itself is a FUNCTION. What it does is completely independent of the program. It can easily be replaced because the other pages are not affected by it, nor thou or both shall go with him. hmmm. It is a function. An important function but a function none the less. The other pages on the site are unaware of its existance and so are not affected by any low level changes that I make to it. The sub pages behave as if they are in a vacuum, unaffected by the index page. It is not a typical MVC that seeks to solve a problem by controlling/limiting structure rather than providing a genuine solution to the structure problem.

What I could have done and what most people do is make the index into a class. And then enslave other pages into a "house of cards" situation. Now instead of isolating the solution to a problem of IF statements - the programmer ends up complicating the entire program in order to simplify it. I am not saying that wide spread refractoring is not necessary. I am saying that the inplementing complex solutions to a problem should not be allowed to complicate the program as a whole. Find a way to solve the problem without creating thousands of little problems/new workflows in the progress. Alot of this is explained to more dept in software engineering anti-patterns

Now for the code.

Here I will list elements that add complexity when writing programs;

IF THEN ELSE Statements: Avoid having a catch all "else" statement. Usually it leads to logic bugs and poor clean up.

Avoid unecessary class implementations: There is nothing more annoying than having to do a "new" every single time you want to use a base class. Its pointless. If you only need one instance at a time why is it a class? Make a single function that manages itself. Always ensure that you know the ;why" behind everything you program so that you can better make it when it needs to change.

Avoid giving yourself future work or more per-module work: Now I understand that some people like the whole "house of cards" thing but really now. It is easy to copy development documents off the internet and pass then off as your own but hard to implement something that you have no expirence in using.

Avoid doing the same thing over and over with slight per-module changes: This is a another sign of a train wreak waiting to happen. Sooner or later you are going to have to refactor all those slight changes and you will realize that 3 lines at the top of every module was simply there to make you feel productive but added nothing to the program.

Avoid tight coupling of you classes. This often occurs by using checked exceptions to force calling processes to handle them. Hence causing every calling program to be tied to a useless/decorative exception tree of choas.

Avoid eating you own dog food: I cannot stress this enough.

Avoid fragmenting processes: There are times when you may be tempted to create a function for the purpose of simplifing a process. This usually happens when you have so much code that its difficult to really keep track of what is going on. In such a case avoid creating singleton functions that look like functions but are infact big GOTO statements. These singleton functions usually have to be called in a specific order and a specific custom object has to passed to them. Its better to just keep it all in one function with good documentation. Ten random singleton functions are neither helpful nor do make the program easier to read/manage.

Avoid classes with too many setup functions: Some may think its a good idea but classes should manage as much of its internal processes as possible. Avoid;

c = new calc class;

c.setid(10);

c.setname('test');

c.getdata();

c.getresultset();

ans = c.calculate();

Its better to create a function called ans = calculate_test(10, 'test'); Not only do you have less lines of code (per call) but the test calculation process is encapsulated.

Avoid try-catch-throw logic: if a function is boolean it should return true or false. It shouldn't throw random exceptions to the calling function. Try-catchs are often used as a lazy form of IF-ELSE. Situations like this should be avoided for the same reason as mention before.

Avoid bandaid errors, hiding errors and non-specific error messages. A system is not secure if its errors need to be a secret. Having clear error messages allows for quickly identifying problems during the development and testing phase and evening during the life of the system. Searching through log files for errors that could have been easily displayed to the user is a waste of time. Critical errors can be missed that are hidden for years in log files and catch statements. The last thing you want is someone to be calling you in the middle of the night about some program that you wrote 5 years ago. Assume All errors are fatal!

Assume all errors are fatal. Often times errors are ignored or logged at lower levels of the program and the program is allowed to continue. This is often done to prevent the program from crashing. PROGRAMS CRASH its what they do when something is wrong. It is more important in program processes to identify WHEN a error occurs as opposed to the order. Log files are good are error order but poor for edge case event errors.

Conclusion

If your going down the wrong road it never too late to turn back. A poorly written program is only good as long as no one knows about it. You can throw as much RAM or HARDWARE at it as you want. Sooner or later it will get replaced by a off the shelf software that is probably JUST AS BAD OR WORST THAN your custom developed software. And the software you wrote will be just another skeleton in your closet. The main difference will be that the off the shelf software has learned to manage its complexity, increase flexibility while meeting user requirements.

Often times there is nothing you can do but to just run with what you have, make as much documentation as you can and pray for the future developers.

By owen on Articles

God Does Answer Prayers (Logbook)

2008-09-19 21:54:13

There is this man at school who has been trying endlessly to get with some of the students from last year;I just happen to be one of those students.I have ridiculed,ignored and even taken advantage of the fact that he wants to get with me.When I left the school I was so overjoyed. I bought myself lunch at Fridays and topped it off with a slice of Coconut cake at Devon House. But then due to circumstances beyond my control I have to return to the same school and guess what he will still be there.I stood in disaray as I watched my hopes falling to the floor like a glass;shattered to pieces.

A conversation developed between us where in which I was told that he is ignoring me because I broke his heart. I laughed so hard I nearly fell off the chair that I sat on. How can I break something that wasnt whole in the first place? His heart is in little bits and pieces and he cant put it back together because he cant find the missing pieces of the puzzle he calls a heart.

While trying to talk his way into the cold dark vacuum that now occupies the spot where my heart used to be a young lady walked in. Now,this young lady isnt more than 16 and he is 30 something. They start talking he whispers in her ears and stuff next thing I know she start writing down digits. So I was like watch him. Typical Male! As I could say that;while turning off the AC he hit up his genitals. All I could say is God does answer prayers.

By crazychick on Logbook

Memories forever cherished! (Logbook)

2008-09-17 22:16:17

Memories forever cherished are the memories that were created while I was around you.They will go unaltered,unchanged,frozen in reality but constantly moving in my thoughts.If I had a picture frame I would frame it for the world to see.

These memories have taught me to push every minute to the limit.To cherish and savour every second that I get to spend with someone dear to me.I spent a moment with you where,the world stopped spinning for a while.At that moment I had a whole new perception,a different view of you.I was captivated in your eyes.I saw me through you."beauty is in the eyes of the beholder."I became aware of my beauty in your eyes!

If I could do it all over again would I do it the same way?A question I often ask myself. Yes,I would try to correct the mistake that I made.In regards to the moments that we spent together,the verbal exchange we had on the phone I remain untouch, all I would do is pray,hope and work towards us having some more moments like the ones that we had.

By crazychick on Logbook