4 ms·
My suggestion is to : 1) Put your name as Author in every bit of code you have written. 2) Document everything about the app and publish it in an internal wik
by la64710 4y ago
My suggestion is to :
1) Put your name as Author in every bit of code you have written.
2) Document everything about the app and publish it in an internal wiki.
3) Find a way to distribute the wiki internally so everyone is aware of it.
4) Appreciate that the boss is taking your app to the board and is getting their sponsorship. Now ask for a good raise.
5) You don’t have to live in anyone’s shadow. Let people know what you do and get more familiar with the business side of things.
6) Credits Just like everything else in real world is complex and multidimensional.
- mikece 4y ago> 1) Put your name as Author in every bit of code you have written. Isn't that was `git blame` is for?
- Ancient 4y agoNo, because ... - Not all bosses are programmers. - No everyone knows about Git or how to use it. - Who regularly Git Blames lines of code to see who the author was? - Who would rather see the author name stand out in first line of code file versus doing Git Blame? - You can easily move the codebase without the Git history to another location (easy to delete the .git subdirectory). So it's best to add the author name as many places as possible and distribute it.
- deleted 4y ago[deleted]
- Simon_O_Rourke 4y agoDo all these, and before you start doing anything figure out some major app limiting feature that needs to get done, and present that along with a demand for a raise. No raise, good luck, you're heading to greener pastures.