being patient with technology - and learning to leave unneeded things aside

programmers sometimes get frustrated or annoyed with new technology. then they get enthusiastic and finally they realize it's nothing new. this is not my own thought - someone else has long ago made this observation.

patience can be very difficult when it seems that the originators of a technology seem to have a different viewpoint than your own. perhaps they wanted to solve a more general problem, and therefore put together a general library and documentation without addressing (what you believe to be) the major application of the technology. the w3c's specifications are classic in this regard. ironically this frustration (and even elation) is not helpful. it blinds you to the reality of the technology.

the solution is to be patient and accept technology for what it is, warts and all. it may help to familiariaze yourself with the human side of things, and to realize that this thing that frustrates you was created by someone with the best intentions. after all, it takes a lot of work to write usable software and a lot of commitment to release it to the public. learn to ignore the parts that you don't need. use your patience to write documentation for others that come after you. realize that there probably is a good reason for complexity that initially appears needless. (perhaps there isn't a good reason, but give the author the benefit of the doubt, at least!)

No comments: