Someone sent me a minion laugh audio file yesterday morning. I have now made it my ring tone. So during the day I keep my sound off on my phone but turn it back on after 5pm. Last night my phone rang and made me jump and then laugh I almost didn't answer the phone in time
@ajstringham yeah kinda.....
Now who coulda done something like that...I wonder...
I'd love to have more women in IT! Level the playing field for us really geeky guys! Lol
Ahh yes A.J. sounds fun, that's why you need to expedite getting GF
Or boyfriend... what ever keeps the boat floating....
Wait.. what? BF joke
Ryan, I'm straight tyvm...
You're welcome very much
A few years ago, I was recovering from burnout and took a helpdesk position. It was low-stress, low-workload, and extremely relaxing. Sometimes taking a step back isn't all that bad to do. If I hadn't been recruited away, I'd likely still be there.
That's kinda what I did with my current job, went from an MSP, to Goodwill, to another MSP to help desk / internal IT for a single office. All involved IT help desk in some way except this job, where it's software support only. Been less stressed and given some room to move and do things but I miss having projects and different environments.
I was thinking as a professional resume.
This is all I use it for as well. With every job I've gotten, the hiring manager and/or HR made a comment about having a nice LinkedIn page. I've only gotten 2 or 3 fake recruiters from it and a few referrals for new job openings. The rest of the site seems to be marketing crap.
@scottalanmiller sucked the lol right out of it with logic.
I don't think that hashtags do what you think that they do.
Yeah I'm noticing that. Is this a feature of the text editor?
It's markdown. Just standard markdown, nothing special.
Sorry for the delay, Scott, but I finally shared my resume with you. If you could look at it, when you get a chance, I'd appreciate it.
I got it. Might not get to look at it until the weekend. We will see.
We had a fairly difficult time finding someone that was properly qualified for a network admin position within our company. We had hundreds of applicants, but very few that were qualified for the position
That's what we keep seeing. Lots of people out of work but most out of work for a reason. Unskilled or "mis" skilled - having skills that are over saturated and lacking the ones needed in the market. Or being in the wrong location and unwilling to relocate.
My husband and I have been back at school for just over 9 months, now. We're getting our degrees in IT, but I am heavily considering project management, to be more flexible, in case IT "just isn't what it used to be". We are in our project management cluster now (the adjunct professor is a freakin' rockstar in PM), so I'll know in a month or two if I'm cut out for this stuff.
Congrats on school - I sort of "fell into" IT, but if I had to do it over again, I'd probably be a musician, zookeeper, or humanitarian aid worker.
Have you ever told someone you'd work a ticket for them over the weekend because that's when you had time?
No, but I'll often tell them I'd ***try ***to work a ticket for them over the weekend. If I was unable to do to what I said I would (which happens regularly), I'll just let them know that something else came up and I didn't find the time. I never promise anything - either at home or at work. The best I'll say to a user is "if nothing else comes up then I will work on this at such and such a time". It's the same with my kids - instead of saying "I promise we'll go to the park this afternoon", I'll say "If we have time, we'll go to the park this afternoon". I never promise anything - life is too unpredictable.
As I was reading the OP, this is exactly what rang in my head - why on earth would you promise something to an end user that isn't your boss, and even then why do it? Best effort is the expectation that we should be trying to set, but not promises.
Like MS SQL Server, PostgreSQL is a full RDBMS. It's a hard core enterprise system that goes after drop in replacement with Oracle DB. Pretty much any enterprise software using a database lets you select between PostgreSQL, Oracle, Sybase and SQL Server if not many more like MySQL, MariaDB, DB2, etc.
MySQL is focused on lightweight web applications so is tuned differently than the others. PostgreSQL is the new darling for enterprise app development. It's old but really good.
Someday, maybe he will find this thread.
that is exactly what I was thinking. "hey dude, we were concerned about you" In case he makes it here.
I thought about posting a link to his Facebook profile, but I think that might be crossing the line of professionalism. At least there would be a picture to go on the milk carton when he's considered missing.
I have never taken a counter offer or even considered it. Think about it this way, if you are worth the salary they are countering with, why did they not pay you closer to that in the first place? I consider that an insult.
I agree with CB, this is a difficult situation. I suppose the best solution might be: interview for a position to get a gauge for your current market place value, If you get an offer but you really like the company you work for, visit with management and let them know you have done the research and need a raise. If they scoff you walk. If they say, OK Jim you've done your homework and we like you so here's your raise, then you turn down the other offer.
The unfortunate thing about this is that most companies won't give you the raise right then and there. They'll give you some kind of song and dance that it's not in the budget, etc, etc. Now this has left the company in one of two positions, a) they will try to acquire the needed budget to keep you, or b) they will start looking for your replacement.
I guess your best bet if they do anything other than simply say, OK, and sign a piece of paper stating you will get the raise on your next check, you kinda have to walk (ok turn in your two weeks notice).
I remember I have a lots of intern working with me for the past 3 years. So i used to teach them the following.
1.) Introduction to our environment. Since we have many operators in production area i explain to them regarding our process.What they are doing, the does and don't.Very simple but i am sure they will have an idea what exactly we are doing here.
2.)Basic introduction to our system, OS,network,etc.
3.) I will give them an instruction or documentation then later on i will ask them to try,or to follow the procedure in documentation.
4.) After few 2 or 3 days if i am confident that they can manage to answer basic questions from users i will let them assist operators.
Wow. Even in 1,000 person shops I've never seen desktop specialists wasted in paper changing chores.
Either lazy or ignorant or both, they are all welcome there (or at least were).
Multitasking is a great way to nibble at things without making solid progress in any of them. Humans are designed to work on one thing at a time. The key is breaking down things into manageable chunks that you can get through one at a time. That way, you can work on chunks of different projects, yet still be able to give each chunk your full attention. Some of what I say may sound familiar. It's part of the Getting Things Done method. For more information, check out http://gettingthingsdone.com. I've been a practitioner for 4 years, and it's turned my ability to handle workload right around.
And Change is inevitable in this area managing it separates the good from the better, and best.
And remember, as you go through change, so does everyone else. It isn't that change isn't tough, it's about it being relatively easier for us than for most people.