The most important thing is comprehension. If something is too long and the length makes it less readable then it is too long.
But if having 3-4 files open at the same time makes it harder for you to comprehend a single file because you can't get the full picture, that's on you.
That's... Not... Why...
Do you honestly not understand how having 30-40 years of economic advantage and growth over nearly every country in the world has allowed America to spread it's culture via brand new technologies (TV music and movies) in a way no other country has ever done before with little to no opposition? Is it really that hard to understand? It has taken most of the rest of the world multiple generations to catch up... And those generations entire cultural upbringing was their native culture and America.
Gen Z is the first generation where widespread availability of non-american culture is available...
America spent the last 70 years exporting two things: American culture and violence...
I understand the concern, but readability and comprehension are way more important than line length. If the length impairs readability, it's too long. Explicitly limits are terrible. Guidelines, fine.
Ultimately, you do you. I still think your crazy and I think your argument is poor.
Interesting. I wonder how much you used? I can imagine that a 1/4 tsp of the salt has enough magnesium carbonate to be effective... But I don't know how much is in it (otherwise it should be on the label since magnesium does have an rda)
I too used to think generics were superior until I learned parameter packs, type traits and SFINAE.
I, too, remember the days before ultra high definition ultra wide monitors.
I thought this argument was bogus in the 90s on a 21" CRT and the argument has gotten even less valid since then. There are so many solutions to these problems that increase productivity for paltry sums of money it's insane to me that companies don't immediately purchase these for all developers.
I used to be this way about c++ too... But c++17/22 are not the same language as it was 10 years ago.. And it definitely isn't the language most firmware guys get to use it as.
There is some truly wild shit in the templating system.
Not that you are wrong, but it was super weird to read that "python can be emulated in c".
I mean yes... But...
Your mistake was giving them an answer instead of asking how the scale was setup before giving them a number. Psychologically, by answering first your established that the question was valid as presented and it anchored their expectations as the ones you had to live up to. By questioning it you get to anchor your response to a different point.
Sometimes questions like this can be used to see how effective a person will be in certain lead roles. Recognizing, explaining and disambiguating the trap question is a valuable lead skill in some roles. Not all mind you... And maybe not ones most people would want.
But most likely you dodged a bullet.
I agree only when your job function is specifically geared around those tools... Otherwise high quality guis are more valuable.
Just because I can do everything in gdb that I can do in visual studio doesn't mean 99% of most debugging tasks isn't easier and faster in visual studio. Now if my job was specifically aimed at debugging/reverse engineering there are certain things that gdb does better on the CLI... But for most software devs... CLI gdb isn't valuable.
Self documenting code is infinitely more valuable than comments because then code spreads with it's use, whereas the comments stay behind.
I got roasted at my company when I first joined because my naming conventions are a little extra. That lasted for about 2 months before people started to see the difference in legibility as the code started to change.
One of the things I tell my juniors is, "this isn't the 80s. There isn't an 80 character line limit. The computer doesn't benefit from your short variable names. I should be able to read most lines of code as a single non-compound sentence in English with only minor tweaks and the English sentence should be what is happening in most of those lines of code."
I think it's more correct to say that we don't know how to travel in the other direction on the time axis. It could also simply be our perception of time only works unidirectionally.
From a mathematics point of view, nothing is preventing going backwards in time... We simply don't perceive time that way.
Practically, this does nothing for us.