3 ms·
Why is the years of development or the number of commits relevant? It feels like there is an unstated incentive at play here? Are you trying to get hired?
by cinntaile 4y ago
Why is the years of development or the number of commits relevant? It feels like there is an unstated incentive at play here? Are you trying to get hired?
- xnx 4y agoI think it's an attempt to convey the level of effort involved? Seems like an even worse measure than lines of code.
- contravariant 4y agoIt's the kind of metric I'd use if I wanted to convey how much time was wasted on something.
- deleted 4y ago[deleted]
- leoloso 4y ago> I think it's an attempt to convey the level of effort involved Exactly this. Also it's a way to point out that I took no shortcuts. When you have a deadline with a client, you start dropping features out, and adding @todos to fix something sometime in the future. Since this is my own project, I took the decision to do it well, at the cost of needing extra time and effort (eg: adding hundreds of tests, making services injectable and reusable, etc). The payoff will come in the future as the codebase proves to be more sustainable, and I require drastically less effort to maintain it.