Writers with Technical Background Needed or Not
One year ago, I stuck my resume up on Dice and Monster expecting to find a nice job as a system administrator. I wrote a decent resume, outlined my abilities and accomplishments and waited to see my cell phone light up with calls. Nothing happened. I went to both job boards and saw that I had a few hits. I seem to remember about four hits on each board for a total of eight hits. I felt a tiny sense of discouragement.
I did get one call from a recruiter looking for a help desk specialist for Raytheon. The hours were simply horrible, I didn't know the product and I could make about the same amount of money flipping hamburgers at Jakes. Fortunately the recruiter, George, and I got to chatting. He told me that he wanted to retire after 40 years in the business, but his old client Raytheon kept calling him. He also conveyed something I didn't know.
When a job order from a large company like IBM went up on their web site, the young recruiters of today simply used software that went looking for candidates on the job boards and at the same time blasted out a "Hello" e-mail. George also told me that at the bottom of each e-mail the software placed a message saying: If you know someone with these qualifications, we pay referral fees.
George didn't like the state of his profession. He said that most candidates never met their recruiter. Then he asked, "What happened to the day when a company trusted you because you were a 'partner' and brought them people you knew and trusted?"
Finally, I got some advice from the elder statesman of the recruiting world. "Put two resumes on each site. Make one of them your Linux resume and the other a technical writer. Then switch them every morning."
I followed his advice and recruiters would call me. I heard this interesting repetitious statement a number of times: "I just found your resume and it fits a position that just opened up".
Sometimes, it's amazing when an industry professional shares knowledge outsiders don't have. So, what will it be? Admin or writer? How about first come first serve?
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
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