Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Locked thread
AlternateAccount
Apr 25, 2005
FYGM

Misogynist posted:

You were under no obligation to sign anything just because he asked you, by the way. It may put you in a worse position as you try to collect evidence of the amount of unpaid work you actually did for this guy.

This is a bit of good advice. If you're getting bounced out or quitting and the terms of your separation are not what you want, don't sign poo poo. No non-competes, no severance agreements, no NOTHING. Those signatures are probably your last bit of leverage that doesn't involve going to court.

Adbot
ADBOT LOVES YOU

The Dreamer
Oct 15, 2013

Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn

Bob Morales posted:

What would a 'masters in IT' even be? MIS is for people who 'like computers' but can't program, right?

My MIS program was supposed to involve actual programming (which is why I chose it) but the instructor that taught it got tired of whiny business students bitching about how "hard" programming is and that it was stupid that they had to learn it at all for a "business degree". So the one class basically became how to pull reports from a database using Crystal Reports and other Visual Studio tools. The other got changed to a SDLC class. The classes were still called Introduction to Programming and Intermediate Programming though.

I probably should have switched majors right then and there but I was stupid and held on until the end (what are sunk costs?). I don't think I learned any real marketable skills at all with my MIS program.

CatsOnTheInternet
Apr 24, 2013

BEEEEAAOOOORRRRRRRW BEEEBEAAAAAOOOORRWW
My MIS program was actually pretty great, but they've since made it stupid. It was a solid blend of coding, and learning how to configure + administer almost anything. ESX (GSX at the time,) AD, BIND, Squid, we did it all. Then towards the end we started learning the management side, which helped me understand you work for a business with actual goals; you're not just playing with toys.

A few years, ago they forked the technical courses into another degree program (Computer Networking) which is nearly 100% technical. The MIS program today is basically a business degree with a passing mention of the OSI model.

Stupor Mundi
Jan 10, 2008
Filil Hobenstaufenin osculamini asinum meum.

Bob Morales posted:

What would a 'masters in IT' even be? MIS is for people who 'like computers' but can't program, right?

My MIS Bachelors program focuses on exactly what psydude said -- systems integration, analysis and engineering. It also includes 3000 and 4000 level finance (not easy) courses, management, organizational behavior and project management. And while it's certainly not a computer science degree there are definitely some challenging technical courses. For instance, I was required to take an intro to algorithm design (which was language independent, essentially a math/logic course), and a course in the programming language of my choice. The program also requires an introductory SQL course and an upper-level database design course. It's not a light-weight program by any means, but obviously it's not as technically challenging as a university CS program.

ZetsurinPower
Dec 14, 2003

