How many lines a day
-
Hi all, No not coke! :doh: I was just wondering on average how many lines of code a day you produce. I am pretty new to development and have been on my first asp.net job since leaving uni. I mean i clock off work in about 15 minutes and i reckon today i have written around 1500 lines of code. Not having anything previous to go on is this a normal amount? Do people write more? I mean I realise I am prob still a bit slow as I am still learning. I am just after an indication really :D Cheers Ian
-
Hi all, No not coke! :doh: I was just wondering on average how many lines of code a day you produce. I am pretty new to development and have been on my first asp.net job since leaving uni. I mean i clock off work in about 15 minutes and i reckon today i have written around 1500 lines of code. Not having anything previous to go on is this a normal amount? Do people write more? I mean I realise I am prob still a bit slow as I am still learning. I am just after an indication really :D Cheers Ian
Senseicads wrote:
No not coke!
Oh...never mind then :)
Senseicads wrote:
I was just wondering on average how many lines of code a day you produce.
Since joining The Code Project, about 3. Mark
"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder
-
Hi all, No not coke! :doh: I was just wondering on average how many lines of code a day you produce. I am pretty new to development and have been on my first asp.net job since leaving uni. I mean i clock off work in about 15 minutes and i reckon today i have written around 1500 lines of code. Not having anything previous to go on is this a normal amount? Do people write more? I mean I realise I am prob still a bit slow as I am still learning. I am just after an indication really :D Cheers Ian
What does the number of lines of code you write in a day have to do with anything? I mean I can type pretty fast so I know I could blow the doors off that 1500 but what would that mean? Is this a typing job? Why "lines of code", why not words per minute like a secretary?
Senseicads wrote:
since leaving uni.
Either you weren't listening in class or that University is worthless.
-
Hi all, No not coke! :doh: I was just wondering on average how many lines of code a day you produce. I am pretty new to development and have been on my first asp.net job since leaving uni. I mean i clock off work in about 15 minutes and i reckon today i have written around 1500 lines of code. Not having anything previous to go on is this a normal amount? Do people write more? I mean I realise I am prob still a bit slow as I am still learning. I am just after an indication really :D Cheers Ian
On average? Maybe 100. Design, debugging, and optimization, when combined, lead to a big process, which means that even though I may initially write 500 lines, revising my code, learning about new things that I can do to reduce code while making the program run more efficiently take just as much time. That said, I'm counting the final result of coding, not all the lines that write and replace/erase. I also program in C++. I don't know whether or not ASP .NET just requires many many many lines of code, but 1500 seems like way too much coding, way too little planning.
-
What does the number of lines of code you write in a day have to do with anything? I mean I can type pretty fast so I know I could blow the doors off that 1500 but what would that mean? Is this a typing job? Why "lines of code", why not words per minute like a secretary?
Senseicads wrote:
since leaving uni.
Either you weren't listening in class or that University is worthless.
@Mike Lol in answer to your questions, prob not and definitely :D yeah I realise that number of lines isn't the be all and end all, and that quality is way more important than how many lines it has taken. I was just wanting an overall impression in the workload other asp.net developers have and what they on average produce. Call me a bit insecure but only been doing this job a couple of months, never done asp.net before and having to learn very much on the fly. Its very much a self-starter role and so having to learn it myself which, don't get me wrong is ace, however I don't have any real way as to gauge the progress I am making other than self analysis. When I first started I was spending 3/4 of my time looking things up and as time has gone on and I have picked up the language and what not I am getting quicker and was just hoping for an indication as to the amount of work you seasoned pro's produce on average. Cheers Ian P.S. for your information I went to De Montfort University in the UK :) -- modified at 14:52 Monday 18th June, 2007
-
On average? Maybe 100. Design, debugging, and optimization, when combined, lead to a big process, which means that even though I may initially write 500 lines, revising my code, learning about new things that I can do to reduce code while making the program run more efficiently take just as much time. That said, I'm counting the final result of coding, not all the lines that write and replace/erase. I also program in C++. I don't know whether or not ASP .NET just requires many many many lines of code, but 1500 seems like way too much coding, way too little planning.
Hmmm You have given me something to think on there. The job I am currently on is updating the companies support system from the paper based on to a web based on. So as a support call comes in instead of filling in a paper form (which they hardly ever did anyway as far as I can tell) they can enter it in as they are speaking to the customer, and be able to report on it afterwards of course. I was literally given the forms they use and told go computerise that. No specification for it or anything. And I am actually spending a lot of my time making changes to the app in response to "wistful" ideas that they have while they are working. Actually sounds a bit amateurish even to me as I am typing it. :-S lol. I tend to write a lot of pseudocode for what I want to do anyway, so as I am coding I will plan out what I am going to do for like the next problem etc so not a lot of my code gets thrown away, but it would have defo been easier with some kind of pre agreed specification. Will talk to my boss about that I think as I am about to start the reporting part of the app and they want it to function inline with the rest of the companies reporting apps, not unreasonable, however its all contained in nested vb dictionaries which I can't for the life of me see the reason for. Cheers Ian
-
@Mike Lol in answer to your questions, prob not and definitely :D yeah I realise that number of lines isn't the be all and end all, and that quality is way more important than how many lines it has taken. I was just wanting an overall impression in the workload other asp.net developers have and what they on average produce. Call me a bit insecure but only been doing this job a couple of months, never done asp.net before and having to learn very much on the fly. Its very much a self-starter role and so having to learn it myself which, don't get me wrong is ace, however I don't have any real way as to gauge the progress I am making other than self analysis. When I first started I was spending 3/4 of my time looking things up and as time has gone on and I have picked up the language and what not I am getting quicker and was just hoping for an indication as to the amount of work you seasoned pro's produce on average. Cheers Ian P.S. for your information I went to De Montfort University in the UK :) -- modified at 14:52 Monday 18th June, 2007
Senseicads wrote:
was just hoping for an indication as to the amount of work you seasoned pro's produce on average.
Well I can't speak to the amount of work I produce but during my career I have produced, in whole or in part, around 8 production products that have run upwards of 8 years before being deprecated, without a single change to the project, no down time no bugs. I have no idea how many lines of code I wrote per day when developing those systems and I doubt anyone cares.
-
Hi all, No not coke! :doh: I was just wondering on average how many lines of code a day you produce. I am pretty new to development and have been on my first asp.net job since leaving uni. I mean i clock off work in about 15 minutes and i reckon today i have written around 1500 lines of code. Not having anything previous to go on is this a normal amount? Do people write more? I mean I realise I am prob still a bit slow as I am still learning. I am just after an indication really :D Cheers Ian
-
Hi all, No not coke! :doh: I was just wondering on average how many lines of code a day you produce. I am pretty new to development and have been on my first asp.net job since leaving uni. I mean i clock off work in about 15 minutes and i reckon today i have written around 1500 lines of code. Not having anything previous to go on is this a normal amount? Do people write more? I mean I realise I am prob still a bit slow as I am still learning. I am just after an indication really :D Cheers Ian
Senseicads wrote:
No not coke!
Whew, I didn't want to answer that. ;) I do very few lines in a day, but experience has brought me to a point where most of my effort is focused on reducing duplication and determining code factoring. I spend much time reducing the potential number of lines.
-
@Mike Lol in answer to your questions, prob not and definitely :D yeah I realise that number of lines isn't the be all and end all, and that quality is way more important than how many lines it has taken. I was just wanting an overall impression in the workload other asp.net developers have and what they on average produce. Call me a bit insecure but only been doing this job a couple of months, never done asp.net before and having to learn very much on the fly. Its very much a self-starter role and so having to learn it myself which, don't get me wrong is ace, however I don't have any real way as to gauge the progress I am making other than self analysis. When I first started I was spending 3/4 of my time looking things up and as time has gone on and I have picked up the language and what not I am getting quicker and was just hoping for an indication as to the amount of work you seasoned pro's produce on average. Cheers Ian P.S. for your information I went to De Montfort University in the UK :) -- modified at 14:52 Monday 18th June, 2007
Senseicads wrote:
I am getting quicker and was just hoping for an indication as to the amount of work you seasoned pro's produce on average.
I guess towards the beginning of my carear I was doing about 1500 lines per day. Now it is variable. Sometimes I do none, sometime I do a couple of hundred. But, over time I've learned to do more with less. My code quality has increase, I'm able to refactor code better so I reuse code more frequently and so on. Also, I no longer write big horrible hard-to-debug lines like this:
this.GetWidget(obj1.Wibble, obj1.Wobble, obj2.FindId(blah)).Initialise();That would now look like this:string wibble = obj1.Wibble;
string wobble = obj2.Wobble;
int id = obj2.FindId(blah);
Widget widget = this.GetWidget(wibble, wobble, id);
widget.Initialise();
Upcoming events: * Glasgow: Mock Objects, SQL Server CLR Integration, Reporting Services, db4o, Dependency Injection with Spring ... * Reading: Developer Day 5 Never write for other people. Write for yourself, because you have a passion for it. -- Marc Clifton My website
-
Hmmm You have given me something to think on there. The job I am currently on is updating the companies support system from the paper based on to a web based on. So as a support call comes in instead of filling in a paper form (which they hardly ever did anyway as far as I can tell) they can enter it in as they are speaking to the customer, and be able to report on it afterwards of course. I was literally given the forms they use and told go computerise that. No specification for it or anything. And I am actually spending a lot of my time making changes to the app in response to "wistful" ideas that they have while they are working. Actually sounds a bit amateurish even to me as I am typing it. :-S lol. I tend to write a lot of pseudocode for what I want to do anyway, so as I am coding I will plan out what I am going to do for like the next problem etc so not a lot of my code gets thrown away, but it would have defo been easier with some kind of pre agreed specification. Will talk to my boss about that I think as I am about to start the reporting part of the app and they want it to function inline with the rest of the companies reporting apps, not unreasonable, however its all contained in nested vb dictionaries which I can't for the life of me see the reason for. Cheers Ian
The three dreaded words: "Go computerize that!". You know what the hardest part of the job is? Getting the customer to specify their needs in detail. You asked about how many lines of code people write every day, but what you really should ask (especially in the light of your project description) is: How do you make the (internal or external) customer submit FINAL specifications. I have worked several solo (in-house) dev-jobs, and after the first nose-dive into a pool full of gentle carress, I've never written a single line of code before I had the specs. You need to rework your game plan whenever the specs change, and you need a stable version before you can really take off. Other than this: There are several form management systems out there, which will allow your company to have all kinds of forms that people can fill out online, a report generator, statistics tools, etc bla bla. Have they been considered? Whatever, your descriptions sounds... well... very enterprisey! ;) Oh, and please do take everything I said with a grain of salt. It probably isn't half as bad as I have made it sounds :)
Cheers, Sebastian -- "If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
-
The three dreaded words: "Go computerize that!". You know what the hardest part of the job is? Getting the customer to specify their needs in detail. You asked about how many lines of code people write every day, but what you really should ask (especially in the light of your project description) is: How do you make the (internal or external) customer submit FINAL specifications. I have worked several solo (in-house) dev-jobs, and after the first nose-dive into a pool full of gentle carress, I've never written a single line of code before I had the specs. You need to rework your game plan whenever the specs change, and you need a stable version before you can really take off. Other than this: There are several form management systems out there, which will allow your company to have all kinds of forms that people can fill out online, a report generator, statistics tools, etc bla bla. Have they been considered? Whatever, your descriptions sounds... well... very enterprisey! ;) Oh, and please do take everything I said with a grain of salt. It probably isn't half as bad as I have made it sounds :)
Cheers, Sebastian -- "If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
Thanks Sebastian, I have almost finished it now anyway. I have rolled out the forms and I am just producing the reporting tool, which I don't mind saying has been a bit of a nightmare! :D Doing the drilling down part of the reports now which I am hoping will be easier than the previous stuff! Never is tho is it? Specification wise, it has definitly been a lesson learnt! There have been mix ups galore and ideas changed on an almost daily basis with it. I get told one thing roll it out and then they decide that they wouldn't use it that way, but if it did it another way it would be an improvement...very frustrating. I think because it is an internal app they just thought they could wing it, it has been a really good learning curve for me tho, I only started a couple of months ago and had no asp.net before I started here and I have been pretty much left on my own to learn it which I am glad about, as I hate pointless courses where they helloworld you and chuck you out the door! Went on a powerbuilder one like that! lol Cheers Ian
-
Hi all, No not coke! :doh: I was just wondering on average how many lines of code a day you produce. I am pretty new to development and have been on my first asp.net job since leaving uni. I mean i clock off work in about 15 minutes and i reckon today i have written around 1500 lines of code. Not having anything previous to go on is this a normal amount? Do people write more? I mean I realise I am prob still a bit slow as I am still learning. I am just after an indication really :D Cheers Ian
No idea a day, better to go off project, But then it depends on the project, If you want a measure of work then go off the number of bug reports sent back by QA or Client (Yes low is better) Because I might one day do 1000 lines of pure brilliance :rolleyes: followed by one line that results in a function getting the wrong value and the system going in a nose dive along with my career. If it’s a website then someone loses there details due to sequel injection my boss gets fined or locked up and his wife and kids kill me on the way to work. Quality is better than quantity :)