oregondan
Joined 12 years ago
Joined 12 years ago
At a previous job, a coworker presented a compelling argument for removing "whitelist" and "blacklist" terminology from our codebases / jargon. Even though the etymologies of the words don't describe them as being based on race / racial judgments, their first recorded usages were in the 16th-17th centuries, when mass enslavement was in full swing. Setting aside the historical context, they also help reenforce the idea of "white is good, black is bad" [0].
At that job we moved to terms like excludeList, allowList, denyList, etc.
Fortunately, there's SymbolHound [0], which is designed for just that! Check it out
EDIT: As always, Wikipedia comes through [1]. There were species of different sizes, with tree sloths always being smaller than ground sloths [2], the giant of the article
[1] https://en.wikipedia.org/wiki/Sloth#Evolution [2] https://en.wikipedia.org/wiki/Ground_sloth
heh
[1] https://www.amazon.com/Universal-History-Destruction-Books-M...
> Although actual harvests were reduced, local officials, under tremendous pressure from central authorities to report record harvests in response to the innovations, competed with each other to announce increasingly exaggerated results. These were used as a basis for determining the amount of grain to be taken by the State to supply the towns and cities, and to export. This left barely enough for the peasants, and in some areas, starvation set in. A 1959 drought and flooding from the Yellow River in the same year also contributed to famine.
> During 1958–1960 China continued to be a substantial net exporter of grain, despite the widespread famine experienced in the countryside, as Mao sought to maintain face and convince the outside world of the success of his plans.
javascript:window.location.href='https://m.facebook.com/l.php?u='+encodeURIComponent(window.location.href);This seems like a road that only leads to technical debt brought on by people who, as you say, know nothing about the code they're working on. Why would you feel that's acceptable to a company?
Fortunately software development (often) has little direct impact on matters of life or death, but can you imagine an architect or construction worker who successfully cheated their way through school being brought on and having zero idea of how to weld, or how to predict the weak points in a structure?
Also, I'd argue that using frameworks is different than 'not writing code,' though I do agree that the JS community has become framework-obsessed...
:( this guy...
My internal map of Italy isn't very good, but given the 'size' of the populations that must speak or have spoken these dialects, I'd guess there was a dialect specific to Sicily.
[1] https://en.wikipedia.org/wiki/Judaeo-Spanish [2] https://en.wikipedia.org/wiki/Judeo-Italian_languages#Dialec...