See our nonprofit COVID-19 resources
We're updating our site to improve your experience. We apologize for any issues that may occur.
My farther was an instrument technician, I began my working life as a field archaeologist (the folk who actually do the digging), a group once dismissed by an academic as 'mere technicians'. After retraining in IT I have worked for some organisations that viewed IT staff as 'the chap (yes we are mostly male) with the screwdriver'. Meanwhile on the other hand in the 'hard core' tech community I am sometimes seen as not technical enough because I worry away at issues like program documentation, accessibility, usability and interface design rather than writing source code.It could be said not unfairly that I am over sensetive about the issue but this article by Dawn Parzych over at opensource.com caught my interest. 'What does being 'technical' mean?' (https://opensource.com/article/21/2/what-technical). Dawn is tackling the issue as seen from inside the tech sector but stereotyping and cliched sloppy thinking can work both ways.How do you make your technical staff feel valued, or if tech is your focus how do you make your non-technical staff feel valued?
Techsoup Community Forum Moderator
Close this window