From humble beginnings at an MSP, I've adventured through life as a sysadmin, into an engineer, and finally landed as a developer focused on fixing problems with automation.
In many industries, there are people who don't want to deepen their knowledge, change conservative methods and move to an improvement direction. Maybe they have other goals ¯_(ツ)_/¯
From humble beginnings at an MSP, I've adventured through life as a sysadmin, into an engineer, and finally landed as a developer focused on fixing problems with automation.
Yeah, as far as "in your language," it's the same issue. Old heads leading the direction against the community and resisting change. One particularly heated thing among the PowerShell community was removing use of ? in variable names to enable features like the ternary or null operators without use of a clunky extra brackets:
$a?.access$a?[0]# vs${a}?.access${a}?[0]
Traditionally you only need to delimit your variable references in places where it might conflict with your meaning like in string interpolation:
"for_${example}_string"
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.
People against learning/change. It happens in my workgroup where using tech from the past ~decade is seen as "chasing shinies."
In many industries, there are people who don't want to deepen their knowledge, change conservative methods and move to an improvement direction. Maybe they have other goals ¯_(ツ)_/¯
Yeah, as far as "in your language," it's the same issue. Old heads leading the direction against the community and resisting change. One particularly heated thing among the PowerShell community was removing use of
?in variable names to enable features like the ternary or null operators without use of a clunky extra brackets:Traditionally you only need to delimit your variable references in places where it might conflict with your meaning like in string interpolation: