Hello IT Community!
-
@scottalanmiller How do you define IT?
To me a programmer is doing IT, but development and not operations. -
@Pete-S said in Hello IT Community!:
@scottalanmiller How do you define IT?
To me a programmer is doing IT, but development and not operations.One of the big things this forum has said for years is that programming - a developer - is not IT. They are coders/developers. but they aren't managing systems/networks, etc in general.
-
@Dashrender said in Hello IT Community!:
@Pete-S said in Hello IT Community!:
@scottalanmiller How do you define IT?
To me a programmer is doing IT, but development and not operations.One of the big things this forum has said for years is that programming - a developer - is not IT. They are coders/developers. but they aren't managing systems/networks, etc in general.
Thanks, I think I understand but managing to me is IT Operations.
-
@Pete-S said in Hello IT Community!:
@Dashrender said in Hello IT Community!:
@Pete-S said in Hello IT Community!:
@scottalanmiller How do you define IT?
To me a programmer is doing IT, but development and not operations.One of the big things this forum has said for years is that programming - a developer - is not IT. They are coders/developers. but they aren't managing systems/networks, etc in general.
Thanks, I think I understand but managing to me is IT Operations.
I agree, managing systems, etc is IT operations, but programmers/coders/developers don't typically do that.
-
@flaxking said in Hello IT Community!:
Cross educated people are valuable, and IT/Dev is kind of standardly recognized. However, being a beginner in both doesn't fit that mold and can actually hurt your resume when trying to get into the field. If you highlight IT on a junior Dev position, it can look like you don't understand the position the job is for and your resume could get instantly tossed right there.
This is very true. For me, being both a developer and an IT guy has been hugely beneficial, but when I entered IT I did so without ever showing or talking about my development creds. The one helps me understand the other, but it's not part of my resume in any strong sense (it's there, but minimized.)
As a hiring manager, if you come to me and want to work in field X and show that you spent time in fields Y & Z instead of X, and don't have a really good story as to why (my dad's company needed my help and I wanted to help the family) then I'm going to assume that either you are confused and don't know any of these things, or that you are floundering going from career to career trying to find something that you like.
The worst, as a hiring manager, is getting someone in IT with a degree in Computer Science. CS is so dramatically unrelated to IT that I have to assume that either they were super confused going into college, super confused all the way through college, or spent all that time in college and only when done realized that they'd screwed up for all those years. None of those things bode well.
-
@Pete-S said in Hello IT Community!:
@scottalanmiller How do you define IT?
To me a programmer is doing IT, but development and not operations.IT is business infrastructure. IT delivers solutions to a business. Development produces products.
Programmers never consider themselves IT. IT people often lump them in, but they never do so themselves. It's extremely different skill sets in most cases. To IT, programmers are "just more end users." And to programmers, IT is their support people.
-
@Pete-S said in Hello IT Community!:
Thanks, I think I understand but managing to me is IT Operations.
Agreed, but IT is Operations. What IT isn't operations? Every role in IT is related to business operations. IT builds and operates the infrastructure of a business (which is why I prefer the term BI.)
Developers make tools. Tools that IT generally uses. IT are the customers of development. The business is a customer of IT.
-
If you spend time with developers, they're always shocked that anyone, including IT people, think that they are IT or related to IT. Programmers are like accountants, they use computers for everything that they do, but they use them like end users. They don't oversee them, they don't manage them, they don't really care about them.
Think about it like a racing team. One team (software engineers) designs the cars. Another team (IT) races the cars. Related? Of course, codependency. Can't race without a car, no reason to design a car without a driver. But the roles are very different. They serve a common goal, for sure, but in very different ways with different deliverables.
-
@scottalanmiller said in Hello IT Community!:
For me, being both a developer and an IT guy has been hugely beneficial
I bought the VB 95 book and taught myself visual basic back when it was new.
I subsequently swore I would never be a developer.
Then I spent 5 years developing bespoke software.
I'm quite happy to be not doing it anymore.
-
@scottalanmiller said in Hello IT Community!:
Think about it like a racing team. One team (software engineers) designs the cars. Another team (IT) races the cars. Related? Of course, codependency. Can't race without a car, no reason to design a car without a driver. But the roles are very different. They serve a common goal, for sure, but in very different ways with different deliverables.
I buy that but then that would put a whole lot of people outside IT. For instance a network engineer or an IT architect. Both are engineers / designers. They don't manage or operate anything, they design different aspects of the car.
-
@scottalanmiller said in Hello IT Community!:
@Pete-S said in Hello IT Community!:
@scottalanmiller How do you define IT?
To me a programmer is doing IT, but development and not operations.To IT, programmers are "just more end users." And to programmers, IT is their support people.
This is truth. Even for the product that the developers develop.
-
@Pete-S said in Hello IT Community!:
@scottalanmiller said in Hello IT Community!:
Think about it like a racing team. One team (software engineers) designs the cars. Another team (IT) races the cars. Related? Of course, codependency. Can't race without a car, no reason to design a car without a driver. But the roles are very different. They serve a common goal, for sure, but in very different ways with different deliverables.
I buy that but then that would put a whole lot of people outside IT. For instance a network engineer or an IT architect. Both are engineers / designers. They don't manage or operate anything, they design different aspects of the car.
Actually they do. They design the solution, not the product. Race cars aren't a perfect analogy. But they plan the route, so to speak. It's still "delivering product" vs "delivering solutions".
A network engineer and a network admin are definitely different hats. But designing a network and managing a network are extremely related tasks - very clear to see that they are both IT. One is configuring the system, one is making configuration changes. They both "work on network gear for a customer/business."
A programmer writing the OS or the GUI of a firewall is clearly a totally different animal. They don't need to know who the customer is, how it will be used, or know anything about IT at all.
-
@Pete-S said in Hello IT Community!:
They don't manage or operate anything, they design different aspects of the car.
Well, in the race car analogy, lol, yes. But in IT they don't.
Software Engineer: Writes the code that runs on a router or switch.
Hardware Engineer: Designs the chips and motherboards of the router or switch.
Network Engineer: Determines which routers or switches to buy, how many, and how to initially configure/deploy them.
Network Admin: Maintains and adjusts routers and switches that are already in use.The first two roles are software engineer and electrical engineer. They make products that you can sell and buy and neither would ever consider themselves IT in any way, and as IT we should naturally feel that they are very different.
The second two roles are IT. They don't make products, the configure and manage the products. The first two roles sit on the "Vendor side" of things . The second two sit on the customer side. The IT jobs are all about "using whatever products are right for our network and business needs", that's where they become IT.
