I’m a very productive very lazy developer. In younger years I used to stay up for three days straight programming or working out some infrastructure crisis (cat

I’m a very productive very lazy developer. In younger years I used to stay up for three days straight programming or working out some infrastructure crisis (catching occasional cat naps on server room floors, meow.) You must pace yourself. Dividing work by cognitive load helps. Intellectual work in the early hours, casual work in between, and finally “talk to people time.” What you will eventually find, is that thought productivity ratios are non-linear. You will become a superior problem solver with the realization that more work does not mean proportionally more productivity. Quite the opposite. Lazy programmer predictive modeling will foresee purpose and economy, eventually finding the least amount of work necessary for producing the most necessary results. Our strengths and weaknesses are all different. I tend to “see the solution“ in the first fifteen minutes thinking about a problem, even when the technical implementation takes weeks or months of implementation drudgery. Don’t burn yourself out. Let more work happen as background processing, practice conservation of intellectual time. Do not over caffeinate. Take exercise breaks (yes you nerds.) Eat properly. TBH, going through ten years of grind may well be intrinsically necessary in cultivating strategic foresight. The only thing wrong with you are your expectations.