Forgot your password?
typodupeerror
Programming Government The Almighty Buck IT Technology News

California Can't Perform Pay Cut Because of COBOL 1139

Posted by kdawson
from the handwaving-only-gets-you-so-far dept.
beezzie writes "Last week, California Governor Arnold Schwarzenegger ordered a pay cut, to minimum wage of $6.55/hr, for 200,000 state workers — because a state budget hadn't been approved yet. The state controller, who has opposed the pay cut on principle and legal grounds, now says the pay cut isn't even feasible because the state's payroll systems are so antiquated. He says it would take six months to go to minimum wage, and nine months more to restore salaries once a budget is passed. The system is based on COBOL, according to the Sacramento Bee, and the state hasn't yet found the funds or resources, in ten years of trying, to upgrade it." The article quotes a consultant on how hard it is to find COBOL programmers; he says you usually have to draw them out of retirement. Problem is, if there were any such folks on the employment rolls in California, Gov. Schwarzenegger fired them all last week, too.
This discussion has been archived. No new comments can be posted.

California Can't Perform Pay Cut Because of COBOL

Comments Filter:
  • Uhh... (Score:5, Interesting)

    by jhfry (829244) on Tuesday August 05, 2008 @02:46PM (#24484009)

    I have never seen a payroll program that has the wages hardcoded in it... there is no reason that this can't be done... she simply doesn't want to.

  • Re:Uhh... (Score:3, Interesting)

    by SQLGuru (980662) on Tuesday August 05, 2008 @02:49PM (#24484095) Journal

    It's pretty obvious that the data is not stored in a relational table and they need someone to interpret the datafile format in order to write an "update" statement that saves off a copy of the current pay and then restores it later. I'm not sure why it would take 9 months to then undo that work......if they don't have a COBOL programmer, how can they get valid estimates? I know that anyone who tries to estimate my database work screws it up.

    Layne

  • by OrangeTide (124937) on Tuesday August 05, 2008 @02:50PM (#24484103) Homepage Journal

    It's a lot easier to just fire them with the software is what they are telling us.

    Seriously if California is in a budget crisis how will they pay firefighters and hospital staff? You can pay everyone full wage now and in 10 months stop paying EVERYONE entirely.

    In a business with this kind of budget problem you simply lay people off. People who work for the state are up in arms over this, but I've been laid off a number of times. You just fill out your unemployment insurance paperwork and get like 1/4 to 1/2 your salary after a few weeks, and look for a new job in the meantime.

    I'm not sure why unions act like every person should be guaranteed a job. What universe you have to live in for things to be so certain?

  • Re:Programmers? (Score:5, Interesting)

    by bestinshow (985111) on Tuesday August 05, 2008 @02:55PM (#24484203)

    It's clearly 1960s and 1970s code. It probably has the pay rates hard-coded in, rather than using a database, because back then memory was expensive and logic had to be compact.

  • Re:COBOL. (Score:5, Interesting)

    by Bill, Shooter of Bul (629286) on Tuesday August 05, 2008 @02:58PM (#24484261) Journal
    Define old. My Step Grandfather was a COBOL programmer. He's 86 now. You really shouldn't let him near anything electronic. He retired in the early eighties and hasn't kept up with any developments in the field. He doesn't know what a database is. Or Unix. He knows the IBM 360 pretty well though. So if they develop on it using IBM cards, he might be able to help.

    If you ask me, this is all payback for the original design of COBOL. If they had just extended FORTRAN and required any one interested in looking at code to have a 3rd graders grasp of math, California wouldn't be in this position and existing COBOL programmers wouldn't have to lie about their development language when talking to other developers.

    Actually, this story is about how California can't screw their state workers to make a political point, right? I guess COBOL wins after all, but they really should have made the syntax a little more like befudge.
  • Re:COBOL. (Score:5, Interesting)

    by Anonymous Coward on Tuesday August 05, 2008 @03:02PM (#24484329)

    the problem is nobody in IT wants to hire old people.

    You are right and the situation is even worse with more engineering oriented firms. Age discrimination in software/hardware is rampant and out of control. Partly it is institutional but often it is that the average 35 year old manager isn't even aware of his prejudices.

  • The problem is.. (Score:5, Interesting)

    by faedle (114018) on Tuesday August 05, 2008 @03:05PM (#24484377) Homepage Journal

    Those of you saying "how hard can it be to write a couple of lines of COBOL" are probably underestimating the problem.

    If all they had to do was just lower people's salary to $6.whatever per hour, that wouldn't be the issue. The problem is they have to account for the ACTUAL salary the person should be making, because once the budget is passed they will have to pay all those people back for the salary that's owed.

    So, there's a big issue here. They have to calculate their salary like they would anyway, and then pay them minimum wage for the number of hours actually worked (because I'd guess a number of State employees are "exempt"), remember how much they SHOULD have been paid and how much taxes SHOULD have been taken out, record that information, and then print out a check.

    In a modern programming language with a modern relational database, no problem. In COBOL with an obsolete non-relational DB, perhaps even one with 80-column mindset? Yeah, right. Good luck with that.

  • Re:Programmers? (Score:3, Interesting)

    by Drathos (1092) on Tuesday August 05, 2008 @03:09PM (#24484471)

    Depends on the way the system was written, I suppose.

    I know a former COBOL programmer who worked for a telco in the early 90s who dealt with their billing program. Every month, he had to make program changes as part of their invoicing process for customers like Coca-Cola and the Mormon Church.

  • by PolygamousRanchKid (1290638) on Tuesday August 05, 2008 @03:11PM (#24484507)

    I know that sounds absolutely idiotic, but an employee of a major European insurance company explained that exactly that happened to them with a COBOL application.

    Hell, with people losing laptops with critical data in the San Francisco Airport, why not?

    I just jested with him, and suggested that the programmers probably deleted it on purpose, because they were sick of maintaining the COBOL code.

  • Re:Programmers? (Score:5, Interesting)

    by LWATCDR (28044) on Tuesday August 05, 2008 @03:12PM (#24484541) Homepage Journal

    Yep I remember my first programing instructor explaining the idea of sentinel. You pick a number that would never come up to mark the end of data input. like 99 for a year. This was only 83 so 99 didn't seem that far away.
    When I asked him about that his answer was.
    Nobody uses software for that long.
    You know I never used sentinels like that in any of my programs after I finished that class. I have to assume that it was a standard method back in the day like using i,j,k for integers in loops. "Fortran defined those as integers be default"

  • by kris_lang (466170) on Tuesday August 05, 2008 @03:20PM (#24484697)

    I kid you not about this: when I worked in the Los Angeles County Health System, I was paid by both the county and the state bursars. The paperwork for my job stated specifically that I was required to carry out my job EVEN IF THERE WERE NO FUNDS AVAILABLE TO BE DISBURSED TO ME FOR MY PAYCHECK. I have that document somewhere in my vertical archaeological dig of paperwork from the prior century.

    I pointed this out to the H.R. person after my employment physical, and she told me "Honey, don't worry about it, the state don't run out of money." I respectfully disagreed, crossed out the line, initialed it, and signed the paperwork. Nobody gave me any trouble, but if this happened nowadays, I bet they wouldn't let me in with that line crossed out.

    Don't even get me started about the payroll records and timecard abuse: the department secretary always told me to sign the blank timecard and she would fill it out: I refused to sign it unless I also filled out my hours. When I put in more than forty, she said, "Oh no, don't worry about it, we'll take care of it," or something equivalent to that.

      I never saw timecards again from the department.

  • by tjstork (137384) <todd.bandrowskyNO@SPAMgmail.com> on Tuesday August 05, 2008 @03:32PM (#24484975) Homepage Journal

    Here's the deal. If you can go get 40% more money working for someone else, if you are that underpaid, why not go work for them? I think that we know that the answer is that 40% less than what "industry would pay" is really a mythical figure, and your day is not so bad after all. After all, if you have to have a union to get higher wages, it means that by definition you -can't- get them from somewhere else.

  • by Naum (166466) on Tuesday August 05, 2008 @03:33PM (#24484989) Homepage Journal

    While it's been nearly 5 years since I toiled in COBOL, I can assure you that much of the information infastructure you deal with on a daily basis still runs on legacy mainframe hardware with COBOL programs being fed your charge card data, airline reservations, utility usage, pharmaceutical claim adjudications, etc....

    There are plenty of COBOL Programmers out there, the problem is nobody in IT wants to hire old people.

    True. Or the "hire" would be at a rate of 50-60% of what that same programmer made previously. I still get soliciations for mainframe COBOL work and the rates and salaries advertised to me are an absolute joke.

    The problem is not lack of Programmers. The problem is managers who think a developer needs many years of experience with a specific language or technology to be able to work with it. I am sure many programmers would be willing to work on their COBOL systems, but without the required "10 years of experience with COBOL" on their resume, they would never be hired.

    Well, code is code, but I would caution that:

    • More essential is experience with the legacy platform that those COBOL programs are running on. Are you familiar with the vagaries of S0C4 or S0C7 ABENDs? Do you JCL? Can you read an MVS dump? Do you know how to allocate a file?
    • Grizzled veterans can pinpoint root cause in short order while it may take an inexperienced crew days, if not weeks, to troubleshoot a problem. It's not about being smarter, it's knowing where to look, with the cruder, less evolved diagnostic tools.

    Wow, if this is a COBOL system, you mean no one took the time and energy to document the system and all of its glorious parameters during the ramp-up to Y2K? I'm shocked...SHOCKED to hear that a bureaucracy would waste such a golden opportunity as the Y2K scare to look long-term and decide that hey, as long as we're in the process of vetting code, why don't we document it as well?

    And yes, there are already those out there jumping up and down pointing out that fixing a year from a two digit to a four digit format is way different than figuring out how to reprogram an ancient computer language. Gotta love the State Government, home to Silicon Valley, too myopic to even consider upgrading something as non-essential as a payroll system.

    Most of the Y2K effort focused simply on alleviating eventual issues with two digit dates by "windowing". No expansion of existing database fields -- as much of the processing in legacy world on a fixed column basis, and lengthening the field was considered "out of scope" -- just a simple if statement to test if it was the 20th or 21st century. And regarding documentation, you're being glib, right? As staffs are downsized, support and application teams siphoned off to India or replaced by imported non-immigrant visa holders, documentation, which never was a top priority, has been given even shorter shrift.

    This sounds like a typical "we have to re-write everything" attitude I hear from a lot of programmers who have to work with legacy code.

    They have an application that calculates the salary. They don't need to change anything in the existing application, all they need is to "decorate" the app with an additional wrapper that rolls back the salary the appropriate amount.

    A rather naive assertion. In legacy systems much of the business logic is embedded deep within the bowels of the code. There may be a "business analyst" who is the overseer, but they are totally reliant on somebody else who can actually read code. And it will be far from straightforward, even for a gifted wizard, as the code in question may be decades old, and littered with patches and interfaces placed on top of all the cruft.

    I'll give $3 to the first person who can explain to me why on Earth you need to edit the software to change p

  • Re:Programmers? (Score:2, Interesting)

    by jgtg32a (1173373) on Tuesday August 05, 2008 @03:34PM (#24485017)
    I have to agree with SgtPepperKSU, because it seems like this wasn't a problem when they needed to raise minimum wage.
  • Re:COBOL. (Score:5, Interesting)

    by Bill, Shooter of Bul (629286) on Tuesday August 05, 2008 @03:39PM (#24485093) Journal
    1)I asked how old were the guys were he thought weren't being given a fair shot. My grandfather wrote Payroll systems for large firms like Ben Franklin, and Montgommary(sp?) Ward. He wasn't stupid, he was a pioneer in the very field we are talking about: COBOL based payroll systems for large organizations.

    2)I did not mean to imply that smart people didn't work on COBOL, or that all of them ended up like my grandfather. I just wanted a further explanation of who he thought were being discriminated against. If you asked my grandfather, he would say its because of his age, rather than the lack of his qualifications. There are a fair number of COBOL programmers of his era that are his age. I'm not sure there is a very large population of COBOL programmers that are not able to find work, solely because of their age.

    3)Are you implying that I read the dummies books for Java and Databases? Ouch. that wasn't nice. Not sure what that has to do with the price of wheat in Thailand, but thanks for sharing your thoughts. Ironically, you remind me a lot of my Grandfather. When he starts losing an argument he switches to personal attacks on his opponents education and qualifications. Learn form his mistakes: don't become a bitter old man who hurts those who love him the most.
  • Re:Uhh... (Score:3, Interesting)

    by DragonWriter (970822) on Tuesday August 05, 2008 @03:42PM (#24485169)

    I have never seen a payroll program that has the wages hardcoded in it... there is no reason that this can't be done... she simply doesn't want to.

    First off, John Chiang is not a "she". Second of all, some of the problems involved include:
    1) Many (as in several tens of thousands) of the affected workers are in positions which are salaried (even though many do get overtime and dock for short hours, they get consistent pay each "monthly" pay period [which isn't always exactly a month] even though different pay periods have either 176 or 168 hours [and may vary even more for workers on 9-8-80 schedules].) Changing them to federal minimum wage means manually changing each of those positions to be treated as an $6.55/hr hourly position instead of a salaried position for purpose of pay calculation. It may also require changing the methods used by the state departments to report hours for those workers to include all the information that would be transmitted for hourly workers plus all that that normally would be trasmitted for salaried workers.

    2) It takes longer to switch back because you then have to recalculate what should have been paid all workers (salaried and hourly) based on their normal pay method, and determine from that and what they were actually paid what they should have been paid. Since the system is not designed to do this at all, this is more complicated than simply changing how you pay people.

  • by Trepidity (597) <delirium-slashdot@@@hackish...org> on Tuesday August 05, 2008 @03:45PM (#24485229)

    I know plenty of people with damn near zero experience in anything who have jobs with web 2.0 type companies. In certain market segments, especially web 2.0 and even more especially social networking, having anything at all that you can sell yourself as is enough to get in the door, because they're so desperate to hire people. Know a little CSS design, maybe can sell yourself as having done some amateur social-network analysis, and can write a PHP script? Sold!

    I exaggerate only slightly. Especially in the SF Bay Area, the fact that Google has hired ten thousand people in the past year alone has really put a drain on the availability, to the extent that most other companies will hire anyone they can in good conscience justify as "probably not terrible".

  • by krlynch (158571) on Tuesday August 05, 2008 @03:48PM (#24485291) Homepage

    I think what Arnold wants to do is a crock

    It's a question of whether the government of California even has the authority to pay people. The law in California, as ruled by the Supreme Court of California, seems to require what the Governor has ordered, and what the Controller is refusing to do:

    Though the 69-page Supreme Court decision [in White v. Davis] addressed many legal arguments, its conclusion was unequivocal. "State law does not authorize the controller to disburse state funds to employees until an applicable appropriation" - a state budget - "has been enacted," the court stated. Once a budget is in place, the employees must receive back pay. And to comply with federal law, the court added, during a budget impasse the state must pay hourly workers the federal minimum wage and those who work overtime time-and-a-half pay.

    http://www.mercurynews.com/ci_10005275?nclick_check=1 [mercurynews.com]

  • Re:Old People? (Score:5, Interesting)

    by popeye44 (929152) on Tuesday August 05, 2008 @04:02PM (#24485643)

    Well, I work here I am affected by this threat of minimum wage. Bleh.

    I can tell you the problem is this. They don't want to preserve or change the current system. "sure continued changes COULD be done to the old one.. but why?"
      They NEED a new one. The old one has served its purpose. Now take the payroll program and multiply by 100.
    That is how many of these programs and problems we have out there. I have a 15 year old sign program. It's sole purpose is to manipulate those fancy signs you see on the freeway. "slow down.. amber alert etc" This program was created by a student who left a few years later. Of course said student took the source with him and we've been stuck for 13 years making this dos program work on the varying versions of windows.

    Now a program can be purchased for 30K "per district x12" that would let us control these older sign controllers as well as the new signs.
      We can't buy it. It is never a priority to replace an OLD program that still sort of functions. In fact it's usually at the bottom of the needs/wants list. yet the state spends 2million to put CMS's "changeable message signs" every half mile in a fog area.

    This is roughly the same problem the controller runs into. He can use the old system. It doesn't matter who the controller is, When Davis tried to do the same thing the problem existed then. The system was not created for making these type of payroll changes. We don't hire cobol programmers. Heck we really don't have anyone coding programs any more. It's all web-dev and off the shelf applications. Guess what? We're in a hiring freeze as well. So it's not like we could hire anyone to do it anyways!

    So if you want to work for free and offer your expertise we do allow that. But if you want to keep all the source then no-thanks!

  • Re:COBOL. (Score:3, Interesting)

    by jmorris42 (1458) * <`jmorris' `at' `beau.org'> on Tuesday August 05, 2008 @04:24PM (#24486127)

    > All this hysteria is just being generated by the democrats..

    As is this BS about it taking six months to change people's pay rate. Here in Biizzaro World something that silly doesn't even get laughed at. In a sane world you would just issue an edict that said, "Shut up and get to work. It's simple, $6.55 * 40.0 = $262. I just ordered the banks to bounce any payroll check greater than that amount drawn on the State's payroll account. I'm betting THEIR Information Tech Dept can manage to carry out that order so you idiots had better make sure you don't cut one for more or somebody is going to get a worthless check instead of a small one."

  • Re:COBOL. (Score:5, Interesting)

    by demachina (71715) on Tuesday August 05, 2008 @04:26PM (#24486159)

    I think it would interesting to see what the world would be like if all the state and federal workers were fired. Would things be better or worse? Would the economy collapse or enter a boom when the tax burden disappeared and we got the free markets the conservatives keep saying will solve all problems.

    People relying on government to support them would certainly suffer, social security and Medicare...gone.

    What would happen to all the weapons the military has laying around, would someone invade us or would peace break out all over when the worlds biggest and most aggressive country stopped being big and aggressive?

    If you still had local police would crime remain in check, though all the state and Federal prisons would be closed down?

    The interstates would crater but maybe that would be a good thing especially if the railroads picked up the slack.

  • I'm here (Score:5, Interesting)

    by Mycroft_514 (701676) on Tuesday August 05, 2008 @04:26PM (#24486179) Journal

    25+ years of COBOL, multiple dialects. Pay me what I'm worth, I'll take a vacation from here to do the job. What's the database, if their is one? IDMS, IDS-II? VSAM files? ISAM files? I've done them all, no problem.

  • by jscotta44 (881299) on Tuesday August 05, 2008 @04:31PM (#24486287)

    Maybe one of you bright guys can tell me why a COBOL programmer is required to change the pay rate for anyone. Are they saying that the pay rates were hard coded into the system? That just doesn't make any sense. Why would any programmer do thatâ"any?

    Someone is not telling the truth or California is hiring very, very poor programmers. Sounds like now is the time to bring in an off the shelf solution. It can probably be payed for with firing the rest of the programmers employed by the state. If this is an example of California hiring for coders, then they (and their HR department as well as the management) should be fired anyway.

  • by Anonymous Coward on Tuesday August 05, 2008 @04:44PM (#24486571)
    I am actually a COBOL programmer (fresh out of college - 2 years ago) and I know quite a few others (1 who just graduated a few months ago who is now a COBOL programmer with us).

    My previous job last year was also COBOL. It's more common than you think, although I admit half of the people you find out there are definitely NOT technical, but a few are still up to date (me and a few others do program in C++ .Net/Perl/VB6/Python just off the top of my head, a few of those few, can manage to write somewhat decent 3d visual programs).

    Sure, I hate the language for its lack of object orientation, but despite the Slashdot following: it isn't bad pay, and they can be found. I'm sure the rumors about COBOL programmers is more about job security, and that's a positive thing I can see about it.

    -AC for obvious anti-pitchfork wielding reasons.
  • Re:COBOL. (Score:4, Interesting)

    by demachina (71715) on Tuesday August 05, 2008 @05:34PM (#24487445)

    "Meanwhile, crime would run rampant on the streets"

    I didn't say anything about disbanding local government and local police. They are the ones that stop crime. The state highway patrol would be the only thing that would be gone people see on a regular basis.

    I was just talking about getting rid of state and Federal government. The only issues I can see with crime are that A) local authorities would have to hold their own prisoners instead of sending them off to the state. Maybe communities would have second thoughts about locking people up for long periods for things like drug possession if they have to hold them at local expense for long periods. B) Criminals could probably move to new localities to avoid the law if there weren't state and federal wide crime databases and authority.

    People have existed with local government only, they could do it again. The only issue you would have is defense from other nations or other locales that can't live peacefully and coexist with their neighbors. I'm not sure it would be the anarchy you say it is unless there were things like food shortages. The conservatives assure us free markets will solve all problems so there should be no shortages, though you might have issues with currency without a Federal Reserve and Treasury.

  • Re:COBOL. (Score:5, Interesting)

    by CodeBuster (516420) on Tuesday August 05, 2008 @05:45PM (#24487609)

    The problem is that the government only sees the option to pay dozens of old programmers to manipulate the COBOL code instead of paying one hacker for a day to write a Perl script to hard wire all the salary data in the database to minimum wage.

    It's probably not that simple. In fact, it is likely that the COBOL payroll system is using flat files on the mainframe or else some old proprietary mainframe database that doesn't even support ODBC (because it predates everything in use today) and is only accessible via terminal or terminal emulation. No offense, but your glib attitude concerning Perl scripting tends to suggest that you haven't had to work with very many legacy systems or at least not mainframe legacy systems (they are finally getting rare now, but they are still concentrated in government and large insurance companies who were the among the first users of computer technologies when they became available and widespread in the decades following WWII). If this type of capability was not built into the system as an option in the first place (i.e. temporarily alter payroll) then it will probably be a royal PITA to accomplish. In fact, there is every reason to suspect that because payroll is (generally) such a well defined problem space that this system is even more rigid than most in its design assumptions. Incidentally, this is why the modern field of software engineering exists. If it were possible to develop flexible and powerful systems via hacking and ad hoc scripting then we never would have delved into databases, OO design, and functional analysis in the first place (and if people could manage themselves then we wouldn't need any managers). So it is either manage the payroll manually (which the system was built to handle because managing it by hand hasn't been feasible for decades now) or come up with some other system which doesn't involve the automatic payroll processing system (i.e. some other political alternative).

  • Re:I'm here (Score:1, Interesting)

    by Anonymous Coward on Tuesday August 05, 2008 @10:36PM (#24490921)

    It's CICS.

    The DBAs are actually competent.

    I know, I was on the Y2K team.

    The controller is a liar, the changes are trivial.

  • Re:COBOL. (Score:5, Interesting)

    by david_thornley (598059) on Tuesday August 05, 2008 @11:33PM (#24491501)

    Having used both FORTRAN 66 (it didn't get decapitalized until Fortran 77) and COBOL 77 extensively, they're very roughly equal in structure. COBOL had the PERFORM verb, in all its various forms, and the paragraph system, which introduced some structure to the language. FORTRAN had functions.

    The most frustrating thing I found about COBOL was the inability to use functions in any real sense. There were analogs to FORTRAN subroutines (ENTER "FOO" USING BAR, BAZ.", if I remember the syntax correctly), but not functions. There was absolutely no way to take some common operation and wrap it in a function.

    Nor do I understand what you mean about the textbooks. COBOL 77 can be written with very, very few GOTOs, in very specific locations. You need them, technically, when using the SORT verb and either feeding data into the sort or taking it out in the program itself (not using USING and GIVING to sort files directly). Using them only in that case was the best way to write COBOL 77. There were no contortions.

    Nor were "88" variables wonderful unless you were trying to do exactly what they were good at. They allowed you to name one conditional name to represent possible values of one variable. In any reasonable language, you'd do it with a function, but not in COBOL 77.

    I'm not familiar with COBOL 85, having managed to escape from COBOL programming without encountering it. I'm happy to say I've been COBOL free since 1997. I was having a distinct feeling that, once having used the COBOL side, forever would it dominate my destiny.

    Now, here's a question: how old are some of those programs? Do you have any reason to believe that they all were written in good COBOL 77 or later? If, as somebody claimed, some of those date back to Vietnam war days, those were in an earlier version of COBOL, one even crappier than 77.

    Now, there are reasons why I'd touch COBOL again. Duress. Kidnapping my son or wife and holding them hostage for some COBOL work. Extremely large sums of money. A drink from the Fountain of Youth. That sort of thing. I wouldn't do it for minimum wage. I'd rather flip burgers.

    For those of you youngsters who've heard of COBOL or glanced at it, and think you hate COBOL, think again. You can't possibly hate it like I do. You can't really hate something you don't know intimately.

  • Welcome to WalMart (Score:3, Interesting)

    by symbolset (646467) on Wednesday August 06, 2008 @01:45AM (#24492405) Journal

    The problem is that if they're paying minimum wage they're competing against a job where the biggest stressor is remembering to say "Welcome to WalMart" when people walk in the door. That, and WalMart has to actually pay the state minimum wage, and the job is to ensure that state employees (including the programmer) get paid the lower federal minimum wage.

    The bigger problem is that if Arnie-baby actually achieves this goal a lot of state employees are going to discover they are due their 20 year retirement and/or realize that real-estate prices in the rest of the country are so low they can trade their 1200 sq ft California "Ranch home" - even at fire sale prices - for a riverfront 2500 sq ft house on a 40 acre spread in Ephrata, WA and have enough money left over to fund their job search in a growth market for 20 years.

    850 Sq ft on 1/20th acre. 1bd, 1bath built in 1928. Near transit. $800,000.

    What, are you nucking futz? The problem with doing this to school teachers is that you also require they be good at math.

    I imagine if Arnie achieves his goal the California mortgage industry could see a spike in defaults. Just guessing here.

  • Re:Programmers? (Score:3, Interesting)

    by Goldsmith (561202) on Wednesday August 06, 2008 @02:17AM (#24492537)

    I have a family member who was in the California assembly at the beginning of term limits. He talked quite a bit about controlled growth and spending caps as a way to prepare for future economic downturns. It turns out he was right about that.

    His argument against term limits was that it took a few years just to learn how to be an effective legislator and described the situation just as you have. A few more years and he may have been able to convince enough people that controlled growth was a good thing. Legislators now don't think more than 4 years ahead. There's no reason for them to do so, they won't be in office if their projects eventually go haywire, and they need immediate results to run for the next office.

  • by ShadowSystems (527521) on Wednesday August 06, 2008 @09:27AM (#24495289) Homepage Journal

    If you cut the Employees to Federal Minimum Wage, they are now legally qualified to collect Unemployment.
    (Because a reduction of more than X hours/week or $X/hour from your normal qualifies you for limited Unemployment benefits.)

    Which means the money he "saved" from reducing their pay to FMW suddenly gets eaten by all the workers who start collecting Unemployment, Food Stamps, etc.
    Then, when the "emergency" is over, he has to pay them back the wages they are due.
    He will have, effectively, paid them *twice*.
    Good job, Arnie.
    *Dumb Ass*

    As you said, I envision a LOT of people considering this their "walking papers" (which, as far as the Law & the Unemployment Office is concerned, they have been fired), selling short, & getting the hell out of California.
    Washington, Oregon, or Nevada can expect to see an influx of previous CA residents who are sick & f'ing tired of being raped by the very people they used to work for.

    The fact that they can take what in CA is poverty-level retirement savings, move across the State line, & suddenly live closer to Royalty than Peasantry?
    Yeah, now THAT'S a great way to keep the government running, Arnie.
    =(

"Marriage is low down, but you spend the rest of your life paying for it." -- Baskins

Working...