2,503 karma · joined July 19, 2013
this is just neuroticism, and isn't really related to the ivys. it's a very common human dynamic, just follow etiquette when crossing class boundaries. the fact that the author makes it into the particular plight of the ivy grad (oh if only they had kept us humble, woe me!) speaks more to his own insecurities than to anything relating to the nature of elite education.
not to say AI-tools do not contribute, they lower the bar of entry to the profession after all, but any C-suite/hiring manager is much more arbitrating labor expense than AI-subscriptions.
they dont care because nobody has a real gut feel affinity for computer programmers or the work, the sort of feeling that is required to animate somebody to action. it's never been a profession with any esteem, and the field never professionalized in the past 60 years, which is a shame, because we now see the outcome.
Pass objects by ref, I said that to underscore its better than create new objects. I get it, its the only way, but theyre still passed by ref.
Yes, [a,b,...rest] =... is restructuring and creates new object.
Named params create new objects, it's better to pass args individually, the ref creation under the hood is not comparibly impactful.
it's a good thing. pass objects by reference.
> Is there a behavior you think is unique to destructuring?
depending on exact syntax, will collect values in another array or object. it's often used as the mirror-pattern of using named variables, which allocates an object for each function call.
in isolation these are not inherently wrong, at scale they start to add up. and should not be used in tight loops.
> Zero-copy is the default, not the optimization:
the amount of fluffy mapping, destructuring, temp scope-creation, ... that is the norm now for JS/TS devs is excruciating. how did this become the norm? do it once it doesnt matter, but every single layer in the app doing this and things become jittery. you first take the hit at creation time, and then another time at GC. stop doing that! Pass references around to objects, not recreate them each time at some function boundary.
> Entity as pure identity.
Stop json.stringifiyng every thing! how many hashThing() implementations i have seen that are essentially Json.stringify. stop it!
> Cache locality by default.
a little less clear for web dev, much is missing in terms of primitives. but do think about it. if anything, it's good hygiene. fixed typed array does make sense, dont mix&match types in your array, ...
Save the web, think like a videogame dev!
generally, students from other departments are writing the code, but current day most archaeologists can work with ready-made packages (model builders etc..) now too.