Therefore, please leave a quick reply saying how many lines of code average that you can write per day. It is an interesting question though as it is a profession where measuring productivity is very difficult. When I wrote code regularly for a few years it took me a long time to get up to lines per day. I think overall I probably averaged a little more in my hay day, but if pretty darn fast in my opinion….
The lower the number of coded lines you do to achieve your objective each day, the better coder you are with machine language as the exception. I had a look at the source code, took a copy and by implementing functions, structures and removing shitloads of repeated code it was down to about !!
The first is not only considerably more efficient count will run each time on the array in example 2 but it looks a great deal better. Some days I have produced 2, or 3, lines if I am writing up some crazy classes. Some days I will probably produce about lines of code.
Really depends ona lot of things and should not be used as a measure of skill or quality. Studies have shown that the average programmer in a production environment puts out about 10 lines of code per day. Her code floated through unit and integration test. I found it as hard to believe as anybody. She had no idea she was doing so much better. She thought she was barely making it, and trying hard to keep up with everyone else.
Thanks for sharing Brian, your story is even more interesting taking account that the super-hero-coder is an humble woman. We all know that there is seconds in an hour. So your coder is basically typing as fast as leaving a finger on a key repeat — 8h20min straight. Without switching windows neither compiling anything, just leave the finger pressed on a key. Sorry for not saying so. It was an assembler shop. So lines are shorter to type. Faster than me for sure. She sat across a divider from me and was scary focused.
And very tense. They were Probably 10 average. Like I said, they thought their system had to be broken. It seemed impossible. She had really clean, nice code with excellent comments too.
Short, to the point and clear. Yes, Patrick. Women were critical to computing at the start. Women defined languages. I worked in a group once where I was one of 2 men in the group of 9. The manager was a woman, and her boss was a woman and so was her bosses boss a woman. I only counted code in products shipped to the user. All the code is cross-platform for Windows and Mac, which makes it more time consuming to write, test and document.
Programming is only one of the things I do. As a one-man-band I also do marketing, sales, QA, support, documentation, newsletters, admin and nearly everything else. I have also done some consulting and training not directly related to my products in the last 12 years. Share this: Tweet. Share on Tumblr. Like this: Like Loading Follow Following. Successful Software Join 2, other followers. Sign me up. Second, I'm not sure why we would measure this. In my busiest year, I've written maybe 10k LOC across everything: prototypes, deployed code, patches, etc.
So the question then becomes: is 10k LOC a lot? I've honestly spent days coming up with a single sentence or equation, so I'm not sure why I care. The harder parts take a lot more time and effort and have worse efficiency by simple rate metrics. With that in mind, my lines of could not be counted. Yeah, some weird statements in this thread. Early on in a project I probably write s in a day, but as time goes on it decreases rapidly and the average will be quite low.
That's , LOC in a year. I think it really depends. We have 1M split about evenly between 3 devs. However, at least in my case, most of that code will be written in probably 2 months of the year. Before that code is written, there's at least a month of design work, and afterwards that's a ton of debugging, testing, change requests etc. In my case it was a splurge doing a rewrite for a component where i new precisely where i wanted to be and i had tools helping me create code pretty much as fast as my mind wanted to put it down.
This component is used by many others. You write a million lines of new code a year, every year? I've worked on a couple of 1M sized codebases, but they'd all taken a few years at least to get to that size. In fact, anything I've worked with that's over 10k in size, has taken well over a man year and a calendar year to achieve that size. I have a strong feeling to kneel and worship So you guys do a minimum of LOC per workday?
Honestly that sounds high, especially when you take design, testing, and integration into account. I can't imagine hitting lines per day.
The question is meaningless. I write hundreds of lines of code a day, but the majority of it is either writing generic CRUD with the occasional tricky data manipulation, or rewriting dodgy old ASP code into dodgy new. NET code. My brother writes code to handle the vehicle AI in simulation software.
I'm sure I write 10 times the amount of code he does, but I'm also sure I'm not working 10 times as hard more likely the other way around. The of lines is otally irrelevant and fairly uninteresting.
I didn't start this thread to reignite the tools discussion. I was more interested in hearing how many lines of code the pro devs in the symposium kick out per day.
So in my environment - lines per day is about right. Some days it could be , others zero, other when refactoring is considered.
I feel like I wrote about 10 lines of code today! So painful. It can be tough going when you inherit code with no documentation, no unit tests etc.
At least by tomorrow I'll be able to give my boss the answer to one of the questions he's been looking for though. I guess at the end of the day all that matters is what you achieve not how many lines of code you write.
I can only dream or have nightmares!! I've spent many days writing a few lines of code to fix something in the thousand lines that someone else did in a day. LOC is meaningless.
I'm writing some cool lisp code these days. I can knock out lines per day of shit like foo. But it is a lot of code.
0コメント