To create a new category, name a new game
linkedin.com
To create a new category, name a new game
1–10 of 39 posts
Re: To create a new category, name a new game
#2This is probably better well known as a "paradigm shift".
Re: To create a new category, name a new game
#3I wish this was easier to do as an employee: you see the writing on the wall, they pay you to be an expert in a field, but no one listens to your "we should be moving in this direction". You're met with one of my most annoying phrases: "this is how we've always done it."
The opportunity passes by, now your company is playing catch-up and managers above you are asking how they missed it. If you say "I told you so," you get a reprimand instead of acknowledgement.
Re: To create a new category, name a new game
#4I wish this was easier to do as an employee: you see the writing on the wall, they pay you to be an expert in a field, but no one listens to your "we should be moving in this direction". You're met with one of my most annoying phrases: "this is how we've always done it." The opportunity passes by, now your company is playing catch-up and managers above you are asking how they missed it. If you say "I told you so," yo…
This is a logical fallacy known as appeal to tradition
Re: To create a new category, name a new game
#5It makes for a good setup for the piece, but the whole "do or don't carboload before endurance racing" is still very much a subject of debate.
Re: To create a new category, name a new game
#6It makes for a good setup for the piece, but the whole "do or don't carboload before endurance racing" is still very much a subject of debate.
His point is "train your body to burn fat instead of carboloading". I don't get it, why not do both?
Re: To create a new category, name a new game
#7This is probably better well known as a "paradigm shift". https://en.wikipedia.org/wiki/Paradigm_shift
I think paradigm shift, at least when accurately used, runs much deeper than this.
Re: To create a new category, name a new game
#8I wish this was easier to do as an employee: you see the writing on the wall, they pay you to be an expert in a field, but no one listens to your "we should be moving in this direction". You're met with one of my most annoying phrases: "this is how we've always done it." The opportunity passes by, now your company is playing catch-up and managers above you are asking how they missed it. If you say "I told you so," yo…
This is part of company memory/history now and you can reference it in the future.
We don't want to avoid doing x because we will end up like [the time we missed the boat].
Re: To create a new category, name a new game
#9I wish this was easier to do as an employee: you see the writing on the wall, they pay you to be an expert in a field, but no one listens to your "we should be moving in this direction". You're met with one of my most annoying phrases: "this is how we've always done it." The opportunity passes by, now your company is playing catch-up and managers above you are asking how they missed it. If you say "I told you so," yo…
It really depends on the direction.
A lot of times, devs want to move in a new direction of whatever the hip tech stack is this year. This would help their career by adding the tech to their resume but the business benefit is almost always net negative.
Rather than arguing with a developer, they might just give a response that is outside of the developers' domain. The real reason is that it was a bad idea for the business.
Re: To create a new category, name a new game
#10I wish this was easier to do as an employee: you see the writing on the wall, they pay you to be an expert in a field, but no one listens to your "we should be moving in this direction". You're met with one of my most annoying phrases: "this is how we've always done it." The opportunity passes by, now your company is playing catch-up and managers above you are asking how they missed it. If you say "I told you so," yo…
It really depends on the direction. A lot of times, devs want to move in a new direction of whatever the hip tech stack is this year. This would help their career by adding the tech to their resume but the business benefit is almost always net negative. Rather than arguing with a developer, they might just give a response that is outside of the developers' domain. The real reason is that it was a bad idea for the bus…
That's a fair point. The perspective of developers is different from that of a manager with perhaps a longer term view or other knowledge than the people in the trenches.