Yeah, I expected such bs explanation. Naval Ravikant at nav.al also mentions in a related podcast that counting bits per second for human cognition is just bs.

Yeah, I expected such bs explanation. Naval Ravikant at nav.al also mentions in a related podcast that counting bits per second for human cognition is just bs. But nevermind. You just do the following: you are an actual developer, go code while simultaneously counting every second and how many bits per second you handle, afterwards provide estimates of quality of this code. In this option there is no assuming that we can use the full input bandwidth. I'd add the following to the 1) of the formulation: how many actual developers would just believe (unable to actually calculate by themselves) the above mentioned 11 mln bits per second AND what code quality/contribution to CS do they produce.