Mixing
![Competing with corporates for talent [closed]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgjbpfN9tAutmK93bJRC3ZoROZzi2TJDms5n8_qJuhgE0a9b52OOHayv3NGT8igAdFL7byXNst-_1DZK5SjrIJ28_6RQPUpBROqMs5s6jo-ZsjX8kjDwfxJufIitH3TaQRXWaGSQKRQib-f/s72-c/1.jpg)
How should reducing development costs metrics be listed on a resume?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
11
down vote
favorite
Every few months at work we add a feature X. On average it took 10,000 LOC (lines of code) to develop. Through design improvements I reduced it to an average 1,000 LOC, which meant fewer associated bugs and less duplication and effort.
I know metrics are good to have on a resume. How can I turn this into a metric? I know LOC doesn't translate to effort, but there is a correlation.
"Reduced development effort in LOC by 90%"?
resume software-industry
edited Jul 28 '12 at 3:34
animuson♦
3,016124068
asked Jul 27 '12 at 13:52
anon
1335
add a comment |Â
up vote
11
down vote
favorite
Every few months at work we add a feature X. On average it took 10,000 LOC (lines of code) to develop. Through design improvements I reduced it to an average 1,000 LOC, which meant fewer associated bugs and less duplication and effort.
I know metrics are good to have on a resume. How can I turn this into a metric? I know LOC doesn't translate to effort, but there is a correlation.
"Reduced development effort in LOC by 90%"?
resume software-industry
edited Jul 28 '12 at 3:34
animuson♦
3,016124068
asked Jul 27 '12 at 13:52
anon
1335
By itself, that wouldn't mean much to me. Do you have anything else that you can relate it to. As in a correlated drop in tech support calls or bug reports?
– Kevin
Jul 27 '12 at 14:04
Would you quantify bugs in terms of number of bugs? Some bugs are orders of magnitude worse than others, which is why I don't like that number.
– anon
Jul 27 '12 at 14:35
Anon, could you clarify if your mind is made up on putting something like this on your resume, or if you're interested in how this may or may not be viewed/read?
– jcmeloni
Jul 27 '12 at 18:11
I would like to quantify it somehow so it doesn't seem made-up, but am also interested in how it will be perceived.
– anon
Jul 27 '12 at 19:04
add a comment |Â
up vote
11
down vote
favorite
up vote
11
down vote
favorite
Every few months at work we add a feature X. On average it took 10,000 LOC (lines of code) to develop. Through design improvements I reduced it to an average 1,000 LOC, which meant fewer associated bugs and less duplication and effort.
I know metrics are good to have on a resume. How can I turn this into a metric? I know LOC doesn't translate to effort, but there is a correlation.
"Reduced development effort in LOC by 90%"?
resume software-industry
edited Jul 28 '12 at 3:34
animuson♦
3,016124068
asked Jul 27 '12 at 13:52
anon
1335
Every few months at work we add a feature X. On average it took 10,000 LOC (lines of code) to develop. Through design improvements I reduced it to an average 1,000 LOC, which meant fewer associated bugs and less duplication and effort.
I know metrics are good to have on a resume. How can I turn this into a metric? I know LOC doesn't translate to effort, but there is a correlation.
"Reduced development effort in LOC by 90%"?
resume software-industry
edited Jul 28 '12 at 3:34
animuson♦
3,016124068
asked Jul 27 '12 at 13:52
anon
1335
edited Jul 28 '12 at 3:34
animuson♦
3,016124068
edited Jul 28 '12 at 3:34
animuson♦
3,016124068
edited Jul 28 '12 at 3:34
animuson♦
3,016124068
3,016124068
asked Jul 27 '12 at 13:52
anon
1335
asked Jul 27 '12 at 13:52
anon
1335
asked Jul 27 '12 at 13:52
anon
1335
1335
By itself, that wouldn't mean much to me. Do you have anything else that you can relate it to. As in a correlated drop in tech support calls or bug reports?
– Kevin
Jul 27 '12 at 14:04
Would you quantify bugs in terms of number of bugs? Some bugs are orders of magnitude worse than others, which is why I don't like that number.
– anon
Jul 27 '12 at 14:35
Anon, could you clarify if your mind is made up on putting something like this on your resume, or if you're interested in how this may or may not be viewed/read?
– jcmeloni
Jul 27 '12 at 18:11
I would like to quantify it somehow so it doesn't seem made-up, but am also interested in how it will be perceived.
– anon
Jul 27 '12 at 19:04
add a comment |Â
By itself, that wouldn't mean much to me. Do you have anything else that you can relate it to. As in a correlated drop in tech support calls or bug reports?
– Kevin
Jul 27 '12 at 14:04
Would you quantify bugs in terms of number of bugs? Some bugs are orders of magnitude worse than others, which is why I don't like that number.
– anon
Jul 27 '12 at 14:35
Anon, could you clarify if your mind is made up on putting something like this on your resume, or if you're interested in how this may or may not be viewed/read?
– jcmeloni
Jul 27 '12 at 18:11
I would like to quantify it somehow so it doesn't seem made-up, but am also interested in how it will be perceived.
– anon
Jul 27 '12 at 19:04
By itself, that wouldn't mean much to me. Do you have anything else that you can relate it to. As in a correlated drop in tech support calls or bug reports?
– Kevin
Jul 27 '12 at 14:04
By itself, that wouldn't mean much to me. Do you have anything else that you can relate it to. As in a correlated drop in tech support calls or bug reports?
– Kevin
Jul 27 '12 at 14:04
Would you quantify bugs in terms of number of bugs? Some bugs are orders of magnitude worse than others, which is why I don't like that number.
– anon
Jul 27 '12 at 14:35
Would you quantify bugs in terms of number of bugs? Some bugs are orders of magnitude worse than others, which is why I don't like that number.
– anon
Jul 27 '12 at 14:35
Anon, could you clarify if your mind is made up on putting something like this on your resume, or if you're interested in how this may or may not be viewed/read?
– jcmeloni
Jul 27 '12 at 18:11
Anon, could you clarify if your mind is made up on putting something like this on your resume, or if you're interested in how this may or may not be viewed/read?
– jcmeloni
Jul 27 '12 at 18:11
I would like to quantify it somehow so it doesn't seem made-up, but am also interested in how it will be perceived.
– anon
Jul 27 '12 at 19:04
I would like to quantify it somehow so it doesn't seem made-up, but am also interested in how it will be perceived.
– anon
Jul 27 '12 at 19:04
add a comment |Â
5 Answers
5
active
oldest
votes
up vote
10
down vote
accepted
I personally would not be interested in an LOC metric on a resume. However, if you could say that you
Reduced development time for complex features by n% while maintaining high quality output
I'd be interested. My point is not to use the LOC metric but to associate it with something else that is more meaningful. Of course, if you say this, it should be true - reducing LOC by that much should probably be associated with less development time.
answered Jul 27 '12 at 14:23
FrustratedWithFormsDesigner
10.7k43957
2
That's definitely a more meaningful metric than Lines of Code. Plus cutting that many lines of code probably had an exponential effect on time saved; much less to test, which hopefully makes development time/effort even less
– Rarity
Jul 27 '12 at 14:27
I have some numbers but am not sure how accurate they are. How do you typically measure development costs?
– anon
Jul 27 '12 at 14:30
@anon: You could measure it in time: how many hours to build, test, deploy). You could measure in dollars: how much to pay for the resources (not just salaries but maybe also tools, hardware, hosting accounts, etc...).
– FrustratedWithFormsDesigner
Jul 27 '12 at 14:33
add a comment |Â
up vote
4
down vote
LOC is a lousy metric. After all, linebreaks normally count as LOC. Plenty of languages don't even require whitespace at all, yet reducing a 1200 line program to a single line might sound impressive, but it turns into an obfuscated mess for maintenence and upkeep. I think a bit of context might be useful, mentioning the language(es) involved, that your changes made the code more efficient, and maybe a short bit about reducing the number of LOC.
answered Jul 27 '12 at 14:21
acolyte
3,0531632
add a comment |Â
up vote
3
down vote
I would include it as a quick statement "reduced code base size by 90%" and make it just one of a half dozen or more such references to achievements
answered Jul 28 '12 at 4:35
Michael Durrant
9,68122856
add a comment |Â
up vote
2
down vote
I have a section under my employers where I list any notable accomplishments. In theory you could list that statistic there.
However, unless you can enumerate the savings in terms of real cost then listing it on a resume is not very useful.
Some related metrics that might be useful:
- Improved performance Benchmarks
- Reduced actual costs of operation
- Reduced actual costs of development
- Reduced actual costs of on going maintenance.
However for these, as a prospective employer I am going to want to to be able to explain and talk about how you came by your metrics. You need to be able to speak with confidence about them and understand those numbers inside out. If you can not do that Unless you have some documentation to back up the numbers I would leave them off. A generic "significant improvement in X," suffices.
Lean Metrics is a good way of coming by these numbers. However it requires planning ahead to capture the before and after numbers. It is hard to establish good numbers for a resume after you have left a position. So it is important if you wish to include them in your resume that you capture them regularly. Fortunately they are also useful in business so you manager will probably thank you for producing the numbers for him.
answered Jul 27 '12 at 16:45
IDrinkandIKnowThings
43.9k1398188
add a comment |Â
up vote
1
down vote
I think the best thing to do is to describe in convincing and appropriately detailed terms what benefit you provided to the project.
However, using "metrics" like percentages and cost reduction in dollars or time or LOC can be really hard to do right. These things are not necessarily measured accurately (or even valid-- in the case of LOC) and they are rarely the result of the singular efforts of one person.
I know that career advice these days says to cite "metrics" to quantify job experiences, but they're dubious figures unless you can back them up and make a strong case for why they're valid and true.
answered Jul 27 '12 at 15:21
Angelo
6,15621631
add a comment |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
10
down vote
accepted
I personally would not be interested in an LOC metric on a resume. However, if you could say that you
Reduced development time for complex features by n% while maintaining high quality output
I'd be interested. My point is not to use the LOC metric but to associate it with something else that is more meaningful. Of course, if you say this, it should be true - reducing LOC by that much should probably be associated with less development time.
answered Jul 27 '12 at 14:23
FrustratedWithFormsDesigner
10.7k43957
2
That's definitely a more meaningful metric than Lines of Code. Plus cutting that many lines of code probably had an exponential effect on time saved; much less to test, which hopefully makes development time/effort even less
– Rarity
Jul 27 '12 at 14:27
I have some numbers but am not sure how accurate they are. How do you typically measure development costs?
– anon
Jul 27 '12 at 14:30
@anon: You could measure it in time: how many hours to build, test, deploy). You could measure in dollars: how much to pay for the resources (not just salaries but maybe also tools, hardware, hosting accounts, etc...).
– FrustratedWithFormsDesigner
Jul 27 '12 at 14:33
add a comment |Â
up vote
10
down vote
accepted
I personally would not be interested in an LOC metric on a resume. However, if you could say that you
Reduced development time for complex features by n% while maintaining high quality output
I'd be interested. My point is not to use the LOC metric but to associate it with something else that is more meaningful. Of course, if you say this, it should be true - reducing LOC by that much should probably be associated with less development time.
answered Jul 27 '12 at 14:23
FrustratedWithFormsDesigner
10.7k43957
2
That's definitely a more meaningful metric than Lines of Code. Plus cutting that many lines of code probably had an exponential effect on time saved; much less to test, which hopefully makes development time/effort even less
– Rarity
Jul 27 '12 at 14:27
I have some numbers but am not sure how accurate they are. How do you typically measure development costs?
– anon
Jul 27 '12 at 14:30
@anon: You could measure it in time: how many hours to build, test, deploy). You could measure in dollars: how much to pay for the resources (not just salaries but maybe also tools, hardware, hosting accounts, etc...).
– FrustratedWithFormsDesigner
Jul 27 '12 at 14:33
add a comment |Â
up vote
10
down vote
accepted
up vote
10
down vote
accepted
I personally would not be interested in an LOC metric on a resume. However, if you could say that you
Reduced development time for complex features by n% while maintaining high quality output
I'd be interested. My point is not to use the LOC metric but to associate it with something else that is more meaningful. Of course, if you say this, it should be true - reducing LOC by that much should probably be associated with less development time.
answered Jul 27 '12 at 14:23
FrustratedWithFormsDesigner
10.7k43957
I personally would not be interested in an LOC metric on a resume. However, if you could say that you
Reduced development time for complex features by n% while maintaining high quality output
I'd be interested. My point is not to use the LOC metric but to associate it with something else that is more meaningful. Of course, if you say this, it should be true - reducing LOC by that much should probably be associated with less development time.
answered Jul 27 '12 at 14:23
FrustratedWithFormsDesigner
10.7k43957
answered Jul 27 '12 at 14:23
FrustratedWithFormsDesigner
10.7k43957
answered Jul 27 '12 at 14:23
FrustratedWithFormsDesigner
10.7k43957
answered Jul 27 '12 at 14:23
FrustratedWithFormsDesigner
10.7k43957
10.7k43957
2
That's definitely a more meaningful metric than Lines of Code. Plus cutting that many lines of code probably had an exponential effect on time saved; much less to test, which hopefully makes development time/effort even less
– Rarity
Jul 27 '12 at 14:27
I have some numbers but am not sure how accurate they are. How do you typically measure development costs?
– anon
Jul 27 '12 at 14:30
@anon: You could measure it in time: how many hours to build, test, deploy). You could measure in dollars: how much to pay for the resources (not just salaries but maybe also tools, hardware, hosting accounts, etc...).
– FrustratedWithFormsDesigner
Jul 27 '12 at 14:33
add a comment |Â
2
That's definitely a more meaningful metric than Lines of Code. Plus cutting that many lines of code probably had an exponential effect on time saved; much less to test, which hopefully makes development time/effort even less
– Rarity
Jul 27 '12 at 14:27
I have some numbers but am not sure how accurate they are. How do you typically measure development costs?
– anon
Jul 27 '12 at 14:30
@anon: You could measure it in time: how many hours to build, test, deploy). You could measure in dollars: how much to pay for the resources (not just salaries but maybe also tools, hardware, hosting accounts, etc...).
– FrustratedWithFormsDesigner
Jul 27 '12 at 14:33
2
2
That's definitely a more meaningful metric than Lines of Code. Plus cutting that many lines of code probably had an exponential effect on time saved; much less to test, which hopefully makes development time/effort even less
– Rarity
Jul 27 '12 at 14:27
That's definitely a more meaningful metric than Lines of Code. Plus cutting that many lines of code probably had an exponential effect on time saved; much less to test, which hopefully makes development time/effort even less
– Rarity
Jul 27 '12 at 14:27
I have some numbers but am not sure how accurate they are. How do you typically measure development costs?
– anon
Jul 27 '12 at 14:30
I have some numbers but am not sure how accurate they are. How do you typically measure development costs?
– anon
Jul 27 '12 at 14:30
@anon: You could measure it in time: how many hours to build, test, deploy). You could measure in dollars: how much to pay for the resources (not just salaries but maybe also tools, hardware, hosting accounts, etc...).
– FrustratedWithFormsDesigner
Jul 27 '12 at 14:33
@anon: You could measure it in time: how many hours to build, test, deploy). You could measure in dollars: how much to pay for the resources (not just salaries but maybe also tools, hardware, hosting accounts, etc...).
– FrustratedWithFormsDesigner
Jul 27 '12 at 14:33
add a comment |Â
up vote
4
down vote
LOC is a lousy metric. After all, linebreaks normally count as LOC. Plenty of languages don't even require whitespace at all, yet reducing a 1200 line program to a single line might sound impressive, but it turns into an obfuscated mess for maintenence and upkeep. I think a bit of context might be useful, mentioning the language(es) involved, that your changes made the code more efficient, and maybe a short bit about reducing the number of LOC.
answered Jul 27 '12 at 14:21
acolyte
3,0531632
add a comment |Â
up vote
4
down vote
LOC is a lousy metric. After all, linebreaks normally count as LOC. Plenty of languages don't even require whitespace at all, yet reducing a 1200 line program to a single line might sound impressive, but it turns into an obfuscated mess for maintenence and upkeep. I think a bit of context might be useful, mentioning the language(es) involved, that your changes made the code more efficient, and maybe a short bit about reducing the number of LOC.
answered Jul 27 '12 at 14:21
acolyte
3,0531632
add a comment |Â
up vote
4
down vote
up vote
4
down vote
LOC is a lousy metric. After all, linebreaks normally count as LOC. Plenty of languages don't even require whitespace at all, yet reducing a 1200 line program to a single line might sound impressive, but it turns into an obfuscated mess for maintenence and upkeep. I think a bit of context might be useful, mentioning the language(es) involved, that your changes made the code more efficient, and maybe a short bit about reducing the number of LOC.
answered Jul 27 '12 at 14:21
acolyte
3,0531632
LOC is a lousy metric. After all, linebreaks normally count as LOC. Plenty of languages don't even require whitespace at all, yet reducing a 1200 line program to a single line might sound impressive, but it turns into an obfuscated mess for maintenence and upkeep. I think a bit of context might be useful, mentioning the language(es) involved, that your changes made the code more efficient, and maybe a short bit about reducing the number of LOC.
answered Jul 27 '12 at 14:21
acolyte
3,0531632
answered Jul 27 '12 at 14:21
acolyte
3,0531632
answered Jul 27 '12 at 14:21
acolyte
3,0531632
answered Jul 27 '12 at 14:21
acolyte
3,0531632
3,0531632
add a comment |Â
add a comment |Â
up vote
3
down vote
I would include it as a quick statement "reduced code base size by 90%" and make it just one of a half dozen or more such references to achievements
answered Jul 28 '12 at 4:35
Michael Durrant
9,68122856
add a comment |Â
up vote
3
down vote
I would include it as a quick statement "reduced code base size by 90%" and make it just one of a half dozen or more such references to achievements
answered Jul 28 '12 at 4:35
Michael Durrant
9,68122856
add a comment |Â
up vote
3
down vote
up vote
3
down vote
I would include it as a quick statement "reduced code base size by 90%" and make it just one of a half dozen or more such references to achievements
answered Jul 28 '12 at 4:35
Michael Durrant
9,68122856
I would include it as a quick statement "reduced code base size by 90%" and make it just one of a half dozen or more such references to achievements
answered Jul 28 '12 at 4:35
Michael Durrant
9,68122856
answered Jul 28 '12 at 4:35
Michael Durrant
9,68122856
answered Jul 28 '12 at 4:35
Michael Durrant
9,68122856
answered Jul 28 '12 at 4:35
Michael Durrant
9,68122856
9,68122856
add a comment |Â
add a comment |Â
up vote
2
down vote
I have a section under my employers where I list any notable accomplishments. In theory you could list that statistic there.
However, unless you can enumerate the savings in terms of real cost then listing it on a resume is not very useful.
Some related metrics that might be useful:
- Improved performance Benchmarks
- Reduced actual costs of operation
- Reduced actual costs of development
- Reduced actual costs of on going maintenance.
However for these, as a prospective employer I am going to want to to be able to explain and talk about how you came by your metrics. You need to be able to speak with confidence about them and understand those numbers inside out. If you can not do that Unless you have some documentation to back up the numbers I would leave them off. A generic "significant improvement in X," suffices.
Lean Metrics is a good way of coming by these numbers. However it requires planning ahead to capture the before and after numbers. It is hard to establish good numbers for a resume after you have left a position. So it is important if you wish to include them in your resume that you capture them regularly. Fortunately they are also useful in business so you manager will probably thank you for producing the numbers for him.
answered Jul 27 '12 at 16:45
IDrinkandIKnowThings
43.9k1398188
add a comment |Â
up vote
2
down vote
I have a section under my employers where I list any notable accomplishments. In theory you could list that statistic there.
However, unless you can enumerate the savings in terms of real cost then listing it on a resume is not very useful.
Some related metrics that might be useful:
- Improved performance Benchmarks
- Reduced actual costs of operation
- Reduced actual costs of development
- Reduced actual costs of on going maintenance.
However for these, as a prospective employer I am going to want to to be able to explain and talk about how you came by your metrics. You need to be able to speak with confidence about them and understand those numbers inside out. If you can not do that Unless you have some documentation to back up the numbers I would leave them off. A generic "significant improvement in X," suffices.
Lean Metrics is a good way of coming by these numbers. However it requires planning ahead to capture the before and after numbers. It is hard to establish good numbers for a resume after you have left a position. So it is important if you wish to include them in your resume that you capture them regularly. Fortunately they are also useful in business so you manager will probably thank you for producing the numbers for him.
answered Jul 27 '12 at 16:45
IDrinkandIKnowThings
43.9k1398188
add a comment |Â
up vote
2
down vote
up vote
2
down vote
I have a section under my employers where I list any notable accomplishments. In theory you could list that statistic there.
However, unless you can enumerate the savings in terms of real cost then listing it on a resume is not very useful.
Some related metrics that might be useful:
- Improved performance Benchmarks
- Reduced actual costs of operation
- Reduced actual costs of development
- Reduced actual costs of on going maintenance.
However for these, as a prospective employer I am going to want to to be able to explain and talk about how you came by your metrics. You need to be able to speak with confidence about them and understand those numbers inside out. If you can not do that Unless you have some documentation to back up the numbers I would leave them off. A generic "significant improvement in X," suffices.
Lean Metrics is a good way of coming by these numbers. However it requires planning ahead to capture the before and after numbers. It is hard to establish good numbers for a resume after you have left a position. So it is important if you wish to include them in your resume that you capture them regularly. Fortunately they are also useful in business so you manager will probably thank you for producing the numbers for him.
answered Jul 27 '12 at 16:45
IDrinkandIKnowThings
43.9k1398188
I have a section under my employers where I list any notable accomplishments. In theory you could list that statistic there.
However, unless you can enumerate the savings in terms of real cost then listing it on a resume is not very useful.
Some related metrics that might be useful:
- Improved performance Benchmarks
- Reduced actual costs of operation
- Reduced actual costs of development
- Reduced actual costs of on going maintenance.
However for these, as a prospective employer I am going to want to to be able to explain and talk about how you came by your metrics. You need to be able to speak with confidence about them and understand those numbers inside out. If you can not do that Unless you have some documentation to back up the numbers I would leave them off. A generic "significant improvement in X," suffices.
Lean Metrics is a good way of coming by these numbers. However it requires planning ahead to capture the before and after numbers. It is hard to establish good numbers for a resume after you have left a position. So it is important if you wish to include them in your resume that you capture them regularly. Fortunately they are also useful in business so you manager will probably thank you for producing the numbers for him.
answered Jul 27 '12 at 16:45
IDrinkandIKnowThings
43.9k1398188
edited Jul 27 '12 at 18:27
answered Jul 27 '12 at 16:45
IDrinkandIKnowThings
43.9k1398188
answered Jul 27 '12 at 16:45
IDrinkandIKnowThings
43.9k1398188
answered Jul 27 '12 at 16:45
IDrinkandIKnowThings
43.9k1398188
43.9k1398188
add a comment |Â
add a comment |Â
up vote
1
down vote
I think the best thing to do is to describe in convincing and appropriately detailed terms what benefit you provided to the project.
However, using "metrics" like percentages and cost reduction in dollars or time or LOC can be really hard to do right. These things are not necessarily measured accurately (or even valid-- in the case of LOC) and they are rarely the result of the singular efforts of one person.
I know that career advice these days says to cite "metrics" to quantify job experiences, but they're dubious figures unless you can back them up and make a strong case for why they're valid and true.
answered Jul 27 '12 at 15:21
Angelo
6,15621631
add a comment |Â
up vote
1
down vote
I think the best thing to do is to describe in convincing and appropriately detailed terms what benefit you provided to the project.
However, using "metrics" like percentages and cost reduction in dollars or time or LOC can be really hard to do right. These things are not necessarily measured accurately (or even valid-- in the case of LOC) and they are rarely the result of the singular efforts of one person.
I know that career advice these days says to cite "metrics" to quantify job experiences, but they're dubious figures unless you can back them up and make a strong case for why they're valid and true.
answered Jul 27 '12 at 15:21
Angelo
6,15621631
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I think the best thing to do is to describe in convincing and appropriately detailed terms what benefit you provided to the project.
However, using "metrics" like percentages and cost reduction in dollars or time or LOC can be really hard to do right. These things are not necessarily measured accurately (or even valid-- in the case of LOC) and they are rarely the result of the singular efforts of one person.
I know that career advice these days says to cite "metrics" to quantify job experiences, but they're dubious figures unless you can back them up and make a strong case for why they're valid and true.
answered Jul 27 '12 at 15:21
Angelo
6,15621631
I think the best thing to do is to describe in convincing and appropriately detailed terms what benefit you provided to the project.
However, using "metrics" like percentages and cost reduction in dollars or time or LOC can be really hard to do right. These things are not necessarily measured accurately (or even valid-- in the case of LOC) and they are rarely the result of the singular efforts of one person.
I know that career advice these days says to cite "metrics" to quantify job experiences, but they're dubious figures unless you can back them up and make a strong case for why they're valid and true.
answered Jul 27 '12 at 15:21
Angelo
6,15621631
edited Jul 27 '12 at 17:10
answered Jul 27 '12 at 15:21
Angelo
6,15621631
answered Jul 27 '12 at 15:21
Angelo
6,15621631
answered Jul 27 '12 at 15:21
Angelo
6,15621631
6,15621631
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f2863%2fhow-should-reducing-development-costs-metrics-be-listed-on-a-resume%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
By itself, that wouldn't mean much to me. Do you have anything else that you can relate it to. As in a correlated drop in tech support calls or bug reports?
– Kevin
Jul 27 '12 at 14:04
Would you quantify bugs in terms of number of bugs? Some bugs are orders of magnitude worse than others, which is why I don't like that number.
– anon
Jul 27 '12 at 14:35
Anon, could you clarify if your mind is made up on putting something like this on your resume, or if you're interested in how this may or may not be viewed/read?
– jcmeloni
Jul 27 '12 at 18:11
I would like to quantify it somehow so it doesn't seem made-up, but am also interested in how it will be perceived.
– anon
Jul 27 '12 at 19:04