3 ms·
Are those really the figures he cited? Working only weekdays, and only eight hours per day, that comes out to five lines of production code per hour. Even with
by kibwen 15y ago
Are those really the figures he cited? Working only weekdays, and only eight hours per day, that comes out to five lines of production code per hour. Even with the overhead of testing and occasional widespread refactoring, that seems incredibly low.
In any case, Braid was just okay. The level where the flow of time depended on the direction that your character was traveling was great, but the rest of the game was forgettable. There was about as much gameplay/story integration as a Final Fantasy game, and the story itself was mostly overwrought. But considering that the game cost me one dollar to purchase, I'd say it was worth it. :)
- mjmahone 15y agoAs an intern at a tech company (not a gaming company, but still) I don't know anyone there who was able to write more than 5 lines of code/hour consistently. Maybe 10 if they absolutely knew all the ins and outs of the codebase. A good chunk of that was because a LOT of the time you spent was finding where the code was, deciding exactly which lines to change, reviewing others' code, etc. Making the wrong color choice could cost someone else ~30 minutes of time to potentially fix 1 line of css.
- regularfry 15y ago> Are those really the figures he cited? Working only weekdays, and only eight hours per day, that comes out to five lines of production code per hour. Even with the overhead of testing and occasional widespread refactoring, that seems incredibly low. Fred Brooks cited 10-12 lines of code per day, constant across languages and projects he surveyed. As far as I know, it's not been shown to have changed since then.