What Are You Doing Right Now
-
@wirestyle22 said:
Those are valid points. My reality is that there are gaps in my knowledge. I didn't go to a traditional school or anything like that.
Few have. Traditional school is worthless for IT. It's a negative... takes time away from the learning that you need to do. You can leverage it if you have it, but the time and effort come at a huge cost that can never really be overcome.
Traditional school creates gaps, it doesn't fill them. This sounds like you are looking for excuses rather than looking for opportunities.
[Tough Love]
-
@scottalanmiller said:
@wirestyle22 said:
Those are valid points. My reality is that there are gaps in my knowledge. I didn't go to a traditional school or anything like that.
Few have. Traditional school is worthless for IT. It's a negative... takes time away from the learning that you need to do. You can leverage it if you have it, but the time and effort come at a huge cost that can never really be overcome.
Traditional school creates gaps, it doesn't fill them. This sounds like you are looking for excuses rather than looking for opportunities.
[Tough Love]
Tough love appreciated. Not trying to make excuses I'm just explaining. I'll apply and see what happens. Worst case scenario I gain valuable experience.
-
@wirestyle22 said:
I tried to interview with CommVault and they started asking me specific CMD line commands I never use and host file editing, which I replied with "The only thing I really edit the host file for is to point to a different DNS and I've done that maybe one time in my life". They never called me back and basically stopped the interview there. I got pretty far with ABC like I said but that was more of a friendly conversation and ultimately they wanted someone with a lot of UNIX experience, which I basically have none. These experiences have kind of shaped my opinion of my knowledge.
So your takeaway here should be...
- Start learning PowerShell and if you get interviewed on CMD you throw your head back and laugh, mumble something about aging DOS era skills and do the thing that they want in PS.
- Start taking my UNIX admin course and do all of the stuff along with us as we do it. Get Linux running at home and get used to it.
- Keep interviewing and learning where you are weak and maybe get lucky when you find something.
-
@scottalanmiller said:
@wirestyle22 said:
I tried to interview with CommVault and they started asking me specific CMD line commands I never use and host file editing, which I replied with "The only thing I really edit the host file for is to point to a different DNS and I've done that maybe one time in my life". They never called me back and basically stopped the interview there. I got pretty far with ABC like I said but that was more of a friendly conversation and ultimately they wanted someone with a lot of UNIX experience, which I basically have none. These experiences have kind of shaped my opinion of my knowledge.
So your takeaway here should be...
- Start learning PowerShell and if you get interviewed on CMD you throw your head back and laugh, mumble something about aging DOS era skills and do the thing that they want in PS.
- Start taking my UNIX admin course and do all of the stuff along with us as we do it. Get Linux running at home and get used to it.
- Keep interviewing and learning where you are weak and maybe get lucky when you find something.
Agreed. Appreciate the advice.
-
@wirestyle22 said:
Tough love appreciated. Not trying to make excuses I'm just explaining. I'll apply and see what happens. Worst case scenario I gain valuable experience.
I spent a huge portion of my career interviewing two to five times a week. You get good at it. Eventually it feels like cheating. I interview way above my skill level. I'm relaxed, confident, conversational. I can generally steer interviewers as I need to make a point. I can turn weakness into strength.
Getting interviewing to a point where you are napping between people is a good thing
-
@scottalanmiller said:
@wirestyle22 said:
Tough love appreciated. Not trying to make excuses I'm just explaining. I'll apply and see what happens. Worst case scenario I gain valuable experience.
I spent a huge portion of my career interviewing two to five times a week. You get good at it. Eventually it feels like cheating. I interview way above my skill level. I'm relaxed, confident, conversational. I can generally steer interviewers as I need to make a point. I can turn weakness into strength.
Getting interviewing to a point where you are napping between people is a good thing
I'll get there
-
Good, old thread that I forgot about got mentioned today. Good reading about RAID comparisons.
https://community.spiceworks.com/topic/352280-obr10-vs-raid6-metrics
-
Just fixed the chrome Roboto font on my laptop. It's been bothering me for a while just too lazy to fix it.
-
We need to make a list of all of the things that people never understand in IT:
- They always say database but mean an application. And just as likely one that doesn't even use a database as one that does.
- Email. People never know how email works and make some really weird assumptions about it (like if you block port 25, your web pages looking at email systems will stop working.) How many IT people actually confuse email on their network with web pages?
-
@scottalanmiller said:
We need to make a list of all of the things that people never understand in IT:
Why do we expect non-IT staff to understand our stuff? Just make your list "all the things" and be done with it.
I'm stoked if they can convey some form of "thingy over there no longer works" - they're paid to do their job not mine.
How often do you go to your car mechanic and say "PCV valve isn't venting and it's causing excessive pressures which is dropping my oil pressure and resulting in engine wear and poor fuel mileage" - it'd be more like "somethings weird man, there's no noise but it's not running like it usually does" if you're very lucky.
-
@MattSpeller said:
@scottalanmiller said:
We need to make a list of all of the things that people never understand in IT:
Why do we expect non-IT staff to understand our stuff? Just make your list "all the things" and be done with it.
I'm stoked if they can convey some form of "thingy over there no longer works" - they're paid to do their job not mine.
How often do you go to your car mechanic and say "PCV valve isn't venting and it's causing excessive pressures which is dropping my oil pressure and resulting in engine wear and poor fuel mileage" - it'd be more like "somethings weird man, there's no noise but it's not running like it usually does" if you're very lucky.
We should make vocabulary lists for our actual users
-
@MattSpeller said:
Why do we expect non-IT staff to understand our stuff?
I'm talking about IT pros.
-
@scottalanmiller I think this topic will be as popular as your Linux Admin course.
-
Hey. I'm sure I need it lol
-
Just about an hour until I head south to the big city, for smoky dive bar dinner and a comedy show. Randy and Mr. Lahey from Trailer Park Boys, to be exact.
-
@RojoLoco said:
Just about an hour until I head south to the big city, for smoky dive bar dinner and a comedy show. Randy and Mr. Lahey from Trailer Park Boys, to be exact.
I mean...nobody wants to admit they ate 9 cans of ravioli
-
@wirestyle22 looks like they were having some kind of crazy liquor and cheeseburger party....
-
@RojoLoco said:
@wirestyle22 looks like they were having some kind of crazy liquor and cheeseburger party....
I live in my car. My car is my home. Cops pull you over in your home how can that be open liquor?
-
@wirestyle22 said:
@RojoLoco said:
@wirestyle22 looks like they were having some kind of crazy liquor and cheeseburger party....
I live in my car. My car is my home. Cops pull you over in your home how can that be open liquor?
If I can't smoke and swear, I'm f@cked.
-
insert grumbling about shopping online and getting the $CDN shaft
