From admin to developer

Question

My friend recently moved from a high-level NOC post to a developer. Before that, he simply did reference information. He has no degree, only ordinary MIS / network certificates, and as far as I know, only messing with the code on the weekend. I see where in some scenarios having a good understanding of configurations, packages, users, OU, etc., It would be very useful for the developer.

My question is, how many full-time developers started this way? Even how many double people own the responsibility of a developer / system administrator / network administration?

Answer 1

I am sure this is a fairly common scenario. I spent 12 years in IT and I find that over time real income comes from a specialist (DBA, encoder, etc.) as opposed to a universal one (network administrator, support service).

This is actually the path of my career. I'm not quite a full time DBA or developer, but where I go.

I’m also willing to bet that the skills of the people I raised along the way (support desk support, network administrator, system analyst) will help me in my DBA / Developer career. Skills that I don’t feel, I would get if I jumped right into the coding framework.

Answer 2

Really. I think developers should know the platform for which they build software. If a developer previously worked as a system administrator, he will know how to integrate his software well. Some Windows-Desktop-App are related to the "integration smells" that come to my mind:

• The application does not start ordinary user privileges (run on properly protected corporate desktop computers? Oops!)
• Applications require write permission for all types of system folders (security? Oops!)
• App stores user settings in "non-standard" places, for example,% programfiles% (backup? Permissions? Oops!)
• The application does not provide installations that are installed without installation (deployment? Oops!)

Etc ..

A real sysadmin will never write software that has one of the above integrated odors. Actually.

Answer 3

This is quite common in small companies. I have done this for some time - developing software that we sold to customers, preserving the network and adding features to the database as needed for a manufacturing company with less than 20 employees.

You wear many hats in a small business.

But I started programming microcontrollers in high school, so I can’t say that this is where I started.

It is very useful to have knowledge of all these systems as a developer.

-Adam

Answer 4

The imposition of developers and administrators is quite a bit. Our latest admin is designed on the side to better understand what it helps. When he left, I became an administrator only because I was busy with the admin panel on the side to find out how my software is supported.

A broad understanding with several tricks is what I consider the best for any technical specialist. Then, with a little study, you can change to fit any need.

Answer 5

I saw this more when another programmer also “administrated” the servers, and sometimes the network. I was definitely in that position.

I would think that he can easily go the other way when the administrator can start programming systems, but in my experience this is not so often. Whenever I ask a server administrator or network user, do you program too? in most cases, the answer is no.

I think it might be easier for programmers to cross the line, because when you program the system, if you always have an admin available, you need to set up your own environment and usually enable server setup.

Answer 6

I started working as an NOC operator, eventually working as a senior network engineer. Over the last 2-3 years of my stay at my previous company, I raised my love for programming and began to learn everything I could in my time. Around 2005, I left the specified company for a small start-up and still works there as an administrator and main developer.

One problem that I impose on myself is not to change admins when the hat falls to satisfy programming problems. I have to force myself to code in such a way that any application that I make can be redistributed elsewhere with minimal privileges, despite the fact that I can do almost everything I want with our own servers. This is a fine line between performing both duties and performing one duty badly because of the needs of the other.

Answer 7

I'm here. Despite the fact that I studied with the code since childhood, my first full-time job was a system administrator, a database administrator, and other related roles. Subsequently, I worked full time as a developer, and now I am both a developer and security researcher. Also, I managed to populate M.Sc in CS. I believe that such transitions are possible and very useful, since you get a wider understanding of your area of ​​work.