I looooove leftovers!
My Computer Informations System bachelors program was part of the business college, and it was a watered down business curriculum (1st/2nd level courses are the deepest you'll go) mixed with a watered down IT curriculum. You dabble and get hands on experience with some technical stuff, lots of conceptual experience and SDLC/project management type stuff, but nothing substantial enough to get a job without some real experience. I felt bad for the people who were obviously in the program because they "heard there are jobs in computers" but had no technical inclination, they are probably working a call center somewhere wondering what happened.

Its not like a CS degree where you gain practical skills, graduate, and go directly into a development position. But to its favor, you are much more marketable and can steer your career into a variety of directions.

Paladine_PSoT
Jan 2, 2010

If you have a problem Yo, I'll solve it

Dude, even in the US if you quit they have no more than 72 hours to settle up with you. The Netherlands has better labor laws than the US, right? LAWYER NOW.

Docjowles
Apr 9, 2009

My undergrad was "Information Science" which I liked pretty well. I started out pure CS but decided a few years in that I didn't want to be a full-time dev and the admin/ops side of the house sounded much more fun. Thankfully the first couple years of IS were almost a complete overlap with the beginning of CS so I didn't even end up graduating late.

The program was kind of a mashup of all the things people are describing. Intro CS programming courses, with a lot of the non-hardcore-coding electives like UI Design, Database 101 and Data Mining made mandatory. Then instead of continuing into advanced math or writing compilers, you took some courses in technical writing, psychology, business and experimental design with the goal of learning to use your technical know-how to solve actual business problems and--gasp--work with people.

I don't recall any courses on how to administrate Windows/Linux/VMware/whatever and honestly I'm kind of glad. Products come and go, if I wanted that kind of education I could just grab a couple certs and save myself a fortune in tuition. Learning actual CS fundamentals and all of the social science and business stuff will last a lifetime and serve me in a wide range of jobs. I'm also of the opinion that within the next decade, a sysadmin who can't code and code well will be out on the street or busted down to helldesk/NOC grunt work, so I'm glad that half of the degree was so CS-heavy.

CloFan
Nov 6, 2004

Congratulations on quitting, Sefal! It was definitely in your best interests. I'll repeat what others have already said, lawyer up and call that accountant today with a figure.

I need to grow a spine like you. I'm still expecting a promotion (Jan 1... then Feb1..now end of Feb), and I spoke to my boss today about compensation for it. He said he didn't expect HR to come up with a payscale that was appreciably more than I'm making now. He's wrong, but I didn't call him on it. Bottom number for my description in my state is 20k more than I'm making, and I think that's part of the reason it hasn't happened yet. He also outright denied my request for additional PTO - currently at 12 days plus federal holidays, requested 17. It's bullshit, but I don't plan to be here too much longer.

On the upside, the CEO gave me a $1500 bonus today for closing up some audit tracking items!

Moey
Oct 22, 2010

I LIKE TO MOVE IT

Docjowles posted:

My undergrad was "Information Science"

I had a very similar undergrad. Information Systems: Analyst and Design. Dabbled in just about the same stuff. Never had any courses on administration or anything. Programming, database, UI, project management...

dogstile
May 1, 2012

fucking clocks
how do they work?
I expect a Sysadmin will have to know how to use a scripting language and how to write batch files at the very least in the future. I'm not to sure what other coding a Sysadmin would really need to do. I've got SQL, C++, Javascript, HTML/CSS and VB down as stuff that i'm quite comfortable sitting down, refreshing my memory on and doing something simple, but as far as i've seen i've not really seen any Sysadmin work with code aside from a bit of fiddling in powershell (which, while i'm not comfortable listing it down as something i can do, i'm definitely playing with it right now).

The "IT" course my uni offered was basically a business course with light coding thrown in to keep people on edge. They skipped over any specific programs/products, much like others i've read about and made it more about "this is how a computer works and this is how you can make that computer work within a business".

evol262
Nov 30, 2010
#!/usr/bin/perl

dogstile posted:

I expect a Sysadmin will have to know how to use a scripting language and how to write batch files at the very least in the future. I'm not to sure what other coding a Sysadmin would really need to do. I've got SQL, C++, Javascript, HTML/CSS and VB down as stuff that i'm quite comfortable sitting down, refreshing my memory on and doing something simple, but as far as i've seen i've not really seen any Sysadmin work with code aside from a bit of fiddling in powershell (which, while i'm not comfortable listing it down as something i can do, i'm definitely playing with it right now).

:windowslyfe:

If you're an admin on non-Windows systems and you don't know how to script, you're doing yourself a woeful disservice. It's pretty much impossible to be a *nix admin and not know perl or python and shell, and the better admins tend to know at least a little C (historically, this is less necessary now).

dogstile
May 1, 2012

fucking clocks
how do they work?
Yeah, that makes sense. I've not really played with many other systems, I need to get a lab going and give it a go.

ZetsurinPower
Dec 14, 2003

I looooove leftovers!

dogstile posted:

The "IT" course my uni offered was basically a business course with light coding thrown in to keep people on edge. They skipped over any specific programs/products, much like others i've read about and made it more about "this is how a computer works and this is how you can make that computer work within a business".

if you're not already technically proficient or get an internship, it kind of leaves you in a lurch when its job hunting time. I think these programs should require a couple of certs before graduation. My intro to Networking prof allowed us to skip the final project if we got our Network+ cert, which I think is a cool way of doing it.

Docjowles
Apr 9, 2009

dogstile posted:

I expect a Sysadmin will have to know how to use a scripting language and how to write batch files at the very least in the future. I'm not to sure what other coding a Sysadmin would really need to do. I've got SQL, C++, Javascript, HTML/CSS and VB down as stuff that i'm quite comfortable sitting down, refreshing my memory on and doing something simple, but as far as i've seen i've not really seen any Sysadmin work with code aside from a bit of fiddling in powershell (which, while i'm not comfortable listing it down as something i can do, i'm definitely playing with it right now).

The "IT" course my uni offered was basically a business course with light coding thrown in to keep people on edge. They skipped over any specific programs/products, much like others i've read about and made it more about "this is how a computer works and this is how you can make that computer work within a business".

Yeah sorry that was a flippant remark. I definitely didn't mean "needs to know how to write 50,000 lines of Java and create baller GUI applications" or anything. To an extent it will depend on the size of your organization, how many machines an admin is expected to manage, and what you want to accomplish. But if you're managing more than a dozen boxes (number pulled out of my rear end) and not automating that work with scripting you're probably wasting a lot of time doing things in a manual, slow, error-prone way. Not to mention boring. Puppet/Chef/etc manifests are a form of code, as are API calls to manage your AWS cloud, and I can't imagine life without them.

There's a difference between banging out a batch file (or shell script in the *nix world) that "works" and writing readable, maintainable, reusable code. Often "scripting" is used as an alias for a lovely quick hack even if that "script" is production-critical. Likewise being able to read and modify someone else's code, whether it's an internal script or an open source tool that's bugging out, is incredibly valuable. That's more what I was getting at. Not that you need to be able to code as well and prolifically as a full-time software dev.

Vulture Culture
Jul 14, 2003

I was never enjoying it. I only eat it for the nutrients.

dogstile posted:

I expect a Sysadmin will have to know how to use a scripting language and how to write batch files at the very least in the future. I'm not to sure what other coding a Sysadmin would really need to do. I've got SQL, C++, Javascript, HTML/CSS and VB down as stuff that i'm quite comfortable sitting down, refreshing my memory on and doing something simple, but as far as i've seen i've not really seen any Sysadmin work with code aside from a bit of fiddling in powershell (which, while i'm not comfortable listing it down as something i can do, i'm definitely playing with it right now).

The "IT" course my uni offered was basically a business course with light coding thrown in to keep people on edge. They skipped over any specific programs/products, much like others i've read about and made it more about "this is how a computer works and this is how you can make that computer work within a business".
In some ways, that's ended up closer to the IT needs of a modern business than it did than when these programs were first formulated decades ago. The push towards the cloud has removed the need for a lot of businesses to maintain in-house technology expertise in domains like running their own email, CRM (seriously, who runs hosted Dynamics instead of using Salesforce these days?), or website hosting systems. Hiring sysadmins to maintain a handful of internal application servers just isn't worth the cost/risk anymore. What we're left with (and I'm dramatically oversimplifying here) is a handful of different IT skillsets diverging from the desktop support/server admin model that we've seen for most of corporate IT's history:

  • People who run the hosted SaaS applications: operations here is the closest you'll get to a traditional non-coding sysadmin because there's always plenty of problems to solve
  • People whose job is to evaluate and integrate platforms in a way that gives the business some kind of competitive advantage (similar to traditional ERP developer/admins and business analysts today)
  • People whose job is to help users within the business understand how to use those tools effectively (tech trainers, customer advocates/client service representatives, and traditional desktop support)
  • People who are so skilled at automation that, for some subset of scalable applications, the economics swing back in favor of the business running its own systems in-house
  • People who are focused on analysis, visualization and interpretation of data (data scientists) and can use these insights to deliver different kinds of competitive advantage

