> I'm sorry, but that sounds like the juvenile fantasy of someone who is still in their programming puberty.
For larger applications what PeCaN was saying still mostly holds true.
I work on large (1-10 million loc systems) enterprise java code bases and write some side projects in k as a hobby.
I can get the equivalent of around 30-40 java class files on screen at once with k.
Even on poorly written enterprise code bases code is clustered and your “working set” of code files is quite small and is not strewn all over the codebase.
Of course you still need to understand the core system abstractions + base platform + common library code.
...and in idiomatic K code, you apparently still need to constantly wonder what 'a' or 'X' means in your current context, with likely 5 different usages on your screen at once.
If you see many different usages of the same identifier then it’s probably a common construct/pattern you aren’t aware of.
In the same way as ‘i’ tends to be used as the current array index in a for loop - but devs don’t get confused by seeing ‘i’ used in lots of different loops.
Or kotlin devs seeing ‘it’ or class based language devs seeing ‘this’.
So you claim it never happens that two people working on different parts of the code decide to use the same identifier for completely unrelated things?
Seems to me that is bound to happen pretty frequently when the expectation is to use only one- and two-letter identifiers.
For larger applications what PeCaN was saying still mostly holds true.
I work on large (1-10 million loc systems) enterprise java code bases and write some side projects in k as a hobby.
I can get the equivalent of around 30-40 java class files on screen at once with k.
Even on poorly written enterprise code bases code is clustered and your “working set” of code files is quite small and is not strewn all over the codebase.
Of course you still need to understand the core system abstractions + base platform + common library code.