Hacker News Reader

So they created selection pressure to maximize LOC created? Intentionally?

I can just see the remaining devs frantically running everything through code obfuscation tools. Double the size of everything! That’ll look great!

View on HN

From what I understand, they used some past period's (-30 days to -60 days?) results so that people could not optimize for the stated goal. They might in the future, if they believe that remains the number 1 metric, but who knows.

Well, if you were one of the survivors there today, how would you be thinking about LOC?

I'd ignore it unless it was given out as an official metric of success. People would optimize for it, making it useless as an indicator, and I'm pretty sure Musk and his team are smart enough to have considered that.

You can commit codes and set the time/data to which you want to be in. LOC is dump in all ways.

Guess I’ll just add a couple NPM packages. Easy 6k LOC.

Only if you cut n’ paste them.

May, just remove node_modules from .gitignore. Boom, massive productivity.

You could commit node_modules

Reply on news.ycombinator.com