Conversation

Notices

1. Embed this notice
   Jason Gorman (jasongorman@mastodon.cloud)'s status on Friday, 26-May-2023 18:05:50 JST Jason Gorman

   @daedalus The person to speak to is Robert C. Martin. It's from Clean Code. I've personally recorded programming sessions (not just mine) and noticed just how much time nothing happens on the screen during "coding" sessions. Various sources (e.g., The Mythical Man- Month, and this one https://blog.ndepend.com/mythical-man-month-10-lines-per-developer-day/) estimate average dev lines of code per day at between 10 - 100. Let's call it 55 LOC/day. Average words in a LOC: ~5. 275 words per day. At 30 wpm, < 10 mins of typing code/day.

   • clacke likes this.
   • Embed this notice
     clacke (clacke@libranet.de)'s status on Friday, 26-May-2023 18:11:25 JST clacke

     in reply to

     • sabik

     @sabik @daedalus @jasongorman First time I hear about COCOMO. Worth looking into today?

     www.interviewbit.com/blog/coco…

   • Embed this notice
     sabik (sabik@rants.au)'s status on Friday, 26-May-2023 18:11:26 JST sabik

     in reply to

     @jasongorman @daedalus
     Lot less than 55 LoC/day if you go by COCOMO

     (I think COCOMO works out to something like 10-20 LoC/day? It's been a while since I last played with the formulas...)

   • Embed this notice
     Jamey Sharp (jamey@toot.cat)'s status on Sunday, 28-May-2023 16:00:31 JST Jamey Sharp

     in reply to

     • clacke
     • sabik

     @clacke @daedalus @jasongorman @sabik If you've ever run the old https://dwheeler.com/sloccount/ tool you've seen estimates based on the COCOMO model. It's fun to come up with numbers estimating how many person-years your code might take to construct from scratch and how much those engineers might get paid for that time, but I don't know that those numbers have any useful relationship with reality…

     clacke likes this.
   • Embed this notice
     clacke (clacke@libranet.de)'s status on Sunday, 28-May-2023 16:02:13 JST clacke

     in reply to

     • sabik
     • Jamey Sharp

     @jamey Aha, I don't know that tool but I know some analysis websites that operate on open source codebases provide an estimate of how much the code would cost to reproduce. I guess that's a similar model.

     @daedalus @sabik @jasongorman

   • Embed this notice
     sabik (sabik@rants.au)'s status on Sunday, 28-May-2023 16:27:06 JST sabik

     in reply to

     • clacke
     • Jamey Sharp

     @clacke @jamey @daedalus @jasongorman
     Yeah, there's only really the one model

     clacke likes this.