I think people really need help on this.
I often spend a few minutes perusing the job listings on CL just to see who is hiring for what.
I think it is very easy to stay away from companies that are "misguided" I guess is the way to put it.
Know what you are hiring for.
If you are looking for someone to maintain servers, do dba work, support desktops, etc. you ARE NOT looking for a Network Administrator. The main focus of a network admin is to feed are care for networks. Not your stupid M$ Winblows server. Most really good network administrators are afraid of M$ because it has a propensity to blow up when we need it most. We love *nix OSes.
We all have our strengths. When you are building a (usually want to be) enterprise network do not hire a Sysadmin to do it for you. Spend some bucks and hire a part-time network architect to do the design and build for you. It will pay off in many ways.
When I build out a network I ask all of the questions that a dedicated Sysadmin (most likely) not think about. Most people do not end up with networks and systems that can scale. They will reach a critical mass that will require replacement of equipment. I design a network to grow until a point that you are running enough traffic that spending the money to open a second data center, building a new network, etc. is the least of your worries. You will have money if you have a good business model.
The life of a really good network.
1. Design a network and systems to handle about twice the traffic you anticipate. Make sure that you can grow by adding boxes (and perhaps relatively inexpensive leaf switches.)
2. You will have to replace your load-balancers. You should be running, at minimum, TCP offload. Make sure your next pair can handle the growth of a pod at least. You can then use the pair that you are removing from the
3. Replace the Firewalls between your app servers and the DB layer. Then make sure these are in redundant pair so you can use them in the next architecture. (Remove one, flip the routes, then move number 2.)
4. Rinse and repeat. You can also at this point start to build "pods," "islands," "silos" or what ever you want to call them.
The hard part about all of this? Getting it right the first time. There are many many questions to be answered. If you dont, you will end up with gear that just does not work for you. You dont really get good money for gear on Ebay.
Thanks, at last that has
Thanks, at last that has found that wished to read here.
By the way, I have drawings on this theme. Where it is possible to throw off?
free satellite tummy tuck
Very interesting article.
Very interesting article. Thanks
Ooo, lookie.
Doug-ee can has a blog? Drupal huh? Gets the job done.
BTW
How in the hell did you find this? I have done NO publication really. Need to get some more content up before it becomes anything useful.
hehehe
Yeah...it is the re-emergance of the blog.
I am surprised you didnt have a longer comment on this one ;)
hello
very cool realy thanks....evden eve nakliyat
To answer both comments :
1. I'm *me* silly. I find stuff. It's what I do (your Linked-In page was good for that).
2. I got TONS of stuff to chime in on that topic as you may imagine. I loved the "hire the right people for the job" post too. Sadly, H.R. is not geared or qualified to hire I.T. or even write the ads ... P-e-r-i-o-d. At CAT I used to raid H.R.'s garbage can for the people they threw away and swap them for all the ones that got through to my desk. (A CompSci grad with a B.S. fresh out of school does *not* know how to set up VLans or secure Solaris)
Anyway, sleepy time.