The slides include all of the commands used in the presentation."
Link to Original Source
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
...or sometimes a Solution Architect.
Most big tech companies (think SAP, Oracle, IBM, Red Hat) have a specific role for this. It is someone who could be an engineer but is specifically assigned to the sales process. Once the sales person has found the lead, the SE works with the customer to identify their needs and how best to meet them with the company's products. The sales person writes the deal and handles all the "sales" stuff.
Oh, and the SE gets a set percentage of the commission.
it's time to send ftp to where gopher is
Only if we can bring back Archie, Veronica, and WAIS.
According to Kenney, the standard has grown from 'a simple protocol to copy files over a TCP-based network [to] a sophisticated, integrated model that provides control, visibility, compliance and security in a variety of environments, including the cloud.
Actually, FTP predates TCP by 10 years and 679 RFCs. Hint: TCP is defined in RFC 793.
"The problems resulted in soaring costs"
That's weird, I thought the census was $1.6 billion under budget.
I live in the DC area and I was offered the job of lead architect/consultant overseeing the building of the datacenter for the 2010 census. In fact, I was offered this job six times in various forms over the last 6-8 years. I turned it down because I already have a good job. Not to mention the long ass commute out to the boonies of MD everyday. From what I understand, they had a lot of trouble finding good talent for the job.
Also, the various offers told a tale:
Here's a US Army Colonel who contradicts Sagan:
The evidence he speaks of includes the hard data of sensor technology that has frequently confirmed the reality of physical craft and the high quality of extremely reliable eyewitnesses who are "neither misreporting facts nor delusional."
You're kidding right? If I claim I have evidence of a mountain of gold hidden under Yankee Stadium, including all manner of sensor data, are you going to take me at my word? People make claims like this all the time. Guess what? The evidence never turns up, or if it does, it is found to be mistaken or fake. Every time.
Personally, I doubt we are alone in the universe. However, there has never been any validated evidence of any visitation to Earth. What Sagan points out is that we have very good answers to the question "How can otherwise reasonable people be utterly convinced that they have been taken aboard an alien craft when there is a lack of any evidence to show it actually happened?"
Why can't we go back to the good old days when the marketing meant finding out what people want* and directing R&D toward that thing, instead of what we have now, where they take any old product and just tell people it's the thing they want....
Let's see, which makes more money... Convincing people to buy things they don't need or want, or the first way.
Hotmail doesn't use cloud computing though.
Is that supposed to be a joke?
Religion is no minor offense.
Fixed that for you.
So a good sysadmin that knows GUI is cheaper on the payroll than say, a sysadmin that can master a CLI. Good to know that when standing in the unemployment line. Learn your freaking GUI for a job!
Yes, you will find that vast majority of small companies looking to hire a "computer guy" to click on the GUI are not going to pay very much and they are going to get exactly what they pay for. If they do manage to hire someone with real skills, that person will be gone within a year or two because they can get a hiring paying job once they have some experience.
I find it rather disturbing the UNIX ideal that sysadmins should be programmers. The opinion seems to be that it is perfectly ok for someone to need to do a fair bit of programming work to solve a system problem.
Not only have I spent over 10 years as a professional *nix system administrator, I currently work training professional system administrators. I don't know *anyone* who thinks that a system administrator should be a programmer. That being said, shell scripting is a tool of the skilled system administrator. Writing simple scripts is nothing like programming. While shell scripts can be quite complex, most that a system administrator would write are very simple. Really just a series of commands.
I know more than a few programmers that are abysmal at system administration...
And how! The vast majority of developers I know are terrible system administrators. There is a reason we keep them as far from the production systems as possible. The problem is that they think they do know system administration, but they have a completely different mindset.
...this attitude smacks of the "People should just get down and code what they need," thing. No, not really. Not everyone should have to learn that skill, and you could well be excluding people you want by requiring it.
Again, I don't know anyone who thinks this. People should learn the tools they are being paid to work with. That includes shell scripting. Now, some shops like to write a lot of in house tools in perl or python and will look for people skilled in system administration as well as those languages. Most big shops have a small number of sys admins who can write such tools. Don't confuse the tools team with the rest of the sys admins. This is a specialized role.
Also there's the simple matter that GUIs work better for unfamiliar situations. While it might be easy to just say "Well a good admin should know about this," that is rather stupid. Nobody knows everything, you never get someone with limitless experience. Part of systems administration is being able to solve novel problems.
I could not disagree more. While a GUI might help someone plod through without really understanding what they are doing, this is not a good thing. I agree that no one knows everything. However, a skilled sys admin can research and learn new things when needed. Most GUIs just get in the way of learning and deeply understanding. Then when something doesn't work as expected, you are SOL. Or you miss a subtle issue that bites you in the ass later.
I'd like to point out that I use GUI tools all the time. However, I make a point of learning the technology I am paid to understand. When I use a GUI it is because it is the best or most convenient way to get something done. I can also tell you all the places on the system that GUI changed and what to do if something went wrong.
That can make it much faster to deal with something you are not familiar with. This is important and useful in real IT work.
I have worked in IT for long enough to know this isn't true. The simple reality is that most people working in IT suck. Seriously. I have interviewed and worked with more than enough of them. They use GUIs as crutches. They are over worked and have no time to learn anything even if they were so inclined. They have a very shallow understanding of the technology they are paid to understand. They choose "easy" tools instead of tools that require learning. It is the sad state of things that truly skilled system administrators are a rare find.
Should everything be CLI? Of course not. Should everything be GUI, of course not. However, to say that GUI tools are better because you don't have to be familiar with them is a very scary attitude if you ask me.
To downgrade the human mind is bad theology. - C. K. Chesterton