4 ms·

Chances are when you work on a very small team you probably don't have a sysadmin at all. At the startup I work at, I do both and the more I work without a sysa

Chances are when you work on a very small team you probably don't have a sysadmin at all. At the startup I work at, I do both and the more I work without a sysadmin the more I appreciate the work they do! When we do have a dedicated sysadmin, at the very least he will be very appreciated by me, because I know he will be improving all the stuff I have done out of sysadmin ignorance.

sophacles 16y ago
I think it is extremely important to have at least one developer who has been a sysadmin in the past. One of my closest colleagues started his career as a sysadmin. At first I was a bit distrustful because he didn't have a lot of "real experience" or "education". But as I got to know him, I realized his sysadmin "spidey sense" was a godsend. He has a knack for knowing when things that should just work will in fact fall over. He also has a lot of deep OS and platform knowledge, so frequently when we would want to throw piles of code at something, he would suggest and OS tweak or similar to get the same end result. So yeah, sysadmins on all development teams from the get-go are now a must in my book.
- mgrouchy 16y ago
  Yeah, I was never a sysadmin, but for 8 months in my university days, I worked as a systems programmer for the CS Department at my university. I worked on stuff that automated system deployments, backups, imaging, etc. Its actually in the process of being open sourced now at http://www.labnet.ca/ http://www.labnet.ca/ (Its actually a pretty incredible system I recommend anyone who is interested in this type of stuff to check it out). Because of this I worked with some awesome sysadmins and unix/linux gurus so even though they were a bit rusty, I had enough core systems admin skills to have a good intuition about how to solve most of the problems I have normally. When I run into roadblocks I know some awesome sysadmins that I can hit up to get me over the hump.

sophacles 16y ago

I think it is extremely important to have at least one developer who has been a sysadmin in the past. One of my closest colleagues started his career as a sysadmin. At first I was a bit distrustful because he didn't have a lot of "real experience" or "education". But as I got to know him, I realized his sysadmin "spidey sense" was a godsend. He has a knack for knowing when things that should just work will in fact fall over. He also has a lot of deep OS and platform knowledge, so frequently when we would want to throw piles of code at something, he would suggest and OS tweak or similar to get the same end result. So yeah, sysadmins on all development teams from the get-go are now a must in my book.

mgrouchy 16y ago
Yeah, I was never a sysadmin, but for 8 months in my university days, I worked as a systems programmer for the CS Department at my university. I worked on stuff that automated system deployments, backups, imaging, etc. Its actually in the process of being open sourced now at http://www.labnet.ca/ http://www.labnet.ca/ (Its actually a pretty incredible system I recommend anyone who is interested in this type of stuff to check it out). Because of this I worked with some awesome sysadmins and unix/linux gurus so even though they were a bit rusty, I had enough core systems admin skills to have a good intuition about how to solve most of the problems I have normally. When I run into roadblocks I know some awesome sysadmins that I can hit up to get me over the hump.