I work in a research environment with a lot of hacking around and very little programming. I estimate I write around 100 lines a week on proof of concept stuff that usually gets thrown out once we find a new approach. After 2 years of this I'm getting the itch to write a large amount of code per week. I wish I could pump out a easy 100-200 lines a day on some product. Switching to Google soon so google people please comment and tell me what it's like for you. Huawei TC 105 Google TC 280 3 YOE
What's Google TC and level and location?
Regularly writing many hundreds of lines likely only happens at super early stage startups..
Or stable nerdy manager-less company. Less stress than start-up but might pay you less.
Writing a lot every day means you're not optimizing for maintainability. Don't be that person. Write shit as small and as easy to maintain as possible. Go out of your way to do it.
Who counts their weekly lines of code? That's weird
Just a guess. The difference between 100 --> 500 -> 1000 is pretty huge imo
If you’re looking to churn out tons of code be prepared for disappointment. Google has a strong focus on consistency/style, code ownership and testing and therefore can be a lot slower than many companies.
Can't be slower than my current position lol but yeah I'm not expecting google to be crazy fast either
Damn. Just realized the amount I am writing a week is quite normal. I never realized how much I used to write at my last job which was a start up
Can you elaborate on how much you wrote at the startup? What size was the startup? I might want to experience that atleast once
Goal is to be negative. Hit it most weeks.
Why's that the goal lol
Less LOC = possibly more efficient / elegant code?
Same here, on a good week minus few hundred. That’s production code. Why? Because code is liability. If you can refactor or make your procedural code more functional there is a smaller code base to screw up. There are exceptions to this. I generate a few dozen lines of scripts to assist me with what I do regularly per week. And since we are devops I write more and better automations. My automated test suite is another place where code is growing. In several critical places I have 100:1 lines of test:production code
Yeah design and testing is a huge part. Coding is mostly the easy part. You just hack it in real quick.
I guess I ment lines edited, not just added
Normal output is 100 LoC/wk of high-quality (defined as cannot be meaningfully improved without investing unreasonable effort, by a competent IC) code. Best ICs can do 1,000/wk sustained high quality. Hence the term 10x engineer lol
Ughhh. Also TC or
Lmao added