No what I am saying is that you can list a degree or not it will make no difference in my determination. I look only at background and my perception of your raw talent.
No, sorry it is not, your raw talent and resume is your most respected qualification.
I am constantly interviewing and hiring both systems engineers and developers. If there is a degree listed on your resume I don't even bother to read it. The same goes for certifications they mean absolutely nothing. When I interview someone I am looking for natural raw talent and a proven background.
Windows easier to manage, says who? I have been in more than one shop where you have 1 admin per 1000 linux servers. Now granted the ones they have are top notch linux gods. Now if you have qualified that as easier for a beginner, then yes windows is the way to go.
I have a rather good friend that runs a ISP. He has a rather simple solution to bandwidth hogs, he disconnects them. If they paid for the month he refunds them and sends them on their way. It just is not worth it to keep those problem customers.
I am not one to condone copyright theft however if I leave my front door open it does not make me a criminal. The person that enters that door locked or not however is very much a criminal.
Running in the cloud has the same implications of running any other successful IT operation. The organizations that experienced long term outages during the amazon issue had no failover or disaster plan.
Nail hit head, you are correct the key to staying running is planning for failure. Anyone that experienced a multi hour outage obviously had not thought things through.
It worked just fine I was in the effected zone and just failed over to the west coast region. I actually could have stayed on east coast as our infrastructure does not have single points of failure.
Many.com websites were unnecessarily down for hours since nobody had thought to plan for a outage. I am sure quite a few architecture meetings where held the following day addressing disaster recovery.
The fact that reddit was down for hours is as much their fault as it was amazons. Just because you run servers in the cloud does not mean you don't have to worry about disaster recovery.
I'll bet there is quite a few architecture discussions going on today. Just because you are running servers in the cloud doesn't mean you don't need to think about disaster recovery.
I have machines in the effected zone, not a problem with them. If I had a problem it would have had no impact since I spun up a full standby deployment in the west coast data center.
I use my trusty oxy-acetylene torch, it takes but a second to pierce the top cover. Once the top cover is breached the disks are vaporized almost immediately with no possible chance of recovery.
Actually I would say at least half of the people we do hire have degrees but it is in no way a determining factor in a hiring decision.
No what I am saying is that you can list a degree or not it will make no difference in my determination. I look only at background and my perception of your raw talent.
No, sorry it is not, your raw talent and resume is your most respected qualification.
I am constantly interviewing and hiring both systems engineers and developers. If there is a degree listed on your resume I don't even bother to read it. The same goes for certifications they mean absolutely nothing. When I interview someone I am looking for natural raw talent and a proven background.
Windows easier to manage, says who? I have been in more than one shop where you have 1 admin per 1000 linux servers. Now granted the ones they have are top notch linux gods. Now if you have qualified that as easier for a beginner, then yes windows is the way to go.
It is probably the bot running on your xp box that is using all the bandwidth.
I have a rather good friend that runs a ISP. He has a rather simple solution to bandwidth hogs, he disconnects them. If they paid for the month he refunds them and sends them on their way. It just is not worth it to keep those problem customers.
I am not one to condone copyright theft however if I leave my front door open it does not make me a criminal. The person that enters that door locked or not however is very much a criminal.
I hope so because mysql runs like ass in the cloud.
LuaJIT is pretty darn quick but then again node.js running on googles V8 engine is right there with it.
Running in the cloud has the same implications of running any other successful IT operation. The organizations that experienced long term outages during the amazon issue had no failover or disaster plan.
Man powers car on ethanol, forgive me if I am less than impressed.
Nail hit head, you are correct the key to staying running is planning for failure. Anyone that experienced a multi hour outage obviously had not thought things through.
It worked just fine I was in the effected zone and just failed over to the west coast region. I actually could have stayed on east coast as our infrastructure does not have single points of failure.
Many .com websites were unnecessarily down for hours since nobody had thought to plan for a outage. I am sure quite a few architecture meetings where held the following day addressing disaster recovery.
The fact that reddit was down for hours is as much their fault as it was amazons. Just because you run servers in the cloud does not mean you don't have to worry about disaster recovery.
This does put a smile on my face, new game customers.
I'll bet there is quite a few architecture discussions going on today. Just because you are running servers in the cloud doesn't mean you don't need to think about disaster recovery.
Yes droid is just killing ios, oh wait apple is making billions per month on it.
I have machines in the effected zone, not a problem with them. If I had a problem it would have had no impact since I spun up a full standby deployment in the west coast data center.
eip's move in seconds but in my use case I do not need eip's since a front end is handing off the requests to the cloud systems.
In about the time it took you to write that message I spun up a standby deployment in another data center smart guy.
Does it talk about the twenty or so xml config files I would have to edit just to get one running?
Windows, I have heard of these self harm disorders before, I hope for your speedy recovery.
I use my trusty oxy-acetylene torch, it takes but a second to pierce the top cover. Once the top cover is breached the disks are vaporized almost immediately with no possible chance of recovery.
In my shop it is either bash or python take your pick, perl is not to be used on company systems.