If you are into software, and if you need to demand more you have to prove you can write very complex code so that company never dares to replace you. So you can demand increments whenever you please since your code is not possible to easily modified by others.
If your code is easy to modify by any person, company will not pay you any attention even if you threat to resign. But don't worry there are solutions for this kind of issues.
following is a brief extract from the site,
To foil the maintenance programmer, you have to understand how he thinks. He has your giant program. He has no time to read it all, much less understand it. He wants to rapidly find the place to make his change, make it and get out and have no unexpected side effects from the change. He views your code through a toilet paper tube. He can only see a tiny piece of your program at a time. You want to make sure he can never get at the big picture from doing that. You want to make it as hard as possible for him to find the code he is looking for. But even more important, you want to make it as awkward as possible for him to safely ignore anything.
Programmers are lulled into complacency by conventions. By every once in a while, by subtly violating convention, you force him to read every line of your code with a magnifying glass.
You might get the idea that every language feature makes code unmaintainable — not so, only if properly misused.
for more information :
http://mindprod.com/jgloss/unmain.html
If your code is easy to modify by any person, company will not pay you any attention even if you threat to resign. But don't worry there are solutions for this kind of issues.
following is a brief extract from the site,
To foil the maintenance programmer, you have to understand how he thinks. He has your giant program. He has no time to read it all, much less understand it. He wants to rapidly find the place to make his change, make it and get out and have no unexpected side effects from the change. He views your code through a toilet paper tube. He can only see a tiny piece of your program at a time. You want to make sure he can never get at the big picture from doing that. You want to make it as hard as possible for him to find the code he is looking for. But even more important, you want to make it as awkward as possible for him to safely ignore anything.
Programmers are lulled into complacency by conventions. By every once in a while, by subtly violating convention, you force him to read every line of your code with a magnifying glass.
You might get the idea that every language feature makes code unmaintainable — not so, only if properly misused.
for more information :
http://mindprod.com/jgloss/unmain.html
