Re:How we rolled out one of the largest Python 3 migrations
by panic on Tuesday September 25, 2018 @05:46PM
(#18070781)
The size of a codebase is less about its function and more about the number of people adding code to it.
[ Parent
| on HN ]
Re:How we rolled out one of the largest Python 3 migrations
by flukus on Tuesday September 25, 2018 @08:33PM
(#18071704)
In turn this becomes the number of people required to maintain a codebase.
Re:How we rolled out one of the largest Python 3 migrations
by thijsvandien on Tuesday September 25, 2018 @06:39PM
(#18071155)
What would you consider the main cause(s) of that?
Re:How we rolled out one of the largest Python 3 migrations
by panic on Tuesday September 25, 2018 @07:23PM
(#18071407)
The job of a programmer is to write code, so that’s what they do. I doubt there are very many people at Dropbox whose job it is to remove code!
Re:How we rolled out one of the largest Python 3 migrations
by maltalex on Tuesday September 25, 2018 @07:39PM
(#18071488)
That’s an extremely narrow definition of a programmer’s job.
I think that in terms of lines if code, my contribution to many projects was net negative.
Re:How we rolled out one of the largest Python 3 migrations
by icebraining on Wednesday September 26, 2018 @04:00PM
(#18079684)
The classic story: https://www.folklore.org/StoryView.py?story=Negative_2000_Li...
Re:How we rolled out one of the largest Python 3 migrations
by MisterOctober on Tuesday September 25, 2018 @08:54PM
(#18071808)
I dunno - refactoring often involves removal of a fair bit of code