The bottom line is that businesses are interested in people who can help them win. Executives are interested in having staff whose contributions can be linked directly to the success or failure of business initiatives, rather than $140,000/year plumbers.

evol262 posted:

:windowslyfe:

If you're an admin on non-Windows systems and you don't know how to script, you're doing yourself a woeful disservice. It's pretty much impossible to be a *nix admin and not know perl or python and shell, and the better admins tend to know at least a little C (historically, this is less necessary now).
evol262 is using very muted language here, so I'll take off the kid gloves and post my own experiences: I have never, not one time, hired a sysadmin who couldn't code -- Linux, Windows, or even enterprise storage -- and I've never regretted the outcome. Don't underestimate the efficiency and cost savings of a storage guy who can reverse-engineer the performance data collection infrastructure on a proprietary storage array and figure out how to get it to dump more granular metrics to Graphite instead.

Vulture Culture fucked around with this message at 20:32 on Feb 14, 2014

dogstile
May 1, 2012

fucking clocks
how do they work?

ZetsurinPower posted:

if you're not already technically proficient or get an internship, it kind of leaves you in a lurch when its job hunting time. I think these programs should require a couple of certs before graduation. My intro to Networking prof allowed us to skip the final project if we got our Network+ cert, which I think is a cool way of doing it.

Yeah, I went and took the computer science course instead, which gave me some Cisco certs. I liked the idea of learning how to apply things to businesses, but I really would prefer to know the finer details rather than the basic knowledge. When I learn something, if I don't know it in depth i'm not satisfied because occasionally something will go wrong and I won't know why. When I know something in depth that doesn't really happen.

In regards to the post about never hiring an admin who can't code, it looks like I better keep my skills crisp then. Which is fine by me, i'm not content to sit at a helpdesk for a piddly £19,000 or so a year.

dogstile fucked around with this message at 20:37 on Feb 14, 2014

Bob Morales
Aug 18, 2006


Just wear the fucking mask, Bob

I don't care how many people I probably infected with COVID-19 while refusing to wear a mask, my comfort is far more important than the health and safety of everyone around me!

computer science = cisco certs?

skipdogg
Nov 29, 2004
Resident SRT-4 Expert

My brothers CS covered some Cisco stuff, not sure if he took the classes as an elective or not though. He learned Linux/CUDA/Java/Cisco in his program.

QuiteEasilyDone
Jul 2, 2010

Won't you play with me?
A job offer came in! :yotj:

45K for a very very Jr. Sysadmin position. Considering I have less than a years experience in the field of IT and this is an effective doubling and change of my current rate, I'm going to chalk this off as a win.

Docjowles
Apr 9, 2009

QuiteEasilyDone posted:

A job offer came in! :yotj:

45K for a very very Jr. Sysadmin position. Considering I have less than a years experience in the field of IT and this is an effective doubling and change of my current rate, I'm going to chalk this off as a win.

Congrats! :cheers:

bull3964
Nov 18, 2000

DO YOU HEAR THAT? THAT'S THE SOUND OF ME PATTING MYSELF ON THE BACK.


It just seems a really odd thing to have in CS coursework. We didn't have anything vendor specific in any of our work.

CS 101 was C++ and CS 102 was Java. That changed the year I started our program ('97), in prior years it was CS 101 = C and CS 102 = C++.

Other than that, we did a good bit of assembly, SQL, and then there was one semester that hit just a ton of different languages including some really off the wall ones to expose us to different types.

One of the strangest was Occam2, concurrent computing was a difficult thing to wrap your head around at first.

The big sophomore project was to write an assembler in C++.

Alfajor
Jun 10, 2005

The delicious snack cake.
While the "goon in the well" makes sense without any kind of backstory, I googled anyway. This is a pretty fair description: http://pastebin.com/F83ZG2L6

quote:

The "goon in a well" is an analogy used throughout GBS and E/N to describe goons with horrible relationship problems who refuse to take good advice.

OP: "Help! HELP! I'm stuck in a well!!!"
Goons1-4: "Climb! Climb up and take our hands!"
OP: "I'm thinking I should dig... should I dig?"
Goon5: "NO! I was trapped in a well, and digging is a bad idea! Climb out!"
Goons6-8: "Were lowering ropes! Take hold of a rope!"
Goon9: "I've even tied a harness to the end of this one!"
OP: "I can feel the ropes, but I don't want to hold onto them... should I dig?"
Goon10: "No! If you dig, you'll hit water, and then you'll be proper hosed. I should know, I almost drowned."
OP: "I dug a little bit just now, and I haven't hit water. I'm gonna keep digging..."
Goons11-18: "No! Climb! Climb out!"
OP: "Guys, I'm seriously stuck in this well! Help! HELP!!!"
Goon19: "I was trapped in a well once. It took me two years, but I managed to build a climbing machine that pulled me to safety out of a well bucket and a pocket watch. I'm dropping the blueprints, extra buckets, and an assortment of pocket watches."
Goon20: "I've engineered a jet-pack that will rocket you to safety. Stay where you are and we'll lower it down!"
OP: "Thanks for your help, guys. I'm gonna keep digging. I'll find the Mines of Moria and I'll just walk to the surface."
**Goons1-20 piss in the well**
Goon21: "Guys, seriously... stop peeing in the well."
Goon22:"Yeah, like any of you guys have even seen a real well, you neckbearded, WOW-addicted shut-ins."

Sefal, please don't dig and lawyer up. And tell us more because :allears:

dogstile
May 1, 2012

fucking clocks
how do they work?

Bob Morales posted:

computer science = cisco certs?

It was a side thing it offered. If you wanted to do it, you could do it, they'd pay. The rest of it was actual computer science stuff, guess I didn't explain that well. Apologies.

psydude
Apr 1, 2008

Latin American Studies majors represent.

evol262
Nov 30, 2010
#!/usr/bin/perl

psydude posted:

Latin American Studies majors represent.

Yah. History major here. At least my program (mostly) wasn't about how badly Potosi and sugar farming hosed an entire continent

Fiendish Dr. Wu
Nov 11, 2010

You done fucked up now!
What's the procedure for handling another recruiter calling about the same position for which you've already accepted an offer from another recruiter?

GOOCHY
Sep 17, 2003

In an interstellar burst I'm back to save the universe!
There is no procedure. I mean, I guess you could try it if you wanted to piss off both recruiting companies and the client.

mattfl
Aug 27, 2004

Fiendish Dr. Wu posted:

What's the procedure for handling another recruiter calling about the same position for which you've already accepted an offer from another recruiter?

Tell them you've already been submitted by another company.

Fiendish Dr. Wu
Nov 11, 2010

You done fucked up now!

mattfl posted:

Tell them you've already been submitted by another company.

That's what I did.

As soon as I found out it was for literally the same position I told them I start in 2 weeks through another company.

They were also offering $5/hr less!

Edit:

GOOCHY posted:

There is no procedure. I mean, I guess you could try it if you wanted to piss off both recruiting companies and the client.

That's why I asked, I want to make sure I don't piss anybody off and also trying to cover my rear end.

Fiendish Dr. Wu fucked around with this message at 23:49 on Feb 15, 2014

MW
May 20, 2001

"Nooooooooo!?"

Sefal posted:

Update! I quit.

Just to clarify, you worked for 11 months without pay?

Doctor_Fruitbat
Jun 2, 2013


So if, say, I was looking to get into a sysadmin role, and was currently boning up for the A+ (I pretty much know enough to pass, I just need to save up the moneys), what cert or language/skills should I look into as a next step? By which I mean the most generally useful/appealing to employers.

I'm fairly technically proficient already and will shortly be starting on the new tablet support team/minor helldesk role at work (still better than the office work I'm currently doing) and I've finally worked up the enthusiasm to apply myself to getting some actual qualifications, but I am really skittish and unsure about applying myself unless I have a concrete idea of what route to chuck myself down. I thoroughly enjoy tinkering with both hardware/software and ruining all my tech in the name of funsies but haven't much enthusiasm for full-on coding, if that helps at all.

I did have a job offer for a role installing and troubleshooting hospital IT equipment until about a week ago, but it's fallen through in favour of someone more qualified, so you can imagine why I'm asking.

Fake edit: What does :yotj: actually mean? The 'otj' I can guess at, but the y? Yomp? Yodel? Yakketysax?

Doctor_Fruitbat fucked around with this message at 14:02 on Feb 16, 2014

deedee megadoodoo
Sep 28, 2000
Two roads diverged in a wood, and I, I took the one to Flavortown, and that has made all the difference.


Doctor_Fruitbat posted:

Fake edit: What does :yotj: actually mean? The 'otj' I can guess at, but the y? Yomp? Yodel? Yakketysax?

Year of the Job. I believe it started a few years back when a bunch of people in this thread all got sick of their jobs and made it their mission to look for something new. Now a lot of people use the phrase "yotj-ing" to mean looking for a new job.

evil_bunnY
Apr 2, 2003

YOTJ'ing means actually changing jobs, not merely looking.

QuiteEasilyDone
Jul 2, 2010

Won't you play with me?
Otherwise you can still be a goon in a well

Docjowles
Apr 9, 2009

Doctor_Fruitbat posted:

So if, say, I was looking to get into a sysadmin role, and was currently boning up for the A+ (I pretty much know enough to pass, I just need to save up the moneys), what cert or language/skills should I look into as a next step? By which I mean the most generally useful/appealing to employers.

Some great resources right here in SH/SC are the certification thread, the home lab thread and Dilbert's Goon User Groups. You should start by deciding if you want to focus on the Windows or Linux side of things*. There's pros and cons to both; there's arguably more Windows jobs out there but the companies that are hiring for Linux will really come after you because there are less qualified candidates out there.

For the Windows world, look into the MCSA: Windows Server certification track. PowerShell is the obvious programming language to learn, and Learn Windows PowerShell in a week of Lunches is an excellent resource for that. On the Linux side, the Red Hat certs are the most recognized and should be useful even if your job ends up not using a Red Hat distro. You'll want to look at the RCHSA and the RHCE certs. The choice of a programming language is less obvious here; at a bare minimum learn Bash shell scripting (this is more or less the Linux version of batch files). From there I'd suggest picking up Python, although Perl or Ruby aren't bad choices either. That you're comfortable with a language is more important than which language it is.

Understanding networking fundamentals is also extremely valuable, even if you have no desire to go deep down that career path. The CCENT or Network+ certs are a good level of detail for a sysadmin to know. At least be comfortable with the material even if you don't end up taking the exam.

I'll conclude by saying that while certs are useful and many jobs require (or effectively require) them, they are not the only way to go. I've been in IT for 8 years and a full-time sysadmin for 6 despite having zero certs. I started on an entry level helpdesk job at a smallish company and helped out the admin with simpler tasks when I had time. After a couple years of that and taking on increasingly challenging duties I was able to land a junior admin job and kept growing from there.

Also I am totally going to start reading YOTJ as "yakkitysax on the job" :yotj:

* I've intentionally left out virtualization/VMware. As a sysadmin you should absolutely know what virtualization is, but going from zero to full-time VMware admin is a tall order since you need to know so much about network, storage, the guest OS's, etc.

Docjowles fucked around with this message at 17:47 on Feb 16, 2014

Doctor_Fruitbat
Jun 2, 2013


Perfect stuff, thanks; I'm more of a Windows man so I'll start there. This thread has actually been really useful for getting my confidence up, particularly about the need for a good attitude etc. I'm good at first impressions and can definitely talk up my social skills and whatnot when needed. It's also confirmed my suspicions when a job listing seems to require a lifetime of broad experience just to get considered.

Dr. Arbitrary
Mar 15, 2006

Bleak Gremlin

Docjowles posted:

* I've intentionally left out virtualization/VMware. As a sysadmin you should absolutely know what virtualization is, but going from zero to full-time VMware admin is a tall order since you need to know so much about network, storage, the guest OS's, etc.

I can speak from personal experience, dive into virtualization if you really want to find out how much you don't know.

What the gently caress is an Eye Scuzzy?

Jedi425
Dec 6, 2002

THOU ART THEE ART THOU STICK YOUR HAND IN THE TV DO IT DO IT DO IT

Dr. Arbitrary posted:

What the gently caress is an Eye Scuzzy?




Seriously though, Virtualization is a fascinating area to look into, but it really does touch every other part of the traditional IT landscape. As a Network Admin I'm always happy to work with a good Virtual admin type; the good ones can always tell me exactly what they need and why, and if I need something from them they know just how to set it up for me.

Sepist
Dec 26, 2005

FUCK BITCHES, ROUTE PACKETS

Gravy Boat 2k
I usually end up telling the vmware guys what the problem is since I'm familiar with esx/vswitch/fiber interconnects, I should really add it to my resume.

Adbot
ADBOT LOVES YOU

Dark Helmut
Jul 24, 2004

All growns up

Fiendish Dr. Wu posted:

What's the procedure for handling another recruiter calling about the same position for which you've already accepted an offer from another recruiter?

I keel you.

  • Locked thread