Finding a workable pain management procedure has taken much more than I ever would have suspected. While in one of my periods of relative “feeling good” I checked out the OSHA website and found an article on ergonomics. In the referenced article it is stated that “Work-related musculoskeletal disorders (MSDs) currently account for one-third of all occupational injuries and illnesses reported to the Bureau of Labor Statistics (BLS) by employers every year. These disorders thus constitute the largest job-related injury and illness problem in the United States today.“ Finding data specific to those of us who sit for hours in front of our computers as programmers was not a quick find, and therefore I don’t have specifics.
What I do have to say is that MSDs are real, can be very painful, and get in the way of living ones life to the fullest!]]>
WOW! What a perspective! I believe it was originally posted somewhere in response to the release of the SANS Top 25 Programming Errors. (See my January blog post “Software Development, Security and Programming Errors“). At the time I simply dismissed the comment as being way out in left field – but the comment has haunted me since reading it.
I suspect that the comment has haunted me as it has because I am keenly aware that certainly there is the potential of an element of truth to the perspective. However, I’m not so sure that “easy” software development tools add to the problem, I would expect well designed tools (easy or otherwise) to be producing well designed and secure software.]]>
Secondly I believe that most applications will have those activities which are only seldom performed, or performed only as a “fix” to something gone wrong. The infrequently performed operations which just don’t fit into the everyday flow of the business function, and therefore also not of the business application should be documented for users. Of course, any documentation available will be only as good as its availability.
Ready availability of documentation for an application, or more explicitly documentation specific to a particular operation is crucial. As long as I’ve been around applications this has always been an issue. First off, creating good user documentation (read this as usable user documentation), is not an easy task. It can also be a costly task. Ineffective and it won’t get used, unavailable and it won’t get used, confusing and hard to find answers and it won’t get used!
More often than not what I’ve seen is an attitude of “Why document – nobody ever looks at it anyway”, or, “Document the obvious, don’t worry about the details – let them (users) ask!”. Personally I think application users deserve more respect than that.]]>
While mulling over the “…paperless life…” idea I recalled how yesterday while watching TV in the morning I was introduced to the term “Data Rot” in a CBS news story. I’d never run into the term but I immediately could relate to the terminology, as well as the concept of data formats “going away”. (I was enthralled with the “wire recorder” and “reel to reel” recorder when I was in my ‘tweens!).
Anyway, “Data Rot”, the “paperless office” and “paperless life” all are interesting topics, and looking back at what I’ve seen for changes in my life, I can’t help but wonder what our lives will look like in 2080? One thing I’m sure of, however, death and taxes – not necessarily in that order!]]>