Why the change is easy when you are doing it simple

Wednesday, June 18, 2008

Recently I was assigned a tasked to write a particular program using the OO language called ABAP.
ABAP is a language invented by SAP AG to customize it's applications. Like any other programmer (can't say most of them are like that though :) )I just started the coding part and in about a 4-5 days I completed it and gave it for testing.
Now starts the real deal. The testing person found many bugs ( Not to mention that I could not believe that a person like me actually made those errors. Because some of them were too simple. You know what i mean). A certain error required the flow of the program to be changed but the problem was that if i did the change it would require me to change some other places as well. Resulting in a major modification to the program.
Which might result in creating more bugs than previously occurred.

Anyways my point is, if you can do a thing with simple concepts and maybe convert the hard problems or matters in to simple things, a change or a major modification or a transition might not cost you soooo much than you might expect.


Gaveen said...

Good to see you blog after sometime. :)

About the issues you mentioned, yes the simplicity is the king. :)

Anyway, a BDD or TDD tool might help you out. I don't know if there's any such thing available for ABAP like RSpec (Ruby) or JSpec (Java).

Thilanka said...

Yeah thanks. It's been a long time since I updated the blog. :)

I suppose they are diagramming tools.

Gaveen said...

No dude, BDD & TDD stands for Behavior Driven Development and Test Driven Development. In my previous comment I mentioned a couple of tools RSpec (Ruby) and I mistakenly called JSpec. The Java tool should be JBehave I think. And remember JUnit test in Java? :)

Anyway, I still haven heard about such a tool for ABAP.