In the past year or so, I have been using Twitter a fair amount, and I have found that, despite all of the systemic issues of bullying and harassment, there are also plenty of communities from which to learn, exchange ideas, and commiserate. From time to time, I need to find a specific tweet, and have taken to using a few searches, filters, and operators to find what I need:
Thoughts on many things Posts
Since it’s been a few years since I wrote about my podcasting diet, and since easter is coming up at the end of the week, I thought I’d take a new look at what podcasts I subscribe to. I still use Downcast for podcasts; it’s been working well for me, and I see no need to replace it with something else. The podcasts I listen to has changed a fair bit over the years; some have been removed, and others have been added. Here’s the list as it currently stands:
When you work product support on a specific product, you need to have a solid grasp of how to set up the product, as well as the best practices for making things work as you want and expect. This was certainly the case for me when I worked for FotoWare. One of these best practices was not to use the Domain Users group to set permissions.
I am a big believer in the principle of putting information out there, for the world to see. This blog is part of pursuing the goal of achieving just that. It made sense to me, then, to ensure that the data from my weather station would be made available to as many people as possible.
I am sure that I am not alone in making an effort to keep abreast of what jobs are being posted within what can largely be termed my field, and am struck by the paradox represented by requiring relevant experience for most jobs, even entry-level positions. For example, I have seen my share of highly educated people cycle through a support department on their way to the jobs they’ve educated themselves towards – usually software development – in an effort to gain “relevant experience”.
An important principle of ITIL is that all requests should go through a single point of contact (abbreviated to SPOC). What this means, is that a single channel should be defined for the reception, classification, and distribution of a request or incident. Crucially, it does not mean that all contact with the customer should be done by tier one.
In December of 2016, I discovered Bear Writer. At the time, I had been using a number of different solutions for note-taking and organisation, none of which had really done the trick for me. That all changed with Bear. Arriving to critical acclaim, Bear is certainly a very pretty app, and its iCloud sync feature has served me well enough. There has just been one issue; it is only available on Apple devices.
In recent years, a number of approaches to taking hand-writing and turning it digital has come to the market. From tablet computers to writing tablets with e-Ink technology, there are plenty of offerings out there, none of which has scratched my itch for hand-written notes. Tablet computers tend to be too slick and slippery, resulting in a less than satisfactory writing experience, and e-ink writing tablets are – at least as this is being written – just not good enough for my use.
One of my many roles at work is that of change coordinator for a large subset of our customers. I have learned a lot in this capacity, and have come to feel that, while Incident Management is the natural first step in ITIL implementation, until you start implementing Change Management, the majority of your effort is largely spent firing fires.
Working with process development, I have found that I draw on the lessons I learned in business continuity planning during my studies. In particular, I have found that the actions to take in response to risks, also known as the four t’s, has been particularly useful. These four are: