Finally leaving my job, and it's just as annoying as I thought it would be
-
@scottalanmiller I think @guyinpv should give that one a shot.
-
That's the way to do it!
-
@scottalanmiller said in Finally leaving my job, and it's just as annoying as I thought it would be:
No time or date on it, instructions unclear, demand he continue to work without a paycheck thinking he was termed 6 years ago.
-
@guyinpv any news on the job after another week there? Decided that it is just time to go? Planning to stick it out for a while?
-
@DustinB3403 said in Finally leaving my job, and it's just as annoying as I thought it would be:
@guyinpv said in Finally leaving my job, and it's just as annoying as I thought it would be:
And all I wanted to do was open up a conversation so they could start looking for a replacement. I wasn't expecting a circus.What were you realistically expecting?
To begin a detailed, thought-out, plan of finding a competent replacement. Start looking at quality job boards, map out job requirements, etc. Be reasonable, efficient, mindful.
Instead they panicked that I was going to walk out and leave in a couple days. They rushed to find anybody with basic knowledge of a computer from the local staffing agency and threw them onto my lap with little consideration. Now I'm trying to train a person with no experience and fairly rudimentary knowledge. Plus they dumped all these demands for an encyclopedia worth of how-tos, procedures, vendor notes, troubleshooting guides, etc.
It's funny but also sad. One day the new person was there and I was at home, sick or something. A shared network connection in Windows got disconnected which made an app pop up an error. New person tried to troubleshoot the app, perhaps not knowing the shared network drive existed. So boss asks if I've already written a specific procedure for this specific app when having this specific error caused by this specific problem.
I'm just like, no, I can't write a procedure detailing every conceivable error that can happen on every one of 50+ vendors we deal with, lol.
The IT person is supposed to know how to troubleshoot issues, not just read from a procedure book encyclopedia written by the previous IT person!
-
@guyinpv still there?
-
@guyinpv said in Finally leaving my job, and it's just as annoying as I thought it would be:
@DustinB3403 said in Finally leaving my job, and it's just as annoying as I thought it would be:
@guyinpv said in Finally leaving my job, and it's just as annoying as I thought it would be:
And all I wanted to do was open up a conversation so they could start looking for a replacement. I wasn't expecting a circus.What were you realistically expecting?
To begin a detailed, thought-out, plan of finding a competent replacement. Start looking at quality job boards, map out job requirements, etc. Be reasonable, efficient, mindful.
Instead they panicked that I was going to walk out and leave in a couple days. They rushed to find anybody with basic knowledge of a computer from the local staffing agency and threw them onto my lap with little consideration. Now I'm trying to train a person with no experience and fairly rudimentary knowledge. Plus they dumped all these demands for an encyclopedia worth of how-tos, procedures, vendor notes, troubleshooting guides, etc.
It's funny but also sad. One day the new person was there and I was at home, sick or something. A shared network connection in Windows got disconnected which made an app pop up an error. New person tried to troubleshoot the app, perhaps not knowing the shared network drive existed. So boss asks if I've already written a specific procedure for this specific app when having this specific error caused by this specific problem.
I'm just like, no, I can't write a procedure detailing every conceivable error that can happen on every one of 50+ vendors we deal with, lol.
The IT person is supposed to know how to troubleshoot issues, not just read from a procedure book encyclopedia written by the previous IT person!
Man what a pain! I needed to do this for my previous employer and it was hard to deal with it. Ended up creating a 60 page manual for staff and about the same for the IT Admin person taking over me.
-
@dbeato said in Finally leaving my job, and it's just as annoying as I thought it would be:
@guyinpv said in Finally leaving my job, and it's just as annoying as I thought it would be:
@DustinB3403 said in Finally leaving my job, and it's just as annoying as I thought it would be:
@guyinpv said in Finally leaving my job, and it's just as annoying as I thought it would be:
And all I wanted to do was open up a conversation so they could start looking for a replacement. I wasn't expecting a circus.What were you realistically expecting?
To begin a detailed, thought-out, plan of finding a competent replacement. Start looking at quality job boards, map out job requirements, etc. Be reasonable, efficient, mindful.
Instead they panicked that I was going to walk out and leave in a couple days. They rushed to find anybody with basic knowledge of a computer from the local staffing agency and threw them onto my lap with little consideration. Now I'm trying to train a person with no experience and fairly rudimentary knowledge. Plus they dumped all these demands for an encyclopedia worth of how-tos, procedures, vendor notes, troubleshooting guides, etc.
It's funny but also sad. One day the new person was there and I was at home, sick or something. A shared network connection in Windows got disconnected which made an app pop up an error. New person tried to troubleshoot the app, perhaps not knowing the shared network drive existed. So boss asks if I've already written a specific procedure for this specific app when having this specific error caused by this specific problem.
I'm just like, no, I can't write a procedure detailing every conceivable error that can happen on every one of 50+ vendors we deal with, lol.
The IT person is supposed to know how to troubleshoot issues, not just read from a procedure book encyclopedia written by the previous IT person!
Man what a pain! I needed to do this for my previous employer and it was hard to deal with it. Ended up creating a 60 page manual for staff and about the same for the IT Admin person taking over me.
Does stuff like that happens when it’s a one person IT position?
-
@scottalanmiller said in Finally leaving my job, and it's just as annoying as I thought it would be:
That's a state level law and I'm pretty sure nowhere in the US makes you give notice. If they do, it's an extreme exception.
Doctors have this. xxx number of days, to make sure notes on patients are passed over. In reality this isn't really a big deal with modern EMR's, and in most practices.
-
@guyinpv Time to give that notice and go. zero reason to stay now, you've been replaced.
-
@StorageNinja said in Finally leaving my job, and it's just as annoying as I thought it would be:
@scottalanmiller said in Finally leaving my job, and it's just as annoying as I thought it would be:
That's a state level law and I'm pretty sure nowhere in the US makes you give notice. If they do, it's an extreme exception.
Doctors have this. xxx number of days, to make sure notes on patients are passed over. In reality this isn't really a big deal with modern EMR's, and in most practices.
How do they handle if doctors get sick or can't come in?
-
@black3dynamite said in Finally leaving my job, and it's just as annoying as I thought it would be:
@dbeato said in Finally leaving my job, and it's just as annoying as I thought it would be:
@guyinpv said in Finally leaving my job, and it's just as annoying as I thought it would be:
@DustinB3403 said in Finally leaving my job, and it's just as annoying as I thought it would be:
@guyinpv said in Finally leaving my job, and it's just as annoying as I thought it would be:
And all I wanted to do was open up a conversation so they could start looking for a replacement. I wasn't expecting a circus.What were you realistically expecting?
To begin a detailed, thought-out, plan of finding a competent replacement. Start looking at quality job boards, map out job requirements, etc. Be reasonable, efficient, mindful.
Instead they panicked that I was going to walk out and leave in a couple days. They rushed to find anybody with basic knowledge of a computer from the local staffing agency and threw them onto my lap with little consideration. Now I'm trying to train a person with no experience and fairly rudimentary knowledge. Plus they dumped all these demands for an encyclopedia worth of how-tos, procedures, vendor notes, troubleshooting guides, etc.
It's funny but also sad. One day the new person was there and I was at home, sick or something. A shared network connection in Windows got disconnected which made an app pop up an error. New person tried to troubleshoot the app, perhaps not knowing the shared network drive existed. So boss asks if I've already written a specific procedure for this specific app when having this specific error caused by this specific problem.
I'm just like, no, I can't write a procedure detailing every conceivable error that can happen on every one of 50+ vendors we deal with, lol.
The IT person is supposed to know how to troubleshoot issues, not just read from a procedure book encyclopedia written by the previous IT person!
Man what a pain! I needed to do this for my previous employer and it was hard to deal with it. Ended up creating a 60 page manual for staff and about the same for the IT Admin person taking over me.
Does stuff like that happens when it’s a one person IT position?
No, things like this happen when the company is shit.
-
@guyinpv said in Finally leaving my job, and it's just as annoying as I thought it would be:
Instead they panicked that I was going to walk out and leave in a couple days. They rushed to find anybody with basic knowledge of a computer from the local staffing agency and threw them onto my lap with little consideration. Now I'm trying to train a person with no experience and fairly rudimentary knowledge. Plus they dumped all these demands for an encyclopedia worth of how-tos, procedures, vendor notes, troubleshooting guides, etc.
This is kinda hilariously common in SMB land, but did you stop and think that maybe, just maybe they don't know what it costs for the skills they need to hire for? What is the pay rate they a re paying for the job? If you are expecting someone who knows Sysadmin work, Networking, End user support, application troubleshooting, vendor management/bidding etc and they hired at 40K a year then you are going to get this no matter what. When I worked i n consulting many times I saw management want to fire/replace people and I had to get them to stop and realize that when you pay 1/2 the going rate, you get 1/10th the expected outcome. When a tenured employee is leaving for greener pastures that doesn't mean that for the same rate (or even a good bit more) they will get a perfect 100% drop in replacement quickly. You've described management as difficult to work with, and not placing value in IT.
-
Why would anyone good WANT to work for that person? (Might be a lot of candidates just nope their way out of the interview).
-
Why would that management pay the rate they need to?
I mean my dude, at a certain point you gotta ask yourself why you think this isn't the outcome that's going to happen.
FWIW I've seen people handcuffed to a job and it's done a lot differently.
-
Pay more than the going rate for the job and the rest of the market. (Shockingly this is the one thing Netflix does on staff management that no one talks about!).
-
Deferred compensation. If I left tomorrow. I would forfeit my bonus for the half, my outstanding RSU's, my unvested ESPP (well I'd get face value, but no gainz). This pile of loot is enough to make me think twice about leaving, demand a signing bonus to offset it (Making me less attractive to future employees trying to pick me up cheap), or at least force me to time my exit for maximum vestment on the way out. I've seen someone find a new job and take 6 months to leave for this reason.
-
Perc that are not standard like unlimited vacation, 6 months maternity/paternity etc.
-
-
@scottalanmiller said in Finally leaving my job, and it's just as annoying as I thought it would be:
How do they handle if doctors get sick or can't come in?
It's like a 30 day transition in theory but I"ve never heard of that being enforced. I suspect that has more to do with niche surgical practices.
Doctors can reach the EMR from home and put in notes. For in patient care whoever is coming off call on the weekend calls whoever is taking over and does a transfer of knowledge over the phone on top of the notes.
It's considered unethical in medicine to just "Dump" someone with an existing condition that you began treatment on without making sure someone else picks them up. Example.... can't set a central line and then as a practice not take it out.
-
@scottalanmiller said in Finally leaving my job, and it's just as annoying as I thought it would be:
@Dashrender there's also a value in providing a benefit, employee retention is an important metric which translates to dollars. And a car is so much more than a coffee machine.
Higher pay retains people too, and better I'd argue. I'll take pay over a car any day, in fact, I'd rather not have a car at all.
I have a car (Drive maybe 1800 miles a year on it?). I just use Uber for work (Have platinum status lol) for work. I earn the points and can take calls and get things done on the way to the meeting/airport etc.
The problem with a company car is I'm on the hook for maintaining it on some level more than likely (Unless you have fleet services), There are limits to how I use it (Can my kids ride in it?, Can I take it out of town?), the car might also be a car I don't like to drive (Ford Ranger, with no stereo) or really want.
-
@StorageNinja said in Finally leaving my job, and it's just as annoying as I thought it would be:
@scottalanmiller said in Finally leaving my job, and it's just as annoying as I thought it would be:
How do they handle if doctors get sick or can't come in?
It's like a 30 day transition in theory but I"ve never heard of that being enforced. I suspect that has more to do with niche surgical practices.
Doctors can reach the EMR from home and put in notes. For in patient care whoever is coming off call on the weekend calls whoever is taking over and does a transfer of knowledge over the phone on top of the notes.
It's considered unethical in medicine to just "Dump" someone with an existing condition that you began treatment on without making sure someone else picks them up. Example.... can't set a central line and then as a practice not take it out.
It's being hit by a bus that I'm talking about. Where the doctor has no choice.
-
@scottalanmiller said in Finally leaving my job, and it's just as annoying as I thought it would be:
It's being hit by a bus that I'm talking about. Where the doctor has no choice.
Ahhh for that? EMR, as well as the service they are on should have had "rounds" where the team was briefed on the patients current steps. If it's private practice new person will do a full workup.
-
@StorageNinja said in Finally leaving my job, and it's just as annoying as I thought it would be:
@scottalanmiller said in Finally leaving my job, and it's just as annoying as I thought it would be:
It's being hit by a bus that I'm talking about. Where the doctor has no choice.
Ahhh for that? EMR, as well as the service they are on should have had "rounds" where the team was briefed on the patients current steps. If it's private practice new person will do a full workup.
That's more what I would expect, and the same from IT. Sure documentation has to be minutes or hours behind sometimes. But really never more than a day at an extreme.
-
-
