Software House, The Problems We Have (part.2)

Business Market

As i told you before, this post will talk about the mistakes that many software houses do and of course it's all about the software and lil' bit about hardware things. Many companies want a business process computerizing these day, so there are many offers in the business market and attracts entrepreneurs to involve in that field as well, in this case is making software house. But many entrepreneurs haven't experienced enough about software house and even don't care about it.

It causes many software houses work wrong. Most of them don't understand the whole steps of making programme (Analytic, Designing, Programming and Beta Testing), the thing which is known is only Programming. That's why a programmer can work as Analyst, Designer and Beta Tester at the same time. Can you imagine that? The whole steps worked by one division only or even just a man! But the worst, they only paid as a Programmer and sometimes they also have to do the hardware things like networking, maintaining and many.

Programmer also can't have a meeting with client, that is'nt they right. Only Project Leader, System Analyst, Database Analyst or The Boss. But then Programmer expected to make the programme by their own mind, they only given the whole output data without have any discussion with the client. So they have to computerize a business process without involve to it. I think programmer can be a magician somehow, appearing something without any cause. According to information i read, it causes by wrong perspective of computer technician in this country. When we say that someone is a computer technician, they expect the man can do the whole computer things, hardware and software. Damn it crazy. Obviously programmer are kinda man who "just" build the programme, like i compared on last post -- on construction field, we can say programmer as a builder.

Software House

But of course all things about programme making with that way can be done, by time. In this case, the maker will work repeatedly. The programme will be analyzed, made, ran and bugged at the same time. This is'nt such an effective way to make a programme, furthermore the programme won't work in next 2 - 3 years because it's just made for this time only. When the company develops the business process, the programme has to be rebuilt. That's why we need an analyst, so the programme will stand as long as the business process is'nt changed because it's already analyzed completely. But programmer can't do that, this isn't about ignorance but professionality. You can't give two or more types of jobs to one man who works just for one. The programme making steps are also a class for someone who works in software development. From programmer to analyst, it's a career level according to experience and skill.

Those are real examples if the software house doesn't follow programme making steps, but sometimes there's a software house which understands the step but they too greedy to follow the whole steps. I know one of them, but there's no rule about it so what can i say. However the wrong way won't work too long, it will die about time. If only it doesn't make any change. This is just my opinion of some facts happen arround us, if you have any suggestion or critic just message me on facebook.