How Red Hat Hires 113
New submitter markfeffer, Senior Editor at Dice, writes "Red Hat's hired about 600 people in its last three fiscal quarters, and it's going to keep hiring – about 900 to 1,000 more this year. The company's primarily looking for software and technical support engineers, along with salespeople who can help strengthen its cloud-technology capabilities. They want people with strong technical skills, of course, but the company puts a premium on those who've taken the time to research its business and send in a resume that's custom-tailored to the job opening."
Re:Nice Ad (Score:3, Informative)
And it's a fairly transparent slashvertisement.
Agreed. If they're going to do that, the, "New submitter markfeffer, Senior Editor at Dice, writes [...]" part was at least an honest way to handle it.
Maybe they should add the disclaimer at the bottom like we used to have for parent and sibling companies, too.
Re:how red hat hires (Score:5, Informative)
"Come on, who doesn't want individual audio level settings for each program?"
Me. WTF do I need that for? My system sounds just fine, always has although audio is rarely used. Mostly just in connection with multimedia apps, and the login screen.
The point is that PA allows unobtrusive audio clues, like a gentle "ding ding" 10 minutes before an appointment, even though you are listening to fairly loud music. I like the fact the sound levels in VLC and Amarok is different from the rest of the system.
Before PA there wasn't a functional sound daemon, so everybody just turned off any sound notifications and manually set the sound level to zero to avoid a sudden blast of noise when accidental starting a web commercial, or when "System Bell" gave a extremely loud warning "DING!" just because you had been listening to load music earlier that day.
Not talking about the problems with running sound i Dosbox, or using two apps with sound at the same time, bluetooth sound, etc. PA solved all those problems, it just works and makes life easier for developers, distro makers and end users, which is the reason why all major Linux distributions have converted to it.
People trash talk PA, but it just that, trash talk, without technical argumentation, without any alternative to the many features that PA gives, and without regard to the fact that PA works well in the real world.
That's it.
ALSA did everything I needed for years, and ESD/OSS before that. As a user I really don't give a rat's ass how the code looks behind it all, as long as it works, which it did.
As far as SysVinit, same idea - it worked, and worked very well for decades. I still have no use for fast booting since I rarely if ever reboot. And I fail to see what other use there is for tinkering with something that worked just fine - I liked the old scripts since they were very self-documenting and easily modifiable.
So, no. Keep it.
SystemD goes way, way beyond the wish of faster booting. It really is a Sysadmins dream come true when it comes to controlling the many services (not just daemons) that runs on modern Linux systems. "systemctl" is just a natural, UNIX like way of controlling all these services from the command line or in scripting. "init/Sys V" was perhaps a fitting system for the needs of Unix boxes in the 1980's, but modern day servers and desktop systems have other needs, and init scripts are complicated, messy and fragile to edit. SystemD is just so coherent and natural to use, and allows far superior ways of maintaining, configuring, and monitoring systems.
I think your main problem is, that make your own way of using your system, a baseline for everybody else. You may not use sound very much, but many people actually do, you probably don't use bluetooth sound on your system, but many Linux devices, like smartphones do, you may not have the need to tweak init scripts, or administrating or monitoring services on a server, but other people do.