Inflation isn't a problem, as the current rate is well below the Fed's target rate of 2%. Where most people get into trouble is thinking that they deserve finer things in life when they make more money. Hence, bigger houses, bigger cars and bigger TVs. It isn't long before they find themselves in the same predicament they were in before, still thinking that more money would solve all their problems.
I do I.T. support work — help desk, desktop, PC refreshes, data centers, and system admin — that typically starts at $25+ per hour. Once I complete a couple of security certifications, and get a new job in a few years, I should double my income as a computer security specialist.
I'm not pursing the American Dream of HAVING IT ALL, and I certainly don't live in San Francisco. In fact, companies are offering higher pay rates ($35+ per hour) for employees to work in the southern half of Silicon Valley (San Jose, Santa Clara and Sunnyvale), as all the young hipsters want to work and live within 30 minutes of San Francisco (i.e., Palo Alto, Mountain View and Menlo Park). Living in a studio apartment in a rent-controlled city for the last ten years also helps.
While interviewing for jobs last year, I ran into a former coworker who was still working at the same company and making slightly more money than I did when we worked together nine years ago. He stayed in the same position and accepted 2% pay raises over those nine years. I did short-term contract work — anywhere from a day to a year — for various Fortune 500 companies in Silicon Valley, making 80% more money because I have much broader range of experiences in assignment and corporate cultures. Go figure.
Last year a recruiter contacted me for a Silicon Valley job at $25 per hour. I went for an interview. The other hiring manager wasn't available, so the full interview had to be rescheduled. Oh, BTW, the job only pays $15 per hour. So I told the manager and the recruiter that I was no longer interested in the position.
A month later the recruiter accidentally sent me the salary spreadsheet via email because my name was similar to another employee's name. All the employees at that location got paid $10 per hour. If I came back for a rescheduled interview, I wouldn't be surprised if they pressured me to take the job at $10 per hour.
The contracting agency gave me a new fancy title, "Senior Systems Administrator," based on 18 years of I.T. experience, when they renewed my contract. I pointed out that a Senior Systems Admin in Silicon Valley makes $40K more per year than what I'm getting paid now. I heard their frown all the way from the East Coast on my raise request. Didn't help that the company I'm assigned to gave me server access to fix a blotched printer migration.
I don't torrent. Not then, not now. I'm just repeating what a bunch of AC's told me back then why they were upset because I revealed the series finale.
Next month Microsoft will probably introduce a.NET patch with the version number 4.6.0.1702 to fix all the bugs introduced with update version 4.6.0.0000 this month. I feel sorry that you can't tell the difference between an update (new features and previous bug fixes) and a patch (new bug fixes), or understand that a system can have multiple versions of.NET (i.e., versions 1.x, 2.x, 3.x and 4) to support legacy applications. Thanks to Microsoft (Windows/Office), Adobe (Acrobat/Flash/Reader), and Oracle (Java), I got job security because these applications all require a steady stream of updates and patches that don't always install automatically and/or correctly the first time. That's why I'm a professional, you're not.
Last episode of Battlestar Galactica was in 2009. Illegal copies over the net took a while longer to circulate back then. The AC's told me that they were waiting to watch the final episode illegally, as they couldn't afford cable TV or the $1.99 per episode fee on Amazon//iTunes.
A bunch of AC's chewed me out on/. for revealing the ending of the Battlestar Galactica TV series (remake) in a comment two weeks after the series finale. They were still waiting for an illegal copy of the final episodes to become available on the Internet. Silly pricks.
My job at my company is to look at the patch report and figure out why the patches aren't going through for 80,000+ systems. The last set of patches holding everything up is typically a set of.NET patches for the one, two, three or four versions of.NET installed on each system. That's an additional 15 minutes on my part to remote in and manually install the.NET patches on each system. Your point is not only off topic but also wrong.
His obvious mistake was going for the jackpot. If he rigged it for smaller payouts under $500 over a long period of time, he might have escaped detection. Big numbers attract attention, smaller numbers seldom do.
Try 30 years ago when all you could see from the side of the road was a sea of cattle. The smell was suffocating and the summer heat was oppressive, especially with the windows rolled up, the AC in the car not working and 55MPH was the speed limit. Today we have more techies than cattle to drop cow pies.
When I took my A+ certification ten years ago, I've got thrown off on the printer questions that described a dot-matrix printer but the answer was for a laser printer. My printer experience then was mostly dot matrix, inkjet and thermal. I didn't get a home laser printer until 2007. A $300 Brother printer that lasted seven years until the laser drum reached end of life after 30,000 pages. A $150 replacement printer was cheaper than a $200 laser drum.
I'm talking about.NET 1.x, 2.x and 3.x. Hence, multiple versions of.NET that are still receiving patches from Microsoft for legacy applications. This is almost as bad as maintaining legacy applications that are dependent on a particular version of Java 6. The.NET patches tend not to automatically install and require manual installation to get them off the monthly patch report and/or Nessus scan.
If your employer wants you to get certificates, get them (they'll probably pay for it).
I worked for many companies that proclaimed their profund devotion to becoming an ITIL certified shop, run everyone through training courses, and then refuses to pay for the entry-level certifications. Since the companies don't want to commit money to their devotion, the techs decline to pay for their own ITIL certifications and no one gets certified. So ITIL becomes a fig leaf. If you do find yourself in an ITIL certified shop, that's when you get your own ITIL certification.
Slashdot Mirror
Inflation isn't a problem, as the current rate is well below the Fed's target rate of 2%. Where most people get into trouble is thinking that they deserve finer things in life when they make more money. Hence, bigger houses, bigger cars and bigger TVs. It isn't long before they find themselves in the same predicament they were in before, still thinking that more money would solve all their problems.
I do I.T. support work — help desk, desktop, PC refreshes, data centers, and system admin — that typically starts at $25+ per hour. Once I complete a couple of security certifications, and get a new job in a few years, I should double my income as a computer security specialist.
I'm not pursing the American Dream of HAVING IT ALL, and I certainly don't live in San Francisco. In fact, companies are offering higher pay rates ($35+ per hour) for employees to work in the southern half of Silicon Valley (San Jose, Santa Clara and Sunnyvale), as all the young hipsters want to work and live within 30 minutes of San Francisco (i.e., Palo Alto, Mountain View and Menlo Park). Living in a studio apartment in a rent-controlled city for the last ten years also helps.
While interviewing for jobs last year, I ran into a former coworker who was still working at the same company and making slightly more money than I did when we worked together nine years ago. He stayed in the same position and accepted 2% pay raises over those nine years. I did short-term contract work — anywhere from a day to a year — for various Fortune 500 companies in Silicon Valley, making 80% more money because I have much broader range of experiences in assignment and corporate cultures. Go figure.
Last year a recruiter contacted me for a Silicon Valley job at $25 per hour. I went for an interview. The other hiring manager wasn't available, so the full interview had to be rescheduled. Oh, BTW, the job only pays $15 per hour. So I told the manager and the recruiter that I was no longer interested in the position.
A month later the recruiter accidentally sent me the salary spreadsheet via email because my name was similar to another employee's name. All the employees at that location got paid $10 per hour. If I came back for a rescheduled interview, I wouldn't be surprised if they pressured me to take the job at $10 per hour.
The contracting agency gave me a new fancy title, "Senior Systems Administrator," based on 18 years of I.T. experience, when they renewed my contract. I pointed out that a Senior Systems Admin in Silicon Valley makes $40K more per year than what I'm getting paid now. I heard their frown all the way from the East Coast on my raise request. Didn't help that the company I'm assigned to gave me server access to fix a blotched printer migration.
I don't torrent. Not then, not now. I'm just repeating what a bunch of AC's told me back then why they were upset because I revealed the series finale.
Next month Microsoft will probably introduce a .NET patch with the version number 4.6.0.1702 to fix all the bugs introduced with update version 4.6.0.0000 this month. I feel sorry that you can't tell the difference between an update (new features and previous bug fixes) and a patch (new bug fixes), or understand that a system can have multiple versions of .NET (i.e., versions 1.x, 2.x, 3.x and 4) to support legacy applications. Thanks to Microsoft (Windows/Office), Adobe (Acrobat/Flash/Reader), and Oracle (Java), I got job security because these applications all require a steady stream of updates and patches that don't always install automatically and/or correctly the first time. That's why I'm a professional, you're not.
Last episode of Battlestar Galactica was in 2009. Illegal copies over the net took a while longer to circulate back then. The AC's told me that they were waiting to watch the final episode illegally, as they couldn't afford cable TV or the $1.99 per episode fee on Amazon//iTunes.
From Scully's bedroom, wearing pink robes and slippers.
A bunch of AC's chewed me out on /. for revealing the ending of the Battlestar Galactica TV series (remake) in a comment two weeks after the series finale. They were still waiting for an illegal copy of the final episodes to become available on the Internet. Silly pricks.
My job at my company is to look at the patch report and figure out why the patches aren't going through for 80,000+ systems. The last set of patches holding everything up is typically a set of .NET patches for the one, two, three or four versions of .NET installed on each system. That's an additional 15 minutes on my part to remote in and manually install the .NET patches on each system. Your point is not only off topic but also wrong.
The schools have no problem building brand new football fields, which is a higher priority than class size and supplies. Your tax dollars at work.
His obvious mistake was going for the jackpot. If he rigged it for smaller payouts under $500 over a long period of time, he might have escaped detection. Big numbers attract attention, smaller numbers seldom do.
Try 30 years ago when all you could see from the side of the road was a sea of cattle. The smell was suffocating and the summer heat was oppressive, especially with the windows rolled up, the AC in the car not working and 55MPH was the speed limit. Today we have more techies than cattle to drop cow pies.
Microsoft routinely releases patches for various versions (1.x through 4.x) of .NET that are installed on your system.
Nope. You responded to my comment to an AC responding to mightMartain.troll. Hence, you hijacked my thread.
http://slashdot.org/comments.pl?sid=7713693&threshold=-1&commentsort=0&mode=thread&cid=50148259
You're the one who hijacked my thread. Pat yourself on the back.
Being California, it's apricot.
Maybe 30 years ago. I can drive to Stockton with the car windows open on I-5 without ever smelling a freshly made cow pie.
When I took my A+ certification ten years ago, I've got thrown off on the printer questions that described a dot-matrix printer but the answer was for a laser printer. My printer experience then was mostly dot matrix, inkjet and thermal. I didn't get a home laser printer until 2007. A $300 Brother printer that lasted seven years until the laser drum reached end of life after 30,000 pages. A $150 replacement printer was cheaper than a $200 laser drum.
I'm talking about .NET 1.x, 2.x and 3.x. Hence, multiple versions of .NET that are still receiving patches from Microsoft for legacy applications. This is almost as bad as maintaining legacy applications that are dependent on a particular version of Java 6. The .NET patches tend not to automatically install and require manual installation to get them off the monthly patch report and/or Nessus scan.
If your employer wants you to get certificates, get them (they'll probably pay for it).
I worked for many companies that proclaimed their profund devotion to becoming an ITIL certified shop, run everyone through training courses, and then refuses to pay for the entry-level certifications. Since the companies don't want to commit money to their devotion, the techs decline to pay for their own ITIL certifications and no one gets certified. So ITIL becomes a fig leaf. If you do find yourself in an ITIL certified shop, that's when you get your own ITIL certification.
How hard is it to understand?
Two words: legacy applications.
Older versions of .NET will still get patches.