4 ms·

Yes, remove a 0 to that 40. Did the maths wrong. Fixed.

• Deimorz 10y ago
  Averaging 680 lines every single day is still much, much too high.
  • glandium 10y ago
    I'm sure it's easy to reach, if you inline all your function calls.
• dietrichepp 10y ago
  4M is still high. In order to maintain 680 lines per day on average, you have to sacrifice a lot. Remember that code is not intrinsically valuable. The highest I've hit is 3,500 over a three-day weekend, and the experience was awful. I spent a week recovering.
  • eropple 10y ago
    Yup. My estimate of my own, over the last twenty-one years, is somewhere in the neighborhood of a million. And that's in delivering projects for a lot of customers.
• sqeaky 10y ago
  First impressions matter. When people are talking about moving fast an breaking things it does not mean to move so fast as to skip quality. They mean they are delivering new goods and old services can be torn down (or something similar enough). A half uploaded you could have taken 15 minutes to proofread is a clear indication that you are more focused with quantity than results. You then expect us to see you as automatically deserving of a high end tech job. Is it possible that you did something, anything to give anything less than a perfect first impression in interviews? If you must code take some of your many lines of code and put them on github and use that as portfolio. This is a strong way to make a first impression. Don't tell people you wrote a bunch of code, show them how awesome your code is. If I were you I try to land a job at company in your town writing software. Even if it is one of those ever so hated insurance company jobs. You will be held accountable and forced to deliver. You will earn money. You will get at least some perspective you haven't had yet. Then you can try again at doing whatever you like with a little cash in your pocket and no one breathing down your neck.