DIY-IT: How Linux and Open Source Are Bringing Do-It-Yourself to Information Technology
To Craig McLane, open-source human resources are collective as well as individual. To explain, he quotes T. S. Elliot: “No poet, no artist of any art, has his complete meaning alone”. He adds:
By providing really robust tools to our people and by pulling in more people who are interested in solving problems, who can work autonomously, but who like to have the benefit of a larger community while they're working....
[People like] Stas Beckman are doing core work for us...mod_perl 2.0. [He's] doing a lot of the work that will benefit the community, which benefits us. He's also working on database connection pooling....So we get to take the lead on doing some things that have broad general benefits for everybody. Geoffrey Young is going to start working with us. He's going to be working on things that can be done autonomously, that benefit the community but also provide immediate benefit for our business when deployed in very specific ways.
Our teams have ownership over their tools. They also don't have an excuse. They can't say that a vendor doesn't have an answer or isn't getting back on the phone. Because everybody knows that there's a community out there and you have access to the source. Everything is in front of you. So there's an accountability that's reinforced when you have source code and a community that knows so much and is so willing to respond.
You're also more motivated. When people pick their tools, the work invariably makes sense to them. They're also working side by side with the people creating the tools that we're using day by day. You can't get that anywhere else.
Once again, a company gets smart and saves money by aligning itself with its own smart employees and the development communities to which they belong.
What's different between now and 10 or 20 years ago? McLane says it's “the amplifying effects of the Internet on the power of the individual”, adding, “only a fool would ignore that”.
We read about IT brass going gaga for Linux almost every day. Ken Harris, CIO of Gap Corp., recently said he's in favor of “Anything touching Linux”. Emea Harris of Lehman Brothers said, “We're very aggressive around migrating to Linux.”
When I spoke about DIY-IT at the O'Reilly Open Source Convention in July 2003, the majority of those attending the talk (about 100 in the room) was rank-and-file IT guys, mostly from large companies. Phil Moore was one of them. One audience member said some companies feel that their own open-source developments give them a competitive edge, and they don't want to talk about it for that reason. “They don't want their competitors to know how they do it faster and cheaper”, she said.
What other kinds of stories are we not hearing, then? Here are a few, in no particular order:
Debian: “I'm seeing far more Debian than any report gives it credit for”, says one technologist working for a large vendor that has partnerships with Red Hat and SuSE. “Red Hat and SuSE may sell more, so they show up on surveys that follow sales. But in terms of actual implementation, Debian is pretty big.”
Education: at different periods during the past 30 years, companies like Digital, Apple, IBM and Microsoft have had successful programs for getting students hooked on their goods. Now those students are swimming in a sea of free software and old or cheap PCs on which to run it. Web services consultant and author Doug Kaye says “High schools and colleges are now all about open source....It's LAMP everywhere.”
The power of gravy: a number of IT people have told me that vendor relationships are valued highly, period, and always will be. “You get freebies. Tickets to games. Free dinners. Trips to conferences. A lot of people love that gravy train.”
Small consultant opportunities: one IT guy at a large company told me:
The do-it-yourself movement inside IT is lowering the barriers to entry for small contractors too. Thirty years ago, big companies went to big vendors for big solutions. That's not the case anymore. You've got small vendors and consultants with 15, 20 or 40 people going in and delivering hugely successful solutions to Fortune 50 companies.
Phil Moore adds:
When you contract for an open-source solution, all the middle layers of the contracting nightmare you get when you go through big vendors are gone. If you contract for a simple change from a big vendor, you can be in for spending a lot of money. The cheapest vendor contract I've ever been involved with is a half-million dollars. At the very least you've got two gigantic legal departments involved to begin with, just to negotiate the contract. Yet I've gone and got similar order-of-magnitude technology changes on open-source products for below five figures. This is a gold mine. This frees up a huge part of my budget. And time-wise the process is highly streamlined.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide