Programmer Deathmatch II
Last fall, Berkeley Data Systems ran a "Programmer Deathmatch", offering a $10,000 prize to the one programmer who successfully navigated 3 timed rounds of programming competition. (You can read my write up of the event here and here.)
Of course, Berkeley Data Systems wasn't just trying to add some fun to the local landscape, they were looking for some programmers to recruit and they ended up finding two of them. It looks like they've decided that this was money well spent, because on April 14th, they'll be holding a second in what they've told me will be a recurring series of events.
This time around the stakes are even higher. They've promise $20,000 which will be distributed according to the following equation:
There are some restrictions:
- only a few languages are allowed (yes, Ruby's one of them)
- all contestants must be full-time residents of Utah
- all contestants must be eligible to work in the state of Utah
There are a few more, but you can go and read them at mozy.com/contest if you'd like.
If you're a Utahn, and up for a programming challenge, you might want to leave April 14th open on your calendar. Oh, and if you decide to compete, good luck — judging from last year's competition, you'll need it.
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
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Interview with Patrick Volkerding
- 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