Developers vs. System Administrators

As some of you know I’m training System Administrator, but in general these past 10 years I have devoted primarily to develop. But these past few months (mainly from earlier this year) I’m spending most of the time to manage and organize projects and, above all, to exercise Sysadmin. As I said, I had already had experience in combining both stories, but overall the system always come backed by someone and I “tried to look” instead of working.

Now that has changed and has led me to wonder these two lifestyles together and separately. And I have to say, even a little more hard work from System Administrator, there is no doubt that overall life satisfaction is much higher.

Developers System Administrators

The point is that on a day to day, the developer often found difficulty points but I think they are related. One thing is clear, I speak not of layout designer and developer, that’s another story (this really makes a couple of years and I try not to touch a single line of code). Back then, develop, today is very simple. For the record, I’m programming with Notepad + + and without frameworks and several such shit. We can discuss it, for now I’ve always won, the frameworks are supposed to have you lighten the work but when I ask something then developers make a change looms the drama because “that makes the framework well and touch is complicated. ” No, it’s not complicated, just overload the function, or create a new feature and it’s over, because if you say it must be so (for SEO, WPO, for efficiency or whatever, so). I also recognize that generally develop depends on each. When you spend years and I see a piece of code that I made ​​when I know them. I guess my code is my signature. To finish, I also believe that the development side, but someone is always pushing for “dates” is something that can become very lax, because just when you begin development, you leftovers with a few more weeks and so comfortable.

Instead systems management is quite different. There are generally two types of actions: the “has maroon all” and “needs to be updated.” In general the two situations are quite shit. When something goes wrong, you usually have to fix it “for now.” This implies stress levels quite hard because you usually have to fly co joiner as bothering and fluttering around. Unfortunately people do not seem to realize that in most cases when something fails you and you realize that you have reached 10 emails telling us nose is failing.

The other situation, the maintenance has its upside and downside. The positive is the R & D. The evolution in the programming usually occurs every few years and the jumps are not very big (I could program with the same thing I learned in 2001) but instead the infrastructure is usually different. The machines are evolving every so often (every 6 months there is usually more powerful servers) and we have to adapt the software to the hardware to take full advantage.

For instance, in the last two months that I could get a little further with Varnish I think I made ​​up five new versions of the configuration. Sometimes a simple change of a figure, sometimes it is adding a completely new feature, but in any event can become several hours (or days) devoted to trying to scratch a little here and there to make things work better. I do not know many programmers who after finishing a project to reopen the program and review the code for improvements (and stating that I am one, although it does now and then I get to review code to optimize it somehow ).

I know many Lusers # BOFH will not understand half of what I say (of me) but I guess I needed to vent a little after a few days when between them (developers) and others (administrators) are killing me…