RubyConf*MI, OSCON, and "Ruby for Rails"
Coming off of a big week at OSCon it's time to announce RubyConf*MI, the first regional Ruby conference. It's being held in Grand Rapids Michigan on Aug 26th. It looks like a good conference, David Black will be speaking (the word is he'll be presenting a day of training through Ruby Power and Light ahead of the conference as well). I'm going to be speaking there too, along with several local Ruby hackers. You can see the speaker list or register for the conference at their website.
If you missed OSCon, there are a lot of places that you can find good coverage. Some of my favorite talks included:
- Jim Weirich — on Test First and Design by Contract
- Avi Bryant — on Seaside and 'web heresies'
- Amy Hoy — on user interface design
- Karl Fogel — on developer community tools that we really need
- FOSCon — not really a talk, but it was awesome
Outside of conference news, I also wanted to tell you about a great Ruby book. I just picked up a printed copy of Ruby For Rails (I've been working from a PDF up to this point). I can't say enough good things about it. While it's meant mostly for Rails hackers, to help them build up their Ruby skills, it also works well for plain Ruby hackers. At this point, it's one of three books that I think belong on every Rails hacker's desk (it's also one of a different three I'd recommend to every Ruby hacker).
Ruby for Rails looks at how Ruby works, building up objects from scratch, explaining inheritence and mixins, and exploring how a thorough knowledge of Ruby will make your Rails code better (or your Ruby code for that matter). One of my favorite chapters is the last one, Techniques for Exploring the Rails Source Code, which looks at reading the Rails source code as a way to improve your knowledge of both Rails and Ruby. This is a technique that can be expanded to many other collections of Ruby source.
If you're doing Ruby or Rails Hacking (or just getting started), and you don't own this book, go buy a copy now!
-- -pate http://on-ruby.blogspot.com
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!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
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