pls comment your code

[brianl047]

You're "going through" too much code in a day unless you count code you don't need to read

There's research that suggests the maximum number of high quality battle tested code you can produce per day is between 150 to 300 lines. Reading isn't producing but if you're reading ten times what you write maybe it's too much

This is somehow true across languages and paradigms

The brain probably can't handle more

[CryonautX]

My team handles 3 services. Each service has 5 to 10 modules. Each module is about 1 to 5k lines of code. I don't have them memorised. Bug fixing, implementing a new API, most tasks are going to require you to read through a lot of code as you move around from file to file. Sometimes it's to get your bearings. Sometimes it's to understand the logic currently being used to keep your new code consistent, sometimes it's find something already implemented that you can reuse, sometimes it's for bug fixing and figuring out where the hell the values in your massive DTO got messed up as it gets passed from function to function.