You sure remember the Fox incarnation.
You sure remember the Fox incarnation.
There is a reason that American teenagers aren't working in orchards... if growers paid enough to get teens to take the jobs, nobody would be able to afford fruit.
No. The reason is that the laws (child labor, working conditions) make it impossible for them to use teenagers any more.
Meanwhile the illegals can't complain about working conditions - and will work for less than minimum wage in (those occupations where it applies.)
US citizens needn't apply because they can't compete. (Even if they were willing to work for sub-legal prices and/or in sub-legal conditions, the employer can't risk that they might turn around and demand the missing money or compensation for the conditions.) The illegals, meanwhile, can afford to work that cheaply because social programs can pay for much of the support of them and their families - turning programs intended to help the poor into subsidies for their employers.
Meanwhile, the government's non-enforcement of the laws against the illegals working means that, in highly competitive markets (such as construction contracting), employers are left with a Hobson's choice: Use illegal labor and be competitive, or try to use legal labor and go out of business.
Good! I feel better.
5 years experience in a technology that has only existed for 14 months and cannot be taught in a classroom outside of business anyways. The requirements are way past ridiculous and border on the insane.
There's a "shortage" of good liars. I know a guy who was a fantastic BS-er that way. He had a network of fake references, for example. "Sure, he was doing Java for us in 1989. We used the first beta out. And he used Silverlight when it was still Bronzelight."
I felt too slimy to copy his techniques, but in a competitive world where a position receives hundreds of resumes, it's "survival of the fibbist", I hate to say.
Ego comes first...The unqualified never know that they are unqualified. It's just a bunch of meanies [to them], picking on them.
Heaven forbid if we ever got a president like that.
Or, white men are conditioned to an environment of abrasive competition, and not to complain about such behavior.
In a more general sense, different cultures value different things in different proportions, and that is going create conflict. "X people don't do enough Y" and/or "X people do too much Z".
Our egos make our own culture the center of the universe, and we try to shape the universe in our image. A recipe for conflict.
Most women I've known put money far above men's looks. If I had to use a point system, I'd assign it as such:
Earning power/potential: 60 pts.
Protecting and caring: 30 pts.
Looks/muscles: 10 pts.
True, the muscle part could be seen as "protecting and caring". I'm rather large in general such that perhaps that part mostly took care of itself despite me NOT resembling a super-hero. A man small or slight in stature may need muscles or karate skills to make up that portion of the report card.
Women want to be able to walk down the street at night with their guy and feel safe. There are different ways to achieve that. Some men fake it well with pure attitude.
Grace Hopper did not invent COBOL
COBOL was ultimately designed by a committee, but Grace's early compilers had a lot of influence on the language design.
The military and other organizations found it difficult to build financial, logistics, and administrative software for multiple machines that each speak a different language, and thus formed a joint committee to create a common language. (Science and research institutions had FORTRAN for cross compatibility.)
Basically the COBOL committee grew sour with disagreement. As the deadline for the first specification approached, the committee fractured into a "git'er done" tribe, and a "do it right" tribe. The git-er-done tribe basically cloned Grace's language with some minor changes and additions because they knew they didn't have time to reinvent the wheel from scratch. Grace's language was road-tested.
As the deadline came up, the git-er-done group were the only tribe with something close to ready, and so that's the work the committee heads ultimately submitted. There were a lot of complaints about it, but the heads wanted to submit something rather than outright fail. (The story varies depending on who tells it.)
Later versions of COBOL borrowed ideas from other languages and report-writing tools, but the root still closely mirrored Grace's language. Therefore, it could be said that Grace Hopper's work had a large influence on COBOL.
(It's somewhat similar to the "worse is better" story between Unix/C and a Lisp-based OS: http://dreamsongs.com/WorseIsB... )
- - - - - - -
As far as what orgs should do about existing COBOL apps, it's not realistic to rewrite it all from scratch, at least not all at once. That would be a long and expensive endeavor. It's probably cheaper to pay the higher wages for COBOL experts, but also gradually convert sub-systems as time goes on.
However, whatever you pick as the replacement language could face the same problem. There's no guarantee that Java, C#, Python, etc. will be common in the future. Rewriting COBOL into Java could simply be trading one dead language for another.
I know shops that replaced COBOL "green screen" apps with Java Applets. Now Java Applets are "legacy" also. (And a pain to keep updating Java for.)
Predicting the future in IT is a dead-man's game. At least the COBOL zombie has shown staying power. If you pick a different zombie, you are gambling even more than staying with the COBOL zombie.
If it ain't broke, don't fix it. If it's half-broke, fix it gradually.
Most employment agreements are such that the company owns it even if it is outside of normal hours. So inventions you come up with on your own time are not yours.
And one of the key reasons Silicon Valley grew up in California is a law that, in effect, says:
- As a matter of the state's compelling interest:
- If you invent something
- on your own time and not using company resources
- and it's not in the company's current or expected immediate future business plan
- you own it
- regardless of what your employment contract says
- and employment contracts have to include a notice of this.
Result: People who invent neat stuff their current company won't be productizing can get get together with a few friends, rent a garage across the street, and build a company to develop the new stuff. So companies bud off new companies, doing somewhat different stuff, like yeast. And the opportunity to get in on the ground floor attracts many other skilled people who might not be as inventive, but still wnt to be some of those "few friends" of the inventors.
Sooner or later I will need a knee replacement. It would be nice to have a tissue one instead of metal and plastic.
I could use one now. I tore a meniscus in my knee a couple years ago, and it's healed as much as it will - which isn't enough. Surgery options only involve cutting it out (which leaves the bones rubbing each other) or replacing the whole joint (which is not only inferior but doesn't last as long a my current life expectancy).
Being able to drop in a replacement, grown from a printed scaffold of generic materials seeded with my own induced-pluripotent stem cells, would just fix it. (In fact it should fix it to be as good as it was decades ago, or maybe even better than it ever was.)
All [no standard] means is that websites will write their own version, some already have.
Also: In the race between weapons and armor, weapons always (eventually) win.
By creating a standard and getting the bulk of the "content providers" to adopt it, the WWWC creates a single big target that leads to breaking MOST of the DRM simultaneously. Meanwhile, content providers are left with the choice of getting behind the big target or being non-standard.
Which is fine: Like WEP, or a locked screen door, DRM won't protect things forever. But, like a "No Trespassing" sign, it DOES indicate INTENT forever. Intent of the content provider to limit access, and intent of the unauthorized content viewer to bypass that limit. That takes the "I didn't mean to do it." defence away, and gets any legal cases down to examining whether the poster of the No Trespassing sign had the right to limit the access and/or the crosser of the boundary had a right to obtain access.
There is indeed more social pressure on men to be the bread winners, similar to how women are pressured to look attractive. And thus we'd expect young men to work harder and longer to try to get the promotions. If you are pressured by society to do X, you are more likely to do X.
It may not be "fair", but that's society as-is. A quota system doesn't factor this in.
perhaps companies ARE mistreating women and minorities which WOULD make it the company's fault
The company can't force employees to like someone. If there are known incidents, they can perhaps do something, but most "mistreatment" is subtle and/or unrecorded. The organization cannot micromanage social encounters at that level.
In general, many people are tribal jerks. I've had white colleagues who told about mistreatment when they worked with a uniform non-white group, such as all Asian. The "minority" is often targeted. Sometimes it's driven by resentment of "white culture" discriminating against them in general. They channel that frustration into an individual who happens to be white.
I'm not sure how to fix this because it's probably fundamental to human nature. Mass nagging about "being good" only goes so far. If you over-nag, people often do the opposite as a protest to the nagging. (Is the word "nagging" sexist?)
forcing yourself into a pure functional style means that your code can run anywhere because it doesn't care about the context in which it runs.
Most planners focus on the current needs, not future needs. Whether that's rational (good business planning) is another matter. It's generally cheaper to hire and get future maintenance on procedural code. If and when machine performance issues override that, the planners may THEN care.
It depends on the project. If most of the processing for an app is happening on servers in cloud centers, then it's probably already parallelizing user sessions. Parallelizing at the app level thus won't really give you much more parallelism potential, especially if most of the data chomping is done on the database, which should already be using parallelism. Web servers and databases already take advantage of parallelism. It would thus be diminishing returns to parallelize the app level. If the code is looping on 10,000 items in app code itself, the coder is probably do something wrong.
"No matter where you go, there you are..." -- Buckaroo Banzai