The utilities are used to a certain amount of revenue. If we start cutting into that revenue stream, they'll up the rates to keep the revenue constant. Who's the loser?
Most of the posters either denigrated the study or made the assertion that we catch up later in life. This defensive response validates the study and shows the insecurity of the male mindset. Female minds integrate facts faster and better than the male mind and females multitask better than males. I believe that the female mind is more adapted to the psychology of game-making than the male mind. The programming technology for game development allows this difference to manifest. Programming is the means to an end. Remove the technological hurdle and the innate abilities show themselves. Males are better at learning programming; it's a cognitive task that we are good at. Females want to "get to it" without having to learn the language.
Girl-invented games would be more relational than sequential, have more intricate plots and provide more variety of response to a (perceived) threat.
At one shop we had code walk-throughs. They specifically not termed "code-walkons," Several programmers --- no managers --- would schedule a conference to review and comment on code. These walk-throughs were a good idea --- the coder wasn't attacked by one person; others were (probably) more tactful than yours truly. I learned a lot of respect for my co-workers, not to mention new ways of doing things.
I searched for PostgreSQL and didn't find it. I respectfully suggest that you replace your planned database engine with PostgreSQL. Reasons:
1. it doesn't use litigaton as part of its profit picture;
2. is is about as fast as the selected database when specified with similar options;
3. it doesn't lose data as much as the selected database by a wide margin.
4. it is tied to the academic community. Just a few thoughts.
OpenBSD is a stable system. I ran it for a few months, but went back to Linux because I wanted to get back into the bleeding edge with its crashes, hangs. OpenBSD served me well and I would not hesitate to recommend it to anyone desiring a stable, secure (except for the bug lately) system (read: business users) that doesn't crash.
We promise according to our hopes; we perform according to our fears.
Managers -- down to mid-level -- need to have dates, so the programmer gives the earliest possible date. The software goes out buggy, untested. More pressure on the programmer and management doesn't trust programmer estimates anymore.
I came in late into this discussion. It seems that there is an easy, elegant solution: wait for the female to initiate communication. Perhaps they'll lonely and 'get it'. If not, then nothing lost.
Would it be appropriate to 'escrow' changes (including original entries) to a Wikipedia submissions area and publish only after peer review?
I've found Wikipedia to be a valuable resource on the net; usually the submissions are informative. I'll keep on reading/using Wikipedia, but with a larger grain of salt.
Probable cause (PC) requires, I believe, 'fruits of crime'. Something tangible. A bashed-in skull, an expired license tag,... In other words something has to have been done. It is not a preventative measure. I'd sure like the good guys looking after some one on a lower standard of proof, such as reasonable suspicion so no one gets hurt.
It'll be good in the short run, but when the table turnaround (profit/table) drops because someone is occupying that space 'playing games' and a (new) paying customer has no place to sit, McDonald's may just decide to 're-evaluate' their position.
Slashdot Mirror
Not assembler language -- machine language .
Punched cards and numbers.
There was a calculator before that, but I don't remember its name.
The utilities are used to a certain amount of revenue. If we start cutting into that revenue stream, they'll up the rates to keep the revenue constant.
Who's the loser?
Think of the global implications to surrealism!
It's the money, stupid.
Most of the posters either denigrated the study or made the assertion that we catch up later in life.
This defensive response validates the study and shows the insecurity of the male mindset.
Female minds integrate facts faster and better than the male mind and females multitask better than males.
I believe that the female mind is more adapted to the psychology of game-making than the male mind. The programming technology for game development allows this difference to manifest.
Programming is the means to an end. Remove the technological hurdle and the innate abilities show themselves.
Males are better at learning programming; it's a cognitive task that we are good at. Females want to "get to it" without having to learn the language.
Girl-invented games would be more relational than sequential, have more intricate plots and provide more variety of response to a (perceived) threat.
So there.
My children call me (70) for tech support.
PFC at 25?
He may have had other problems with the Army. At 25, he should at least be some kind of sergeant.
Further information: the (invited, as I remember) attendees were given the code for review a few days before the walk-through.
At one shop we had code walk-throughs. They specifically not termed "code-walkons,"
Several programmers --- no managers --- would schedule a conference to review and comment on code.
These walk-throughs were a good idea --- the coder wasn't attacked by one person; others were (probably) more tactful than yours truly.
I learned a lot of respect for my co-workers, not to mention new ways of doing things.
I searched for PostgreSQL and didn't find it.
I respectfully suggest that you replace your planned database engine with PostgreSQL.
Reasons:
1. it doesn't use litigaton as part of its profit picture;
2. is is about as fast as the selected database when specified with similar options;
3. it doesn't lose data as much as the selected database by a wide margin.
4. it is tied to the academic community.
Just a few thoughts.
Yes, it is sad. But why not give Hans access to computer equipment so he can {develop|finish} his file system.
OpenBSD is a stable system. I ran it for a few months, but went back to Linux because I wanted to get back into the bleeding edge with its crashes, hangs.
OpenBSD served me well and I would not hesitate to recommend it to anyone desiring a stable, secure (except for the bug lately) system (read: business users) that doesn't crash.
Chicago...why?
This might be a significant matter when entering or leaving certain countries.
I'd love to find such a place...
...or if you're a programmer. Inside simply makes no sense.
Back in the 1960s AquaFresh put chloroform in their toothpaste. It was a blast! :-)
Oh, about 1/3 to 1/2.
Some people can, some people can't. Unfortunately they're all in the IT industry.
The automated development platforms that apparently make someone off the street into a programmer are at the base of a lot of bad code.
We promise according to our hopes; we perform according to our fears.
Managers -- down to mid-level -- need to have dates, so the programmer gives the earliest possible date. The software goes out buggy, untested. More pressure on the programmer and management doesn't trust programmer estimates anymore.
Solution? None, with the current business model.
I'm not litigious, but perhaps a few lawsuits are what the doctor ordered to topple the marketing department's insanity.
Capsaicin ointment.
I came in late into this discussion. It seems that there is an easy, elegant solution: wait for the female to initiate communication. Perhaps they'll lonely and 'get it'. If not, then nothing lost.
Would it be appropriate to 'escrow' changes (including original entries) to a Wikipedia submissions area and publish only after peer review?
I've found Wikipedia to be a valuable resource on the net; usually the submissions are informative. I'll keep on reading/using Wikipedia, but with a larger grain of salt.
Probable cause (PC) requires, I believe, 'fruits of crime'. Something tangible. A bashed-in skull, an expired license tag, ... In other words something has to have been done. It is not a preventative measure. I'd sure like the good guys looking after some one on a lower standard of proof, such as reasonable suspicion so no one gets hurt.
It'll be good in the short run, but when the table turnaround (profit/table) drops because someone is occupying that space 'playing games' and a (new) paying customer has no place to sit, McDonald's may just decide to 're-evaluate' their position.