I'm curious to see how many engineers here use shell/*nix tooling on a day to day basis. My experience has been that newer engineers have no experience nor desire to learn any of it, whereas it was basically required when I was coming up.
Most platforms have a POSIX implementation, and a place for the POSIX shell (which standardizes job control that originated in Bill Joy's csh).
This includes Microsoft, who was the biggest UNIX vendor of the 80s with their Xenix series that was sold to SCO.
Microsoft Windows NT also implements a POSIX subsystem, which has waxed and waned over the life of Windows. The POSIX shell is quite relevant to modern Windows, and is worthy of study by any serious user.
I think it mostly depends on the particular engineer and the engineering culture of the team/company. I was hanging out in a coffee shop a while back, and some software engineers who looked extremely young happened to sit at a nearby table. I couldn't help but overhear them excitedly sharing their fun terminal/shell customizations with each other.
I don't think a willingness to engage in such things is a prerequisite to being a great software engineer, but it somehow warmed my heart to see that the younger generation could still find joy in such things.
Comments
I'm curious to see how many engineers here use shell/*nix tooling on a day to day basis. My experience has been that newer engineers have no experience nor desire to learn any of it, whereas it was basically required when I was coming up.
Most platforms have a POSIX implementation, and a place for the POSIX shell (which standardizes job control that originated in Bill Joy's csh).
This includes Microsoft, who was the biggest UNIX vendor of the 80s with their Xenix series that was sold to SCO.
Microsoft Windows NT also implements a POSIX subsystem, which has waxed and waned over the life of Windows. The POSIX shell is quite relevant to modern Windows, and is worthy of study by any serious user.
https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem
I think it mostly depends on the particular engineer and the engineering culture of the team/company. I was hanging out in a coffee shop a while back, and some software engineers who looked extremely young happened to sit at a nearby table. I couldn't help but overhear them excitedly sharing their fun terminal/shell customizations with each other.
I don't think a willingness to engage in such things is a prerequisite to being a great software engineer, but it somehow warmed my heart to see that the younger generation could still find joy in such things.