Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment I'm not seeing anything I recognize... (Score 2) 226

Integrator/Architect here... I travel all over the country (USA) for $CFGMGMT software company doing implementations and training in said package. Further, I do professional services engagements to implement and deploy devops workflows and integration paths for both operational and development workflows. I can say with great confidence that after reading the 150-ish comments here that I've only seen one or two commenters that come close to "getting" modern devops.
As for the RTFA implications, many people saw right through his silliness. Developer in an ivory tower thinking his world is grand and majestic and lauded above all other disciplines. I guess that explains some of the crap in Python (but I digress).
I've been in this business since before the bubble. I have done systems work dating all the way back to the 80's. At that time there were many silos with few bridges between. The first iteration of "devops" I remember seeing can be quantified as developers seeking root access. Even to this day, the answer is continually a resounding "no". Why? Are devs automatically rejected due to what specific tower they are residing in? Are they rejected because of the "separation of powers" or because of "politics"? Are ops folks just dicks with a chip on their shoulder?
I think a number of things have happened and if you'll indulge me, perhaps we can break this conversation out more to see what's going on today.
Back in the day, we had an operations team, systems team, qa team, and dev team. Loosely defined, these were the folks in the NOC monitoring everything and pushing ticket events to the right teams via triage, doing prints and getting them ready for the requestor, managing backups and access to the computer room, etc... general "operational" tasks. Day to day "operations" of the center of computing for your facility. At some point, this title got applied to anything that smacked of someone whose fingers touched anything made of metal. When this seemed to change? Late 90's-ish. I don't have specifics, but that's my recollection. Remember also that different sections of the country progress at different rates, so YMMV.
Then there was the "systems team". Different sites had different monikers for this team from "engineering" (which PEs got pissed about) to "architecture" to "Systems Admins" to... well, whatever title HR thought was appropriate and met their organizational/talent distribution goals, but the work was generally the same. Storage, systems (mid range, intel, mainframe, etc.), capacity planning, backup systems and strategies, disaster recovery, and a myriad of other specializations within systems work. This is the specific "field" of systems work that breeds organizations like SAGE/LOPSA, etc. Those in these organizations dig into the very nuts and bolts of admin as a career and a field of expertise, following current research and methodologies and bettering themselves each and every day. I would offer that while dev folks can be quite competent in various systems tasks, they're just not a sysadmin (much less an engineer or architect). They really have no place in this area REGARDLESS of their quality at it.
Many times I've heard dev get bent out of shape because "ops is being a blocker" or "we can't get anything done because ops is saying 'no'". It's unfortunate to be that myopic and that selfish. What many devs don't understand is the ops person they're dealing with is supporting sometimes as many as 10 different DEV teams operating on the exact same hosts or clusters of hosts and one or two of those environments is the pet project of VP #13 that agreed to a bunch of junk on the golf course that isn't in the statement of work, but is being offered "on the sly". They don't understand that dev #22, who has relationship with VP #11 and can essentially get what they want has forced you to introduce "whiz bang package or library" while the safe, researched, CERT recommended package is (and, incidentally is the one all the other dev teams are using) but because this high-horse, ivory-towered, "connected" dev has enforced his will, all the other devs are screwed because those two packages are incompatible and cannot coexist on the same hosts. Now, all the work that was being done on the systems has to cow-tow to other requirements. Now, ops guy is stuck between two warring factions and has to figure out who to please 1) to keep his job and 2) to make working with everyone involved pleasant (at the very least). "Only approved packages" implemented as per ops, anyone?
Development is a wonderful career. I always say "I am not a developer and I don't play one on TV"... It's a specialization, a craft. I am not a craftsman in this field. I don't even pretend to be. I count on the development teams to know how best to execute their craft. However, they need to reciprocate. I have been fortunate to be in this precise same situation and am grateful for it. They count on me to "do my thing" and I count on them to "do their thing" and we have a pleasant, amicable relationship. I think this is how it should be.
On the subject of "devops"... this depends on your environment. Some folks mean one thing and others mean something else. Point is, even the "devops software" people don't really agree 100% and it all comes down to workflow. What workflow MOST keeps security, stability, and repeatability in place for systems while providing speed, iteration, and flexibility for software development? That's it. And it's specific to you, your culture, and your environment. This simple structure to conform your particular workflow around works in each and every environment I've ever been in. Fitting a company's culture around this sort of workflow WILL make things better. Politics and religious arguments should be set aside when building this. Devs shouldn't be quick to gallop away toward 'give us full root everywhere" and systems should not be quick to impose their view of the world on development and actually *listen* to what they're trying to accomplish. Many times, a little extra work by YOU on the front end can make for happy, fulfilled devs that are excited that they can concentrate on the thing they REALLY excel at: writing great code. If you take the time to implement your infrastructure in code, you get to spend much more time on considerably more interesting things, not the least of which is concentrating on refactoring and making your own code better (whether scripts, recipes, manifests, or whatever). Everyone wins in this scenario and everyone gets better.
I'm certain I'll have a lot of disagreement here, but I've seen it work, it works well, and devs & systems folks really actually find out they like each other to some degree. (shudder!)

