That's probably what makes me uncomfortable with these mandated word changes.
I could argue the linguistics, and the racial connotations never occoured to me then and don't convince me now. But what really makes me uncomfortable is the feeling that I'm surrendering part of my soul to some larger conscience that could turn on me at a whim.
Grandfather. If you look at the website, it explains in detail:
A “grandfather” clause, “grandfather” policy or “grandfathering” in IT s a provision in which an old rule continues to apply to some existing situations while a new rule will apply to all future cases. Those exempt from the new rule are said to have grandfather rights, acquired rights, or to have been grandfathered in.
Why it’s problematic:
“Grandfathering” or “grandfather clause” was used as a way to exempt some people from a change because of conditions that existed before the change (e.g., we’ve grandfathered some users on an unlimited data plan.”) “Grandfather clause” originated in the American South in the 1890s as a way to defy the 15th Amendment and prevent black Americans from voting.
> The cakewalk was a pre-Civil War dance performed by enslaved people, and the winner of which would be given a cake. This is the original source for the phrases “takes the cake” and “cakewalk.” Because of this history, this word and phrase should be avoided.
> Brown bags trace back to the “brown paper bag test,” which was traditionally used to judge skin color by certain African-American sororities and fraternities. References to a “brown bag” when we are really referencing a get-together over lunch surfaces an ugly period of American history that can alienate and offend people.
> (no can do) What might seem like a folksy, abbreviated version of “I can’t do it” is actually an imitation of Chinese Pidgin English. The phrase dates from the mid-nineteenth to early-twentieth centuries, an era when Western attitudes towards the Chinese were markedly racist.
> Using the word “pow wow” is cultural misappropriation, and ultimately racist.
> Referring to something as your spirit animal is cultural appropriation.
You have the word "master". It has at least two meanings in standard English and an additional one for technical jargon. Let's call these concepts owner/slave, expert/apprentice, and primary/secondary.
Even though owner/slave and primary/secondary are different concepts, the technical jargon makes the unfortunate reference the owner/slave meaning because of the use of the word "slave". It's difficult to defense the use of master/slave in this context.
The master in the expert/apprentice concept could be called leader, expert, or teacher and no one would have a problem with that.
This distinction is where people start getting upset.
I'd argue most technical people didn't even give a second thought to master/slave and for them they never considered it to be anything other than primary/secondary because owner/slave is no longer common use and hasn't been for a while. Besides, US Civil War was more than 150 years ago! Who gives a shit?
Well... people do because the effects of that war still affect our society and no one agrees on how to fix it. Removing problematic phrasing from our language as part of that makes sense. No one agrees on that either.
To know you shouldn't use these phrases, you need to know the context.
Therefore, by not using these words, you're reminded of the context. Any time somebody notices you substituting a phrase and they know why, they will be reminded of the context.
Like all self-censorship, it immerses the speaker in the truth while they trip overthemselves trying not to say that thing.
It's like saying, "Don't think about elephants." Now everybody is thinking about it.
I am black but not from the USA I'm from the Caribbean.
It's hilarious how people perceive those who look like me.
Like we are some hyper-sensitive, fragile babies who cannot understand nuance of speech.
It's even worse when some white Americans are afraid to joke around me or poke fun at me, because they don't want to punch down.
Meanwhile I feel more privileged than most white Americans. I speak 3 languages perfectly.
One favor a hiring manager did for me, was giving me a tougher interview than most other candidates. He made sure everyone knew I was hired because I'm good at my job, not because I'm a "diversity-hired to fill some quota".
When I first moved here, I saw myself as a nerdy kid, who liked computers and wanted to build and create stuff. I saw myself as a human being who happened to look a certain way. I saw white people or Asian people just the same.
Then I made the mistake of consuming "woke content" on reddit and Twitter and it affected me, after college those ideas limited me in ways I could only imagine.
I really hope people see me as a bright kid whose into computers not some oppressed victim.
By the way, racism and prejudice exists but they show up differently.
> Then I made the mistake of consuming "woke content" on reddit and Twitter and it affected me, after college those ideas limited me in ways I could only imagine.
The "woke content" just lumps everybody in one big pile, categorizes everyone in order to validate a theory:
After living here for 15 years, I have realized the main narrative of the "black experience" "what is means to be black" is very Anglo-US-centric.
In college, I met a Jamaican guy, the culture shock was just as intense as when I met that girl from mongolia. Totally different cultures and customs. But on paper, in the USA , Me and that Jamaican guy were just Black.
I had more in common with the White French exchange student than with the Black-American kid from Virginia.
To me: that black American kid and a white American kid were the same.
From an academical, political standpoint, Black has become synonymous with "African-American" Not just any "African-American", poor disenfranchised black Americans who are likely from the "ghetto". White means: some mean monster , who are controlling the world and are out to get everybody. So naturally I started to second guess how people acted around me.
Don't get me wrong racism is still alive and well I have experienced it in various forms:
* Prepaid for a meal at a fancy restaurant, the people before me just gave a name and grabbed their food, I was asked to show a receipt.
* Jogging in my neighborhood and having the police follow me around, almost like clockwork can't be a coincidence. (They became cool once they learned I lived there).
* Going out with my white coworkers in casual clothing vs going out with my siblings in casual clothing we have to dress extra fancy to get treated the same, otherwise we get poor service - The black guilt to tip extra at restaurants)
But: Most of the white people I've met were amazing, great people.
That mean guy, is probably a jerk to everyone and just happens to be white.
There needs to be a balance, raise awareness about issues of society, but don't go to the extreme.
In my language:
"The sky is blue, he is about to rain. I need to move my car otherwise she will get flooded"
I appreciate that you chimed in because it's a common perception.
But stopping the use of the master-slave metaphor in tech has nothing to do with assuming there are "hyper-sensitive, fragile babies who cannot understand nuance of speech" it has to do with real metaphors that persist in tech, which hold problematic historical baggage.
Master is used in many context like master key, mastering a song, master copy, having mastery in something.
To stir up controversy because one interpretation is "problematic" just emphasizes that interpretation and reminds everybody that they're not suffering from enough guilt about past events they had no personal involvement in.
I feel like that logic could be used to excuse every historical term with baggage.
Plus, it's not really stirring up controversy saying "hey, we should probably change the term to ~this~, which is equally or more descriptive, in a way that doesn't rely on historically problematic contexts". I think what you're focusing on is chiding people who still use the older terms; I've never seen that happen. I've seen people mix terminologies when discussing something, and oftentimes that has led to the person using the outdated instead using the updated, possibly with a conversation in between, but I've not seen someone call out "how DARE you use (technically-correct-but-outdated-term)!"
That said, I've also never seen anyone dispense with the word 'master' -except- in contexts where it is used to differentiate from 'slaves'. The parent post also only references in that context (though the great-grandparent calls both out separately, though one right after the other, which is likely what is muddling things).
Every word has baggage. "The" was used in slave documents. So were receipts. Does this mean everytime a grocery store clerk gives you a receipt they are perpetuating slavery?
Even Blacklist/Blackbook come not from anything to do with black people but Charles II and his list. If you are offended by it, it's because you chose to be.
What's your point? Does that logic excuse every word with historical baggage, or not? You state every word has historical baggage; either you then disagree with the parent logic, or you agree with the parent logic, and taken together with every word having baggage means you're saying every word is okay to use regardless of the historical baggage attached to it. Which is an interesting take, certainly.
It is OK to use words that remind people of troubling things as long the point of using it is not to do this antagonistically.
Someone could come along and tell me my name means 'short people are possessed by demons' and I would still go on using my name, even if someone said that was mean of me. Why? Because it's a ridiculous accusation, and you are a ridiculous person if you make such an accusation, or entertain it.
Now if I started calling myself '4 foot tall demons' that would obviously be different. It is entirely implausible that the 'baggage' is coincidental.
The point is that the sort of historical baggage you are talking about isn't relevant to the word or it's usage in context.
That logic always seems to fall apart for me. Of course words have had different non-problematic uses over time, before and after a problematic usage. But that doesn't negate the fact that it does and did have a problematic usage.
White people who want the ability to say the n-word often use a similar argument. ("It's only problematic [when/if]...") .
I believe strongly in freedom of speech. To allow assholes and bigots to reveal themselves.
I believe the movement to alter what words we’re allowed to say in our vocabulary is lead by educated mostly white “allies”. These people don’t speak for the underprivileged, they’re creating ways to feel better about themselves through self-policing because they don’t have any real idea about how to solve the issues that actually affect people.
It is very disengenous (and Americentric) to suggest we should revise our language just because of one event. That's simply giving more ground to the wrongdoers. Slave owners only used the word because of its existing connotations, after all.
Its ok to have a master copy, it is desirable to master your soul, someone might be of high station and therefore a master. Etc. It is a useful word. We shouldn't aim to limit the range of expression or accuracy of our words.
That logic always seems to fall apart for me. Of course words have had different non-problematic uses over time, before and after a problematic usage. But that doesn't negate the fact that it does and did have a problematic usage.
White people who want the ability to say the n-word often use a similar argument. ("It's only problematic [when/if]...") .
It's a good enough reason for me. My language is older than American slavery and it will probably outlive the memory of it; I am not American and I do not relate to the history at all. I won't surrender my language and speech to largely imagined grievances. My fear is just that, if I forbid certain words because of a rule that can be widely and arbitrarily applied, then I begin to surrender my thinking to outside arbitrary forces. It isn't worth it.
And I'll take the bait. We avoid the N-word because it is a pejorative, intended to diminish its subject. But no one uses "Master" as a pejorative the same way they might use the infamous N-word. The word has a much longer history, wider scope of meaning and wasn't invented as a pejorative (rather it is a compliment!). It is very possible to use "Master" in a sense that it isn't possible to use the "N-word".
Would you provide me with an objective definition of "problematic", and if I find other common words that meet that definition some point in the past, in any country between any group, will you stop using them?
A “cakewalk” is an easy victory or task. “Takes the cake” means to win the prize or to rank first.
Why it’s problematic:
The cakewalk was a pre-Civil War dance performed by enslaved people, and the winner of which would be given a cake. This is the original source for the phrases “takes the cake” and “cakewalk.” Because of this history, this word and phrase should be avoided.
By not saying these words, how are we helping minorities?
Can somebody please be clear on how ACTUAL PROBLEMS suffered by the disavantaged are solved by wordplay? Words don't cure poverty. Words don't reverse socioeconomic trends. Words don't give opportunity, cure abuses, change what our ancestors went through.
To me it looks very much like signalling, with no real effort.
My first introduction to the term was in the first chapter of SICP and it speaks positively about abstraction.
Also, I'm still not sure why cultural appropriation is actually considered bad.
Anecdata for sure, but I remember one time my cousin (who is of my same culture) excitedly tell us about how in another country (in another continent), a singer from our country was quite famous and they listened to his songs and even sometimes wore clothing from our country. It seems like our cuisine is popular there too. And all of us thought it was very cool!
Using the tools, trying the workflow, experiencing the friction, and just generally developing empathy for the day to day will make everyone better at their jobs. That includes job shadowing, which this is pretty much a form of. The major caveat is that you cant be part of critical path and its sometimes tricky to write even a great PR and expect honest feedback.
Author here. I agree with your caveat wholeheartedly. You've expressed it better than my "don't get in the way" comment. Don't take on critical path work is key. By all means fix things on the edges that are not time-critical or would not cause conflict during review.
> The basic thesis is one of dedicated roles, with the manager archetype focusing their time towards enablement, communication, and expectation.
No, it's because programming requires a mental model of the software and most managers don't have that. Add in constant interruptions and the inability to focus and you have a recipe for disaster.
Would you sometimes take a break from programming to go help accounting do the accounting work? No, no you wouldn't - accounting would smack the tar out of you. Just because you think you can contribute because you used to be able to is the notion that you need to break, and this applies to other fields too.
> This starts young with telling kids they can't be good at multiple things. "You need to focus."
A lack of focus on a problem space is usually the problem, yes. This isn't because we want people to stay in their lane and want to keep kids from being creative. It's because difficult problems are hard to solve.
If you are going to spend hours pulling down code and building it, ask yourself this question:
"Is this the best use of my time? Is pulling down source code and waiting for a compiler the best thing I as a manager can be doing?"
> It's because difficult problems are hard to solve.
Most software development does not involve difficult problems however - other than how to comprehend the stitching together or "complected-libraries-du-jour" via maximal indirection.
I know this is a meme (I guess about frontend web dev sometimes?), but I don't think I've ever seen it play out in real life.
Almost every program source code that I've read or worked on mostly consists of "data processing" and "control flow", with various kinds of abstractions that depend on the problem, programming language, etc.
Even for applications that seem straightforward, writing software well requires quite a bit of mental energy and focus/attention. Especially once you consider future maintainability and interfaces that other devs will use, testing and testability, documentation, readability, et al.
Denigrating programmers for using frameworks and libraries (the horror!) is just pointless and arrogant. Sure, most programmers aren't implementing novel algorithms from scratch with manual memory management. But that doesn't mean other problems can't be hard, it just means that the level of abstraction is higher and the programmer is free to use their mental resources to work and reason differently.
> No, it's because programming requires a mental model of the software and most managers don't have that. Add in constant interruptions and the inability to focus and you have a recipe for disaster.
This is so strikingly true. I try to explain to people who want me to pause a job and do something else that in my head I have this large, abstract structure of what I am trying to build, that is in an abstraction that itself is ephemeral -- it doesn't map nicely onto black boxes or pipes or anything. It is whatever works at that moment, and it requires me to tour it in my head all the time for it to exist at all.
But to me it isn't a question of focus, strictly speaking, because focus doesn't explain my interaction with that model. It's more a question of relaxed, constant presence; it's about having blur over other stuff. If I can inhabit that model in my brain without having to worry too much, it starts to work itself through while I am doing menial tasks like washing up or laundry or cleaning.
As soon as the business side of my freelance life takes over as it sometimes must, I am suddenly on the outside of that abstraction looking in. And no amount of detailed notes or documentation or diagramming will help me back in quickly.
> I try to explain to people who want me to pause a job and do something else that in my head I have this large, abstract structure of what I am trying to build, that is in an abstraction that itself is ephemeral -- it doesn't map nicely onto black boxes or pipes or anything. It is whatever works at that moment, and it requires me to tour it in my head all the time for it to exist at all.
You can. You can also demonstrate the issue in several other ways.
However, it never works. It may last a week, a day, a few hours, but sooner or later, they're going to believe that you're just staring off into space and that it's fine to interrupt you. That you can pick up and put down your task as easily as you would a pen.
> Would you sometimes take a break from programming to go help accounting do the accounting work? No, no you wouldn't - accounting would smack the tar out of you. Just because you think you can contribute because you used to be able to is the notion that you need to break, and this applies to other fields too.
As a counter-argument to this: With my software side business, I've had to dabble in accounting, and I find it a refreshing break. It's like going outside and pulling some weeds. For me it contributes to my productivity and mental health to have a diverse work experience.
> So, should managers code, design, and in other ways contribute in some way to production code or design? Sure, I don't see any reason they can't. Just understand the boundaries and stay out of other people's way.
Has this person been a manager? The amount of time is takes to keep up to date enough to make a net positive contribution is non-trivial. Doing this on top of management responsibilities? Good luck.
The communication between a development team and the rest of the company is complicated. Navigating this requires both a skillset completely orthogonal to writing software and a lot of time.
It all depends on how large the team is and the scope of responsibility. I see, in practice, three types of manager roles.
The first is the team lead manager. This team has 3-5 people on it, and the tech lead codes small features and pairs with other developers, and has a coaching role. Their people management skills are relatively low weight, and their managers, whether senior managers or directors, are doing the heavy lifting on how to manage career progression and run a department, but they will be intimately involved with the progression of the team's goals.
The second is the multi-team or large team manager. This manager has 6-15 reports and does not code or codes sparingly at best. However, they are responsible for low level strategy and tactics.
The third is the barely-technical people manager. This person has over 20 reports, and is in a reporting capacity and people managing capacity and the technical leads are delegated to handle strategic and tactical capacity. The manager is responsible for more holistic thinking and supporting the tech leads, Or the organization is light on career development.
I have seen all three happen. The key to understanding your responsibilities as a manager is to understand the organizational expectations. When you ask as a manager if you should code, the real question is what are you trading for that?
Agreed. I'm moving towards a team lead role at some point. I've volunteered in three positions in orgs outside of work. Team lead is about where my skills and interests end.
55 comments
[ 3.5 ms ] story [ 78.4 ms ] threadI could argue the linguistics, and the racial connotations never occoured to me then and don't convince me now. But what really makes me uncomfortable is the feeling that I'm surrendering part of my soul to some larger conscience that could turn on me at a whim.
+ master
+ slave
+ blacklist
+ whitelist
+ grandfather
+ brown bag
+ manpower
+ hijack
+ kill
The list goes on (and on) and I have not transcribed even a portion of it.
https://itconnect.uw.edu/work/inclusive-language-guide/
https://blog.ongig.com/writing-job-descriptions/a-list-of-of...
What do you call your dad's dad then?
A “grandfather” clause, “grandfather” policy or “grandfathering” in IT s a provision in which an old rule continues to apply to some existing situations while a new rule will apply to all future cases. Those exempt from the new rule are said to have grandfather rights, acquired rights, or to have been grandfathered in.
Why it’s problematic:
“Grandfathering” or “grandfather clause” was used as a way to exempt some people from a change because of conditions that existed before the change (e.g., we’ve grandfathered some users on an unlimited data plan.”) “Grandfather clause” originated in the American South in the 1890s as a way to defy the 15th Amendment and prevent black Americans from voting.
> Brown bags trace back to the “brown paper bag test,” which was traditionally used to judge skin color by certain African-American sororities and fraternities. References to a “brown bag” when we are really referencing a get-together over lunch surfaces an ugly period of American history that can alienate and offend people.
> (no can do) What might seem like a folksy, abbreviated version of “I can’t do it” is actually an imitation of Chinese Pidgin English. The phrase dates from the mid-nineteenth to early-twentieth centuries, an era when Western attitudes towards the Chinese were markedly racist.
> Using the word “pow wow” is cultural misappropriation, and ultimately racist.
> Referring to something as your spirit animal is cultural appropriation.
Some of these are pretty wild.
Some of this feels like someone tried really hard to find problems that didn’t exist and fix them.
That's how a lot of people feel about master/slave and black/white.
You have the word "master". It has at least two meanings in standard English and an additional one for technical jargon. Let's call these concepts owner/slave, expert/apprentice, and primary/secondary.
Even though owner/slave and primary/secondary are different concepts, the technical jargon makes the unfortunate reference the owner/slave meaning because of the use of the word "slave". It's difficult to defense the use of master/slave in this context.
The master in the expert/apprentice concept could be called leader, expert, or teacher and no one would have a problem with that.
This distinction is where people start getting upset.
I'd argue most technical people didn't even give a second thought to master/slave and for them they never considered it to be anything other than primary/secondary because owner/slave is no longer common use and hasn't been for a while. Besides, US Civil War was more than 150 years ago! Who gives a shit?
Well... people do because the effects of that war still affect our society and no one agrees on how to fix it. Removing problematic phrasing from our language as part of that makes sense. No one agrees on that either.
Therefore, by not using these words, you're reminded of the context. Any time somebody notices you substituting a phrase and they know why, they will be reminded of the context.
Like all self-censorship, it immerses the speaker in the truth while they trip overthemselves trying not to say that thing.
It's like saying, "Don't think about elephants." Now everybody is thinking about it.
About the elephant in the room you mean?
You can call your grandfather like you wish. You can also call stuff black.
Problem words: lower the bar
Suggested Alternatives: simplify, inclusive, make more accessible
It's hilarious how people perceive those who look like me.
Like we are some hyper-sensitive, fragile babies who cannot understand nuance of speech.
It's even worse when some white Americans are afraid to joke around me or poke fun at me, because they don't want to punch down.
Meanwhile I feel more privileged than most white Americans. I speak 3 languages perfectly.
One favor a hiring manager did for me, was giving me a tougher interview than most other candidates. He made sure everyone knew I was hired because I'm good at my job, not because I'm a "diversity-hired to fill some quota".
When I first moved here, I saw myself as a nerdy kid, who liked computers and wanted to build and create stuff. I saw myself as a human being who happened to look a certain way. I saw white people or Asian people just the same.
Then I made the mistake of consuming "woke content" on reddit and Twitter and it affected me, after college those ideas limited me in ways I could only imagine.
I really hope people see me as a bright kid whose into computers not some oppressed victim.
By the way, racism and prejudice exists but they show up differently.
Oh well!
Can you share more about this experience?
After living here for 15 years, I have realized the main narrative of the "black experience" "what is means to be black" is very Anglo-US-centric.
In college, I met a Jamaican guy, the culture shock was just as intense as when I met that girl from mongolia. Totally different cultures and customs. But on paper, in the USA , Me and that Jamaican guy were just Black.
I had more in common with the White French exchange student than with the Black-American kid from Virginia. To me: that black American kid and a white American kid were the same.
From an academical, political standpoint, Black has become synonymous with "African-American" Not just any "African-American", poor disenfranchised black Americans who are likely from the "ghetto". White means: some mean monster , who are controlling the world and are out to get everybody. So naturally I started to second guess how people acted around me.
Don't get me wrong racism is still alive and well I have experienced it in various forms:
* Prepaid for a meal at a fancy restaurant, the people before me just gave a name and grabbed their food, I was asked to show a receipt.
* Jogging in my neighborhood and having the police follow me around, almost like clockwork can't be a coincidence. (They became cool once they learned I lived there).
* Going out with my white coworkers in casual clothing vs going out with my siblings in casual clothing we have to dress extra fancy to get treated the same, otherwise we get poor service - The black guilt to tip extra at restaurants)
But: Most of the white people I've met were amazing, great people. That mean guy, is probably a jerk to everyone and just happens to be white.
There needs to be a balance, raise awareness about issues of society, but don't go to the extreme.
In my language: "The sky is blue, he is about to rain. I need to move my car otherwise she will get flooded"
But stopping the use of the master-slave metaphor in tech has nothing to do with assuming there are "hyper-sensitive, fragile babies who cannot understand nuance of speech" it has to do with real metaphors that persist in tech, which hold problematic historical baggage.
The IETF has a document with the clearest and most informative statement on this that I know about: https://tools.ietf.org/id/draft-knodel-terminology-00.html
Besides, "trunk" is an objectively more correct metaphor for the main "branch" in a "source tree".
To stir up controversy because one interpretation is "problematic" just emphasizes that interpretation and reminds everybody that they're not suffering from enough guilt about past events they had no personal involvement in.
Plus, it's not really stirring up controversy saying "hey, we should probably change the term to ~this~, which is equally or more descriptive, in a way that doesn't rely on historically problematic contexts". I think what you're focusing on is chiding people who still use the older terms; I've never seen that happen. I've seen people mix terminologies when discussing something, and oftentimes that has led to the person using the outdated instead using the updated, possibly with a conversation in between, but I've not seen someone call out "how DARE you use (technically-correct-but-outdated-term)!"
That said, I've also never seen anyone dispense with the word 'master' -except- in contexts where it is used to differentiate from 'slaves'. The parent post also only references in that context (though the great-grandparent calls both out separately, though one right after the other, which is likely what is muddling things).
Even Blacklist/Blackbook come not from anything to do with black people but Charles II and his list. If you are offended by it, it's because you chose to be.
Someone could come along and tell me my name means 'short people are possessed by demons' and I would still go on using my name, even if someone said that was mean of me. Why? Because it's a ridiculous accusation, and you are a ridiculous person if you make such an accusation, or entertain it.
Now if I started calling myself '4 foot tall demons' that would obviously be different. It is entirely implausible that the 'baggage' is coincidental.
The point is that the sort of historical baggage you are talking about isn't relevant to the word or it's usage in context.
There is nothing to excuse.
White people who want the ability to say the n-word often use a similar argument. ("It's only problematic [when/if]...") .
I believe the movement to alter what words we’re allowed to say in our vocabulary is lead by educated mostly white “allies”. These people don’t speak for the underprivileged, they’re creating ways to feel better about themselves through self-policing because they don’t have any real idea about how to solve the issues that actually affect people.
It is very disengenous (and Americentric) to suggest we should revise our language just because of one event. That's simply giving more ground to the wrongdoers. Slave owners only used the word because of its existing connotations, after all.
Its ok to have a master copy, it is desirable to master your soul, someone might be of high station and therefore a master. Etc. It is a useful word. We shouldn't aim to limit the range of expression or accuracy of our words.
White people who want the ability to say the n-word often use a similar argument. ("It's only problematic [when/if]...") .
And I'll take the bait. We avoid the N-word because it is a pejorative, intended to diminish its subject. But no one uses "Master" as a pejorative the same way they might use the infamous N-word. The word has a much longer history, wider scope of meaning and wasn't invented as a pejorative (rather it is a compliment!). It is very possible to use "Master" in a sense that it isn't possible to use the "N-word".
Would you provide me with an objective definition of "problematic", and if I find other common words that meet that definition some point in the past, in any country between any group, will you stop using them?
quote from the link: Definition:
A “cakewalk” is an easy victory or task. “Takes the cake” means to win the prize or to rank first.
Why it’s problematic:
The cakewalk was a pre-Civil War dance performed by enslaved people, and the winner of which would be given a cake. This is the original source for the phrases “takes the cake” and “cakewalk.” Because of this history, this word and phrase should be avoided.
Can somebody please be clear on how ACTUAL PROBLEMS suffered by the disavantaged are solved by wordplay? Words don't cure poverty. Words don't reverse socioeconomic trends. Words don't give opportunity, cure abuses, change what our ancestors went through.
To me it looks very much like signalling, with no real effort.
My first introduction to the term was in the first chapter of SICP and it speaks positively about abstraction.
Also, I'm still not sure why cultural appropriation is actually considered bad.
Anecdata for sure, but I remember one time my cousin (who is of my same culture) excitedly tell us about how in another country (in another continent), a singer from our country was quite famous and they listened to his songs and even sometimes wore clothing from our country. It seems like our cuisine is popular there too. And all of us thought it was very cool!
No, it's because programming requires a mental model of the software and most managers don't have that. Add in constant interruptions and the inability to focus and you have a recipe for disaster.
Would you sometimes take a break from programming to go help accounting do the accounting work? No, no you wouldn't - accounting would smack the tar out of you. Just because you think you can contribute because you used to be able to is the notion that you need to break, and this applies to other fields too.
> This starts young with telling kids they can't be good at multiple things. "You need to focus."
A lack of focus on a problem space is usually the problem, yes. This isn't because we want people to stay in their lane and want to keep kids from being creative. It's because difficult problems are hard to solve.
If you are going to spend hours pulling down code and building it, ask yourself this question:
"Is this the best use of my time? Is pulling down source code and waiting for a compiler the best thing I as a manager can be doing?"
Most software development does not involve difficult problems however - other than how to comprehend the stitching together or "complected-libraries-du-jour" via maximal indirection.
Almost every program source code that I've read or worked on mostly consists of "data processing" and "control flow", with various kinds of abstractions that depend on the problem, programming language, etc.
Even for applications that seem straightforward, writing software well requires quite a bit of mental energy and focus/attention. Especially once you consider future maintainability and interfaces that other devs will use, testing and testability, documentation, readability, et al.
Denigrating programmers for using frameworks and libraries (the horror!) is just pointless and arrogant. Sure, most programmers aren't implementing novel algorithms from scratch with manual memory management. But that doesn't mean other problems can't be hard, it just means that the level of abstraction is higher and the programmer is free to use their mental resources to work and reason differently.
This is so strikingly true. I try to explain to people who want me to pause a job and do something else that in my head I have this large, abstract structure of what I am trying to build, that is in an abstraction that itself is ephemeral -- it doesn't map nicely onto black boxes or pipes or anything. It is whatever works at that moment, and it requires me to tour it in my head all the time for it to exist at all.
But to me it isn't a question of focus, strictly speaking, because focus doesn't explain my interaction with that model. It's more a question of relaxed, constant presence; it's about having blur over other stuff. If I can inhabit that model in my brain without having to worry too much, it starts to work itself through while I am doing menial tasks like washing up or laundry or cleaning.
As soon as the business side of my freelance life takes over as it sometimes must, I am suddenly on the outside of that abstraction looking in. And no amount of detailed notes or documentation or diagramming will help me back in quickly.
you can send them this comic directly: https://i.imgur.com/3uyRWGJ.jpg
However, it never works. It may last a week, a day, a few hours, but sooner or later, they're going to believe that you're just staring off into space and that it's fine to interrupt you. That you can pick up and put down your task as easily as you would a pen.
As a counter-argument to this: With my software side business, I've had to dabble in accounting, and I find it a refreshing break. It's like going outside and pulling some weeds. For me it contributes to my productivity and mental health to have a diverse work experience.
Has this person been a manager? The amount of time is takes to keep up to date enough to make a net positive contribution is non-trivial. Doing this on top of management responsibilities? Good luck.
The communication between a development team and the rest of the company is complicated. Navigating this requires both a skillset completely orthogonal to writing software and a lot of time.
The first is the team lead manager. This team has 3-5 people on it, and the tech lead codes small features and pairs with other developers, and has a coaching role. Their people management skills are relatively low weight, and their managers, whether senior managers or directors, are doing the heavy lifting on how to manage career progression and run a department, but they will be intimately involved with the progression of the team's goals.
The second is the multi-team or large team manager. This manager has 6-15 reports and does not code or codes sparingly at best. However, they are responsible for low level strategy and tactics.
The third is the barely-technical people manager. This person has over 20 reports, and is in a reporting capacity and people managing capacity and the technical leads are delegated to handle strategic and tactical capacity. The manager is responsible for more holistic thinking and supporting the tech leads, Or the organization is light on career development.
I have seen all three happen. The key to understanding your responsibilities as a manager is to understand the organizational expectations. When you ask as a manager if you should code, the real question is what are you trading for that?