You sure remember the Fox incarnation.
You sure remember the Fox incarnation.
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.
My recent subjects are: [...] SMB1/2/3
Windows file sharing or the Super Mario Bros. series?
Games for Wii U and Nintendo 3DS are designed to be played offline at least in part. Games for mobile phones have no such requirement for certification.
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.
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?)
ULA's track record with the Atlas V: 100%
Yes, let's take one vehicle in its fifth generation (not counting subrevisions), and ignore its track record with all of its earlier versions that led up to this point and all of their failures, and all of Lockheed and Boeings' other launch vehicles over time, with all of their failures. Lets also ignore that they're going to have to switch engines soon, to an engine with zero track record.
Payloads typically launch on schedule or within a few weeks.
.... Some payloads have been waiting literally years due to delays.
Let's totally ignore that Atlas V launches once per two months, while SpaceX launches once per month, and that almost all of the wait time was due to investigation backlog. When it comes to hitting launch windows, SpaceX has a higher average success rate than average than Atlas V
And lets entirely fail to mention the point that ULA charges nearly double what SpaceX does per kilogram. Or that SpaceX is doing everything while rapidly evolving its rocket, to the point that they've basically even switched propellants partway through (denisification radically changes their properties). And while at the same time running an aggressive recovery and refurbishment programme and developing a heavy lift vehicle, with a small fraction as much capital.
... says the guy posting on a forum during work hours.
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.
As if liquid boosters can't fail catastrophically? Check out SpaceX's last failure. Liquids are hardly immune to catastrophic failure.
And actually more to the point, you've got it backwards. The SRB failure on Challenger was slow, more like a blowtorch. The explosion was when it compromised the external tank (which, obviously, stored liquids).
Solid propellants aren't like explosives. More to the point, you have to keep them under pressure to get the sort of burn rate that is desired for a rocket.
Pound for pound, the amoeba is the most vicious animal on earth.