As long as you don't consider it a general and immutable rule I am fine with it.
You may also consider deliberate learning (e.g. Coding dojos) to frame learning sessions in space and time (codingdojo.org/DeliberatePractice/).
Building this discipline may help to sharpen skills, to be open to different ideas and broaden some knowledge. There is no need to dig deep. Sometimes have surface knowledge or just knowing that something exists is OK.
Valid points! My point is more of if you spend more time learning something you (probably) won't use, you'll have limited experience in the technologies you will.
An example is if for say I'm a backend developer and all my projects are backend, but I spend hours learning say react, while it can be useful, in this scenario it doesn't provide any benefit, other than me knowing how to use it.
About the split between frontend technology and backend technology, I think there is value to know at least a subset of the other side in order to better communicate between frontend and backend developpers.
This can help the organization to break silos. It is for instance what the DevOps philosophy is all about by the way. Make Dev and Ops talk and have more empathy to each other.
I don't advocate to dig deeply unrelated techs for the sake of it. Though, having a minimum of general culture helps make better design choices and better communication with peers in my opinion.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
As long as you don't consider it a general and immutable rule I am fine with it.
You may also consider deliberate learning (e.g. Coding dojos) to frame learning sessions in space and time (codingdojo.org/DeliberatePractice/).
Building this discipline may help to sharpen skills, to be open to different ideas and broaden some knowledge. There is no need to dig deep. Sometimes have surface knowledge or just knowing that something exists is OK.
By not broadening knowledge, there is also a risk of becoming an expert beginner.
daedtech.com/how-developers-stop-l...
Valid points! My point is more of if you spend more time learning something you (probably) won't use, you'll have limited experience in the technologies you will.
An example is if for say I'm a backend developer and all my projects are backend, but I spend hours learning say react, while it can be useful, in this scenario it doesn't provide any benefit, other than me knowing how to use it.
I agree.
About the split between frontend technology and backend technology, I think there is value to know at least a subset of the other side in order to better communicate between frontend and backend developpers.
This can help the organization to break silos. It is for instance what the DevOps philosophy is all about by the way. Make Dev and Ops talk and have more empathy to each other.
I don't advocate to dig deeply unrelated techs for the sake of it. Though, having a minimum of general culture helps make better design choices and better communication with peers in my opinion.