-2000 lines of code. https://www.folklore.org/StoryView.py?project=Macintosh&stor...
You've only added two lines – why did that take two days?
41–50 of 522 posts
Re: You've only added two lines – why did that take two days?
#42The assumption that asking for more information to recreate the bug is a lazy tactic to get out of the bug fix is also a terrible assumption and discredited the opinion IMO. Often times asking for more information can speed things up and lead to a quicker resolution.
In my experience sometimes this is true, sometimes it is not. In some cases when asking for more information it takes much longer. Some of the reasons:
After asking the question I get a meeting schedules where design by committee happens. The story or bug your working on gets completely redesigned. Sometimes in an illogical way. Requiring more questions.
When working remote, like most of us right now, now I will end up waiting for a long time to get a response. I then must start some other story/task/bug. Trying to context switch multiple complex tasks at some point your productivity slows down.
I have also received criticism for asking when I could figure it out myself even when figuring it out may have taken hours more time then just asking a yes/no question.
Re: You've only added two lines – why did that take two days?
#43Earlier quoted context omitted.
I know someone that worked at some skeezy company in Menlo Park that got passed up for a raise after spending months navigating the bureaucracy to save the company millions on their operating costs because they didn't write enough code. This was in the last four years. Edit: And they quit right afterwards.
It’s better to find ways to make more money than to save it. There’s a floor but no ceiling in much of what we do.
Thanks. This comment blew my mind. This perspective is so far on the other side of things that I never considered it.
Re: You've only added two lines – why did that take two days?
#44One time I spent 3-4 months working on a project that amounted to adding 11 lines of code to a config file on kubernetes. Tbh, a lot of it was bad communication, but it was also because I wrote and rewrote so much of the same code.
Re: You've only added two lines – why did that take two days?
#45You've only rendered one two-word verdict -- why did that take five days of deliberation? You had twelve people working on it!
Re: You've only added two lines – why did that take two days?
#46If someone is measuring productivity in code, based on the amount of lines of code written, then they have never written code. Anyone with a tiny understanding of how programming works would totally get why something so small could take so long.
Re: You've only added two lines – why did that take two days?
#47Actually this is one of the upsides of web development: Since every line contributes to the file size of your software and therefore to the loading time there is a motivation for keeping the code base small.
Sadly, there are many projects out there which obviously failed to reach this target at some point.
Re: You've only added two lines – why did that take two days?
#48Conclusions:
1. Picking a good manager is very important!
2. Communicating with your manager is very important!
Re: You've only added two lines – why did that take two days?
#49Do people actually have fights like this with management at their companies? Not trying to knock the author, but I'm just surprised anyone would actually hear this kind of comment in 2020. I'd think by now any and all metrics tying lines of code to productivity would be long dead.
[deleted]
Re: You've only added two lines – why did that take two days?
#50Nobody should manage programmers who is not themselves a very experienced programmer. Otherwise, you are in Dilbert Country.