3 ms·
> On the other hand, writing code that the most junior in your team can understand leads to mediocre code. Disagree on a couple levels. First, while the overal
by jjav 1y ago
> On the other hand, writing code that the most junior in your team can understand leads to mediocre code.
Disagree on a couple levels. First, while the overall architecture of the system might be complex, there shouldn't be any one single function that isn't readily readable by a junior new hire. Complexity is in the system, there should be no complexity in small sections of code.
Second, the ultimate level of mastery is to be able to build simplicity. Any newbie can write a convoluted mess that nobody can understand.
- sdeframond 1y agoOK, I'll give an example. Every so often I encounter some dev that is not familiar with SQL. So instead of writing a single SQL and relatively "simple" SQL request that does the job db-side (say with a few joins and coalesce but no sub-query), they write several requests then process the result in python. The argument ? "SQL is complicated, it is simpler to just do it in Python." Is it though ? I guess it depends on the request and the exact processing we are talking about but in many cases I suspect it is because that person is not familiar with SQL. What "simple" means is not so simple to define. Sometimes it means "easy for me".