<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by The men of the third age on Medium]]></title>
        <description><![CDATA[Stories by The men of the third age on Medium]]></description>
        <link>https://medium.com/@snichor?source=rss-158d1b7d1f3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3kj4_IfuqdHDJF_8IkgVFQ.png</url>
            <title>Stories by The men of the third age on Medium</title>
            <link>https://medium.com/@snichor?source=rss-158d1b7d1f3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:17:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@snichor/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Five tips on changing careers]]></title>
            <link>https://medium.com/@snichor/four-tips-on-changing-careers-c3f683c341bf?source=rss-158d1b7d1f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3f683c341bf</guid>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[career-change]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[The men of the third age]]></dc:creator>
            <pubDate>Sun, 31 Oct 2021 01:28:53 GMT</pubDate>
            <atom:updated>2021-10-31T01:30:06.716Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HmPIP8Qpk3Es3X4zmwr0Fw.jpeg" /><figcaption>Maybe your goal is to sail the high seas!</figcaption></figure><h4>It’s never too late</h4><p>Careers are pretty different in 2021. There’s not so much a linear progression these days, where you stay in a job for life. Instead, we’re tending to jump around more. My personal opinion is that the loss of job continuity is something of an issue, but that is an article for another day. This piece is a practical approach to changing careers, mostly based on my personal experience. Without further ado, here we go.</p><h4>1. Think about why you want to change</h4><p>This seems kind of basic, but you do need to decide the why of changing a career. Possibly you’re driven by values and the job you’re doing is not in line with your values. Maybe the job you’re doing is being phased out. Or maybe you’ve been made redundant, in which case you’re being forced to make a change.</p><p>One point to make about the why: it helps to talk with friends about it. You want to be clear on the why you want to change. It needs to be a level headed decision. For me, the decision to change careers last time around was easy: I was already training adults and enjoying it.</p><h4>2. Work out what you need to get there</h4><p>Sometimes changing is straightforward. No qualifications, no certificates, diploma/degree required. But generally, you’ll need a certificate at least. This might be an IT certification (like a CCNA or an AZ certification) or a teaching degree. The former is something that can be done over 4 weeks (if you study like mad), but a degree can be anything up to 8 years (if you study part time). This is where you’ll need to do some research. If you’re heading into IT, decide which field. Think about which area interest you the most, and which area is likely to sustain your interest.</p><h4>3. Look for openings that allow you to get an idea of what you future job is like</h4><p>Sounds basic, but seriously: many people have great ideas of what it might be like in a different career, but they never think that most careers have long periods of drudgery. It might look great from the outside, but the view from inside is always different. As one of my old bosses would say, “Everything looks rosy”. See also point 1.</p><h4>4. Assess your personal situation</h4><p>This can be a big one. You do need to decide when and if you can make a change. This requires a stock take of your financial and personal situation. It can seriously be the most difficult part of the process. If you have a partner (de facto or married) then you’ll want to take to them about the change. One aspect is whether you keep working in you current job, whether you take time off (like a year or two) to re-train, whether you study part time. IF you have a bi redundancy payout, taking a year off to study may be feasible. If not, consider doing part time study.</p><p>If you’re aiming for IT certification, part time study is likely to be your best options. Many certifications require around 6 months of chipping away, before taking the test.</p><h4>5. Rejig your CV</h4><p>The tricky part of course in changing careers is changing your CV. This requires a little more abstract thought. Step back and think about what higher level skill(s) can I demonstrate? How does this assist in changing to my new career? At this point it is sometimes helpful if you have done some volunteer or pro bono work related to your new career. Put that in, and make sure it is on page 1. I can tell you from experience, people that have CVs cross their desk won’t look much further than page 1. If your CV is good, then they will go through it.</p><p>Those are my five tips. It does require hard work and clarity of thought to successfully change careers. Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3f683c341bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The upsides and downsides of volunteer work]]></title>
            <link>https://medium.com/@snichor/pros-and-cons-of-volunteering-c219d7e4e015?source=rss-158d1b7d1f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/c219d7e4e015</guid>
            <category><![CDATA[volunteering]]></category>
            <category><![CDATA[pro-bono]]></category>
            <dc:creator><![CDATA[The men of the third age]]></dc:creator>
            <pubDate>Sat, 30 Oct 2021 02:36:00 GMT</pubDate>
            <atom:updated>2021-10-30T03:22:26.571Z</atom:updated>
            <content:encoded><![CDATA[<p>Australia has a rich history of volunteering”, said the guest speaker (or something similar). I have to say, the statement caught me by surprise; to be honest the only thing I can think of these days when it comes to Australia is the famous Donald Horne quote, even more so as we really are a country run by second rate people these days. But I digress. I’ve done volunteering work a few times in my life, and it’s mostly been pretty rewarding. But there are some pitfalls to look out for along the way.</p><p>The first time was basically to do some work for an organisation — just basic unskilled labour. I was, at that stage, not long out of uni, and was making a living doing some odd jobs while I figured out where I was going to head to next in the world. That lasted until they found out I had other skills relating to writing code, which meant I was swiftly asked to do some contract work. Which led onto more contract work, till eventually it become a job. And then I left, to do some more travelling. But the experience I gained was enough to get more full time work a year later, in an IT position.</p><p>The second time around I did it partly to explore a new career — at that stage I was a burnt out IT support professional, tossing around options for a new career. After 20 + years of having to do con-calls at 3–4am in the morning, working weekends for little or no overtime, missing out on family time — enough was enough. Getting offered a redundancy gave me some relief, and that was when I started exploring other options. This of course could be you. And so after a bit I thought about volunteering at a local youth organisation. And so began the second and somewhat longer phase of my volunteering. I stuck at this one a few years, until other commitments started taking priority. And so I left, on good terms I hasten to add.</p><p>Volunteering is a great way to gain some work skills, or to look for a new pathway into a career. Just be mindful of over doing it. Don’t turn it into a full time job; you’re not getting paid to do this, remember? Choose where you go wisely. This is like any job you might go to. If you can, check out the staff. This is not always easy I know: you can’t go around and ask them all, “where do you work” etc. But if you can, see if you can detect any cliques.</p><p>The culture can change quickly. When I started work as a volunteer many years back, I was working under a lovely fellow who had the knack of pulling people together. He left, a few other people left, and the culture changed. Other people came in, all of them knew each other, and the whole culture subtly changed. There’s not much you can do, but look to ride it out, or see if you can transfer.</p><p>But overall, I don’t regret volunteering. It was good fun, I learned a few new skills. Even relearned some old ones, like how to install Windows server 2012.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c219d7e4e015" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[About me]]></title>
            <link>https://medium.com/@snichor/thanks-for-dropping-by-480b812ee8e8?source=rss-158d1b7d1f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/480b812ee8e8</guid>
            <category><![CDATA[bio]]></category>
            <dc:creator><![CDATA[The men of the third age]]></dc:creator>
            <pubDate>Sun, 24 Oct 2021 07:27:52 GMT</pubDate>
            <atom:updated>2026-02-28T01:05:49.919Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a 25+ year veteran of the IT industry. My career started around the time Linux first appeared. I must admit, my tech career was a bit of an accident.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=480b812ee8e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ten Things to check on your Storage and SAN environment]]></title>
            <link>https://medium.com/@snichor/ten-things-to-check-on-your-storage-and-san-environment-7af6f686fe5?source=rss-158d1b7d1f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7af6f686fe5</guid>
            <dc:creator><![CDATA[The men of the third age]]></dc:creator>
            <pubDate>Sat, 16 Oct 2021 12:45:23 GMT</pubDate>
            <atom:updated>2021-10-16T12:45:23.409Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Remote replication and the associated hardware are powerful tools to ensure continuity of business. But care must be taken in deployment and use.</em></p><p>SAN switches and storage arrays have been around for many, many years. And over time, they have become more fault-tolerant. However, various issues can still occur. In particular, issues with remote replication and associated hardware can sometimes take time to resolve. I’ve come up with a few guidelines that may help you to prevent some issues from occurring, or alternatively cut down the time taken to resolve issues.</p><ol><li><strong>Check your remote replication works</strong></li></ol><p>After the initial setup of replication, ensure that there are procedures in place to describe which file systems are to be replicated. The pitfall is when disks are added to a server’s file system on the production site, but not on the remote site. The end result can be potentially disastrous if you find that a file system has grown on the production site, but the remotely replicated file system does not include the extra disks. There is no easy way back from this type of issue, particularly when a restore is required.</p><p><strong>2. Ensure you have functioning dual paths for remote replication</strong>.</p><p>Make sure that the dual paths between sites take a separate route to the remote site. Although the instances of a backhoe operator severing data cables have become less frequent due to modern mapping systems, breaks still happen. Most service providers have links between sites going via a different physical route, but you should check.</p><p><strong>3. Ensure the DWDM hardware is supported by your SAN vendor.</strong></p><p>Remote replication usually is done via a SAN switch connecting into another switch, which typically uses Dense Wave Division Multiplexing (DWDM) at the physical level to send the data to a remote site. A big question is: are your SAN switches running a supported mode for remote replication? It might seem basic, but even changing a card on the DWDM switch could put you into an unsupported configuration.</p><p>Upgrades to DWDM hardware also mean you have to check that the SAN switch is running a supported firmware version. This is usually the case; however, sometimes customers have long lag times between firmware upgrades. Be sure to check and advise the customer if there is going to be an issue. Gently remind them that upgrading firmware to the latest version or just below is in their best interests.</p><p><strong>4. Document the order to bring hosts up.</strong></p><p>Storage is very robust? It certainly is, but you still need to know if there are any issues with the order in which hosts are started and applications are started. A document that states this can save you time.</p><p><strong>5. Ensure you have contact details for your DWDM hardware vendors.</strong></p><p>It’s better to not just know where the hardware is located in the data centre. You should also know who to call if you think there is an issue. Sometimes DWDM hardware is looked after by network teams, sometimes it is an outside company. Whoever it is, make sure you know who to call 24/7/365.</p><p><strong>6. Ensure you know who the service provider for DWDM is.</strong></p><p>This may seem common sense, but I have known customers to not know who actually looks after the DWDM service. Sometimes it is the same people who supply the hardware, sometimes it is not. If it isn’t ensure you know the details of the service provider.</p><p><strong>7. Don’t ignore what looks like a spurious alert on SAN switches.</strong></p><p>If you notice some odd alert on a SAN switch, check it out, and get to the root cause. It may be nothing. Or it may be a sign that something is amiss. One customer had an alert that appeared after a weekend. Turned out it was a warning about link degradation on the DWDM link. However, it had been ignored for almost two weeks before an investigation into a slowdown of backups turned to checking out the SAN. The link degradation was due to a cable; cable was replaced, alerts disappeared, and the backup slowdown issue was resolved.</p><p><strong>8. Know the business impact if your remote replication is down.</strong></p><p>If the remote links go down completely, what is the impact? For many sites it might mean backups are affected. Other sites may run reporting type databases; this could mean a business hours impact. Whatever the impact, make sure you know what it is.</p><p><strong>9. When a vendor makes a change to a piece of DWDM kit, make sure you know exactly what they are doing, and make sure it is done one path at a time.</strong></p><p>Once one path is done, run through checks to ensure the replication is still working. Check any alert messages on the SAN side. Once you are satisfied there is no impact, then you can allow work on the second path. The bottom line is that you want at least one fully functioning path.</p><p><strong>10. Ensure cables in the data centre are separated by distance for redundancy, and make sure they are labelled.</strong></p><p>I have seen the case where cables for multi pathing of servers have been loomed together. I’ve also seen a contractor removing old fibre cables by cutting the links and pulling the slack out. The inevitable happened one day. He cut through a live cable; several in fact. Luckily, it only affected one path for each of the impacted servers. All the paths successfully failed over, but it did trigger a few software alarms, and a rapid visit from the data centre manager to the area of misdemeanour.</p><p>Remote replication (and the hardware that supports it) is a wonderful tool, if built and maintained correctly. These guidelines should help to prevent some issues, and to enable timely resolution of other issues.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7af6f686fe5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I took up blues harp, and why I stopped]]></title>
            <link>https://medium.com/@snichor/why-i-took-up-blues-harp-and-why-i-stopped-61c3a700c6c1?source=rss-158d1b7d1f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/61c3a700c6c1</guid>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[The men of the third age]]></dc:creator>
            <pubDate>Sat, 16 Oct 2021 12:30:09 GMT</pubDate>
            <atom:updated>2021-10-16T12:30:09.025Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*XmiOPgirJj_T8yF2CaVuNQ.png" /></figure><h3>Why I took up blues harp and why I stopped</h3><p><strong>It’s not as easy as it looks</strong></p><p>I’m a bit of a failure at a few things in life. Probably most things in fact. One of the reason I took up Triathlons was the attraction of the motto: “why be bad at one sport when you can be bad at three?” There have been some successes along the way I guess. I managed to not finish last in just about every race. I have so far (touch wood) been able to get around courses.</p><p>Other notable failures in my life: I somehow never got to play bass in a rock band and become famous. Or write lyrics and songs that would enable me to get royalties from my Grammy award winning album(s). The royalties that would enable me to set myself up nicely in far north Queensland where I could pontificate about the poor state of something or other and announce my plans to hold a benefit gig for something that takes my whimsy. Though I did manage to play a few gigs with a band, sadly none of us really could be full time musicians, and it was pretty obvious that my lyrics were little better than <a href="https://hitchhikers.fandom.com/wiki/Vogon_poetry">Vogon poetry</a>.</p><p>Of course, there are many things I have been good at — rather obviously, I have made a tidy living working on Unix and later Linux servers. I’ve been principal author on a paper and co-author on another, both published and presented at a conference. Both used a fair chunk of mathematics; the paper I was principal author on also used results from a software program that I did a heap of work on.</p><p>But I digress. Someone gave me a blues harp for Christmas one year. Actually, I suspect this person seriously doubts my ability to do anything of note musically. Yes I know — a terrible choice of words. This person has at various times given a book on how to play guitar, sent me some a device like a slide rule that helps me work out keys (I already knew how to do this) and lastly given me a blues harp. The blues harp is a mysterious instrument. It has 10 holes. You blow in, a note comes out. You breath in, a different note. There is one full octave and two partial octaves. You can bend a note down and fill in the missing notes. I picked it up, had a bit of a look around on the net, worked out a few basics, and started playing.</p><p>But I quickly realised something about blues harp. There are some great players out there — really, really great. But a harmonica is a sort of lead instrument. Or it’s a fill type instrument. I never have had any aspirations to be a lead guitar in a band. I always liked to play bass or rhythm guitar. Playing harmonica was honestly out of my league. Musically it was hard for me to aspire to do anything other than simple Dylan-esque fills. Which I am perfectly fine with. But playing stuff like you see on YouTube? No — not me. And so I stopped. I still like blue harp, and I still hack away sometimes, but as for playing a song and adding in my meaning — no that’s not me. And I’m at peace with that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61c3a700c6c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Life Lessons from tech support]]></title>
            <link>https://medium.com/@snichor/lessons-from-tech-support-6d7ecd13eac3?source=rss-158d1b7d1f3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d7ecd13eac3</guid>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[The men of the third age]]></dc:creator>
            <pubDate>Sat, 16 Oct 2021 11:28:41 GMT</pubDate>
            <atom:updated>2021-10-24T03:40:43.875Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*nvHhEUQqklpmTF25bFzklQ.jpeg" /></figure><p><strong>The light at the end of the tunnel might be an oncoming train</strong></p><p>In a previous life, I worked in tech support. Which is to say I worked in 2nd/3rd level type support. Not directly customer facing, but usually on conference calls with other techs. Or engineers depending on how the company classified you. I’m sharing a few thoughts on various lessons I learned along the way.</p><p>My job titles in rough chronological order went something like this: a Software Engineer, Systems Programmer, Systems Officer, Systems Administrator, Unix Engineer, Storage Engineer, Systems Officer (again), Linux Engineer, Unix Engineer (again) and finally Systems Administrator. Throughout my career I have used a various mix of skills. I can script in bash. I can code in Python. I also (long ago) used C and C++ (back when I was a Software Engineer). But the thread that runs through all my roles has been using tools (like bash/Python) and problem solving skills to fix problems. In many ways, whilst the tools are better and more sophisticated, I still used pretty much the same skills throughout my career. My point is that none of my job titles had much meaning. You can often call yourself by any title in IT. I’m not saying that’s right; it’s just how it is. Don’t worry about titles; they mean little. Worry about developing your skills.</p><p>Of course the big lesson we’re all learning right now is how to work remotely. Now this is something I had to do a lot of when I at my career peak(?!) many years ago. Working remotely then of course meant having to get up at 1am because something had broken on a customer’s mission critical system, and you would check and escalate after 1 hour because it was looking more complex, and then you have a resolution manager assigned and he/she calls a conference call at some time around 3am, and you start to wonder why people say sleep is overrated. Anyway at sometime around 4am a vital component is shipped to the customer site. Usually the company’s policy is to ship two of the components to the customer site but there was only one in Sydney at the time. Guess what? Said component is a DOA (Dead on Arrival) so we have a talk at 4:30am about getting a component from Melbourne. And on and on it goes. This was an actual incident I worked on by the way.</p><p>Anyway, I digress. One of the issues I think we all are perhaps finding out is that, of the various levels of communication available to us, face to face is probably the most efficient. Next is video/phone. Then emails. Then messages. I still recall one of my managers telling us not to bother with emails. Call the person, he would say. Don’t respond to a long to and fro email by continuing the process. Just call them. Better still, arrange a meeting. And this was something I have observed in great detail; people overestimate their ability to express themselves in an email. Everyone (and I mean everyone) can write an email, think the point they have made is clearly expressed, send it, and have it completely misunderstood. Sure, most people will understand an email. But remember the receiver’s mind doesn’t have direct access to your mind and may have a different cultural set of values. If in doubt, send an email and call. Or meet in person.</p><p>There’s probably a few other lessons I learned along the way, like how to make cpio (Unix/Linux people will know this command) into a sort of sort. Just take the “Yippee-I-Ohhh” and substitue in “Cee-P-I-O”. You can dance along to it too, though it probably has to be 3am and you’re in a data centre waiting for a HP N series server to reboot, which meant about 35–40 minutes of spare time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d7ecd13eac3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>