# lines codes. no of pomodoros/day.

"Measuring programming progress by lines of code is like measuring aircraft building progress by weight."

which in reality, is a pretty effective way to do it. Really. (speaking of airplanes)

...where the fewer lines are written to achieve a well-working solution, the better.

Perhaps, but measuring productivity by lines of code is a problem only if there are incentives tied to the metric: if you have a system with other incentives and have two people working in the same language, lines of code is a perfectly reasonable way to judge the productivity of a programmer.

Nope. Things can be solved any number of ways. Often a simple solution with minor changes is better than a quicky designed bandaid with 10 times the LOC

It can be a metric, but it doesn't indicate productivity by itself. It's hard to use even correlated to other metrics, but loses its value if compared out of context and without knowing the code quality

that shouldn't change day by day ?

Ofcourse noone an help you if you are trying to cheat your own system.

If your goal units are newline characters or alarm bells ringing, possibly.

This is ridiculous. More LoC != productivity. If anything, you make your future teammate's life miserable, when they inherit your technical debt.