Programmers monthly salary in Cebu based companies

[kamsky]

---

Of course Lines of Code matters.

Say you're writing 1000 lines of spaghetti code for a project that is due within 2 days and then on your way home you met an accident and died instantly. The project manager decides to put another guy as your replacement. When he starts to look at your code...he would want to kill himself...run to the balcony and jump 6 floors!!!!

"Good programmers write code that a computer can understand, but great programmers write code that a human can understand"

this is an old story. The new techniques of doing project is not just one programmer and also doing agile sd. If the programmer was hit by the bus (his life is more important than the project tough), worst scenario are you can just throw away few weeks code or just redo what he's doing. Specially in a team environment, your team mate would know a little bit of your code. Resignation and sudden death should is a risk that can occur and should be considered by the PM.

[javapenguin]

Of course Lines of Code matters.

Say you're writing 1000 lines of spaghetti code for a project that is due within 2 days and then on your way home you met an accident and died instantly. The project manager decides to put another guy as your replacement. When he starts to look at your code...he would want to kill himself...run to the balcony and jump 6 floors!!!!

"Good programmers write code that a computer can understand, but great programmers write code that a human can understand"

There should be allocated time for documentation, in this case the boss is not giving enough time so jumping from a balcony serves him right, hehehe

[kamsky]

There should be allocated time for documentation, in this case the boss is not giving enough time so jumping from a balcony serves him right, hehehe

how do you document code?

[dcabungcal]

how do you document code?

putting a comments along the way on the codes are already a simple way of documenting the code it self, but some language like Java has its way to generate code documentation (doc comments).

[javapenguin]

how do you document code?

If you were to continue the work of another programmer, what is the best way for you to understand his work? That should be the answer. For me it doesn't have to be the traditional way, you can even do video recording if you like as long you can pass on the idea to the next programmer.

[tantanix]

this is an old story. The new techniques of doing project is not just one programmer and also doing agile sd. If the programmer was hit by the bus (his life is more important than the project tough), worst scenario are you can just throw away few weeks code or just redo what he's doing. Specially in a team environment, your team mate would know a little bit of your code. Resignation and sudden death should is a risk that can occur and should be considered by the PM.

Yeah i know this is how it's done before...i was just exaggerating for the others to understand the importance of good programming.

Avoid long lines of code.

Refactor your code if your code is repetitive.

Apply good ol' object oriented approach.

Always put comments in your code if you're doing something that isn't understandable at first glance.

Document it after.

[vp-rakista]

average monthly salary should be 30K for programmers with 2-3 years experience

[kamsky]

If you were to continue the work of another programmer, what is the best way for you to understand his work? That should be the answer. For me it doesn't have to be the traditional way, you can even do video recording if you like as long you can pass on the idea to the next programmer.

that would add another effort. i dont want to do that, it's redundant, and i dont want to read another so many docs. .

why cant you just have a self-documenting code, readable, implements the design specified i.e. class and sequence diagrams.

your code should be good enough if you understand enough by looking just looking at the class names and method names. if the coder cannot follow good coding practice, adhering standard and styles, then there's no way he can write a good document for his code.

[Silver_clone]

well talking about documentation, hasolan jud ko. sungogon gud ko sa uban istiryans kay d na gud ko matug usahay.. .

starting naku is 5 digit ra tawn,ehehhe,,, **,***.00

but wen I invested on an IT company, ako nay boss.. hahahaha... d na ko mahasol..ako nay manghasol

[moz_k2]

If you were to continue the work of another programmer, what is the best way for you to understand his work? That should be the answer. For me it doesn't have to be the traditional way, you can even do video recording if you like as long you can pass on the idea to the next programmer.

mao ang ang sagad nga problem karon.
kay lahi2x ang programmer nga mobuhat sa project.
samot kagubot labi na kung maintenance projects.
kada programmer lahi2x ug style.

for me mas maayo jud kung imo sabton unsa ang dagan sa system.
kay kung imo sabton ug una ang code you might end up maintaining inefficient codes.

@topic
common karon kung entry level mga 15-18K