Comment Google, maybe? (Score 1) 768

I Googled "History of the 5th Amendment" and got a crap=ton of hits. Not the least of which is this:

"The Fifth Amendment to the U.S. Constitution provides that "no person ... shall be compelled in any criminal case to be a witness against himself." The right was created in reaction to the excesses of the Courts of Star Chamber and High Commission—British courts of equity that operated from 1487-1641. These courts utilized the inquisitorial method of truth-seeking as opposed to the prosecutorial, meaning that prosecutors did not bear the burden of proving a case, but that sufficient "proof" came from browbeating confessions out of the accused. These courts required the accused to answer any question put to him, without advance notice of his accusers, the charges against him, or the evidence amassed. With the abolition of the Courts of Star Chamber and High Commission, the common law courts of England incorporated this principle of nemo tenetur—that no man should be bound to accuse himself. By the 18th century, English law provided that neither confessions coerced during the trial nor pretrial confessions obtained through torture could be used. This was based on the belief that coerced confessions were inherently unreliable. The right to be free from self-incrimination was established in nine state constitutions and was a tenet of the common law throughout most of the colonies before it appeared in the U.S. Constitution. Since then, the U.S. Supreme Court has expanded the Fifth Amendment to apply not only to criminal proceedings and pretrial proceedings in criminal matters, including police-station interrogations, but also to "any other proceeding, civil or criminal, formal or informal, where his answers might incriminate him in future criminal proceedings." The law also prohibits prosecutors from making reference to a defendant's refusal to take the stand as probative of guilt. So long as the government is compelling potentially incriminating speech—either before a jury or a Senate Committee—the right can be invoked."

Seems plausible.

Comment Re:Great idea if you don't care about students! (Score 1) 212

>Distance/video learning can help to enlighten. It can even help to educate people who genuinely want to learn (typically, this works better with adults).
I have to agree here. I'm in a distance-learning theology coursework, and I'm doing 10X the work I ever did while I was in college, and learning and retaining more.

Comment Re:If they are correct... (Score 2) 212

The problem here is one of relegating your own hiring practices to the realm of the very employee you are trying to avoid. Let me explain... I helped a local University (the one I attended) install a pretty massive software package. I trained their entire team on how to use it, and how to bring in what they knew about UNIX scripting to make the thing even more powerful. Six months later, one of the basic admin gigs came open, and I applied for it. I was well qualified for the position, and my experience outweighed everyone else in the department. I was perfect for the job. The screener was the department head, who was a good friend of mine as well. He was painfully sorry he couldn't hire me because the University had a "college degrees only" policy for hiring, and would have no one in these positions that didn't have a degree. Best part: a girl with a degree in Kinesiology got the gig in the computing services department doing that job. I had to train her too.

Comment Re:Getting the Experience (Score 1) 112

I'm sorry you can't comprehend that this does happen out there. 15 years of Java in 2000. 10 years of Windows 2000 in 2002. I've seen both asked. In fact, MANY times this has been covered right here on Slashdot... several years ago. Long before you ever joined the site. You should really pause to consider who the readers and posters in Slashdot are. Many of them are employers, consultants, engineers... Those with PhD's and in fields of research you'll never be a part of. Many of us work for the largest companies in the world.

Comment Desktops... (Score 1) 318

I think this'll only affect the desktop market. (why I run my desktop OSes - Linux, Windows, OSX - on a Mac instead of a PC). In the server space, though, that's big freaking money, and I think the manufacturers will be extremely reluctant to cause this trouble in that space. One of two things could happen here, I think... this will be enough of a political black eye that MS will give in and suggest allowances for other OSes or there will be pressure coming back from the server side toward desktops that can effect change. In any event, this will be interesting to watch.

Comment IBM...Ugh! (Score 1) 434

Based on the dealings I have had with IBM over there years (several companies, different projects), IBM needs to spend their time figuring out how to make their own products work rather than trying to figure out user behavioral patterns. The fact that I've never seen a single IBM project completed at an employer of mine in the 20 years I've been in IT tells me that instead of searching their email, folks might actually need to use it as a "To-Do" instead. http://43folders.com/ http://inbozero.com/

Comment Re:That long ago? (Score 1) 721

Actually, since the inception of the Berne convention, Copyright was modified that copyright laws from country to country would be observed across political and national lines. Prior to Berne, there were no guidelines, and individual countries' copyright laws held, but for their own country. Most of these things are managed through the World Intellectual Property Organization and its Copyright Treaty signed by a great number of nations. So, diatribe aside, it isn't just the U.S.

Slashdot Top Deals

Live within your income, even if you have to borrow to do so. -- Josh Billings