On Thu, 2 Jul 2015, Warner wrote:
On Tue, Jun 30, 2015 at 11:11:50AM -0700, David Lang(da...@lang.hm) wrote:
<snip>
What this author is trying to say is computer programming can be a trade of
a learned skill set, much like a brick layer is a learned skill set; albeit
a crude example. If companies are bemoaning about the lack of computer
programmers and the skill sets in the market, then they need to realize
that mandating a college degree is not needed. It makes no sense that 120+
credit hours from a collegiate university where a large chunk of those
credits have nothing to do with the skills sets needed for the degree are
needed. When in actuality, 1 to 2 years of full time study in just computer
programming is more than enough. This is the same for other trades like
electricians, plumbers, machinists, and the other vital skill sets needed
for society's infrastructure. We do not expect the vital skill sets for
these (electricians, plumbers, etc. etc.) professionals to have 4 to 6
years degrees. IT makes no difference to me if an electrician has read and
studied G. Chaucer's Canterbury Tales or if a plumber understand the
photosynthesis of pine trees. Yet for some unknown reason companies think
you must have the lick and seal of a university degree to be a "good"
computer programmer.
<snip>
People focus so much on degrees, regulations, and certifications. Most
professions could be learned with some reading and intelligence. I'm
getting tired of this game of compare and contrast.
My challenge is that the profession of Infrastructure and Operations is
often looked down upon from those who are ignorant. Infrastructure and
Operations is much more than rack and stack with OS installs.
I have even a greater challenge by the profession at large that is often
self deprecating, supplicating, and ignorant as to the depth and breadth
of their profession. I see this even among some executive technology
leadership.
That is the only reason I indulged this converation in the first place.
That's why the high end of the profession is latching onto words like
Systems Engineer, DevOps, Site Reliability Engineer, and Web Operations.
That end of the profession is more like engineers than technicians.
There's a spectrum of skill and knowledge with any profession. That's
why some folks are entry level and others have less responsibility even
with more experience.
I'm going to identify with and focus on engineering. That's where the
profession is evolving and growing. That's where the profession is
driving change and innovation across all industries.
If others want to focus on other parts of the profession, great. Thank
you, we still need that. But be aware of the depth and breadth of what
Infrastructure and Operations is.
When people talk about the Profession instead of profession, they always seem to
be talking about some sort of formal certification of it's practitioners, and
implied with this is that people who are not cerified should not be allowed to
practice the Profession. This is why the topic tends to drive to degrees,
regulations and certifications.
There are a lot of jobs out there that are looked down on that at the high end
require a lot of knowledge and expertise. I would like to see everyone who's an
expert be recognized as such.
This being said, other than the nebulous "no longer being looked down on"
criteria, what do you think needs to happen (and what could any organization of
practitioners do to achieve these goals, ignoring for the sake of discussion the
small size and budget of LOPSA)?
David Lang
_______________________________________________
Discuss mailing list
Discuss@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
