F
Flasherly
Mine, too. Thankfully, though, they had a regular IT support
department for Microsoft maintenance considerations. Different world
and one without any aspirations on my part to cross over. I had no
qualms about following the same protocols as everyone under the
direction of IT, although what I know of Windows within a personal
perspective is entirely a different world. I'd built computers for
few coworkers or advise given, however, and word got around and
suggestions came back that I should consider transferring to IT.
Windows as an abstraction is beneath most everything else, although on
occasion it does surface perhaps in the sense you're suggesting for an
annoyance. But, that's what I do. I'll hack or modify it until the
form is acceptable, not something I suppose everyone would care
concern themselves with time and effort. And, most certainly not a
standpoint from which to enter into a wider public or official
perspective of an IT-backed Microsoft. It's one big advantage is being
the premier platform, everything that's new and technological filters
through for culling. In as sense of alternatives, as there's still
much I can't deal with these days as I'm pretty far out of
compliance. Setting up another browser, for instance, Explorer, for
corporate retrieval purposes wouldn't be appealing, either. I tend to
see the browser, any browser, as insular within its own area of
protection from other areas. When closed, anything related to outside
content is abnegated, and while open I try and be careful to filter
what can come through.
A matter of time and patience, I suppose, for working with resources I
do enjoy and actively will protect. Oranges and apples, I'd tell them
at work. What I personally enjoy doing I simply wouldn't if placed
under formal directions and guidelines.