How many hours for writing assembler code
‎11-07-2006
12:35 PM
2,915 Views

Truk
Contributor I
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I develope allway complete units that means designe incl. housing (moulding form), PCB-layout etc. Therefore I write only a part of the time source code in assembler and I am not a "fast" software writer. So I have allways discussions with my clients about the hours I invoice.
Therefore I would like to know how many good documented and testet software code a good software engineer could write in assembler with optimization for short code.
e.g.
xx lines of source code / hour
yy kbyte of machine code / hour
I wonder what figures you could carry together!
regards
Truk
3 Replies
‎11-07-2006
04:01 PM
1,564 Views

UcTechnoGeek
Contributor II
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your question is confusing.
Are you asking how many average lines of code you can write per hour?
Personally, I spend as much time debugging, modifying and perfecting the code than I do writing "lines of code".
uCTechnoGeek
‎11-07-2006
04:33 PM
1,564 Views

Truk
Contributor I
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi uCTechnoGeek ,
I meen final code, that means at time the project ist finalised.
Take all the time you need for writing debugging, modifying, optimizing by time or code...... and devide it by the lines in the final version or the machine code.
regards,
Truk
‎11-07-2006
06:55 PM
1,564 Views

alex_spotw
Contributor III
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HI:
The best numbers are the ones you collect from your own experience.
From my experience in C programming (not assembly) I can let you know that my numbers are in the 15-20 lines per hour.
I guess assembly might take longer to write/debug than C.
Regards,
Alex
The best numbers are the ones you collect from your own experience.
From my experience in C programming (not assembly) I can let you know that my numbers are in the 15-20 lines per hour.
I guess assembly might take longer to write/debug than C.
Regards,
Alex
