I'm fine with pausing to explain. Putting "hello world" on the screen isn't worth much if you don't understand the other stuff. In an intro class you could give a cursory mile-high explanation and go into more detail later on. Glossing over the OO concepts is why you get guys in industry who write java like it's C.
Every part of the method declaration you quoted is important for a student to understand. And not just the student who is learning java.
1. "public". This speaks to the difference between public, private and package visible methods. That is to say, information hiding, which is a key concept in object oriented design.
2. "static". This speaks to the difference between class and instance methods. Again, a key concept in object oriented design.
3. "void". Return types. Or, in this case, the lack of one. You'll be hard pressed to learn how to program w/o learning about functions that return a value.
4. "main". This speaks to the need for the operating system to know where to "start" your code when it's executed.
In fact, I'd even go so far as to to say that java being verbose and requiring that these modifiers be explicitly specified is a positive in the context of it being used in a teaching context.
Does DrJava really add that much over vanilla eclipse? If I were a student, I might prefer an environment that more closely mirrors what's actually used in the workplace.
If they can cut those positions without impacting productivity (which they apparently think they can do) then why do you object? Should they keep folks on the payroll who aren't adding any value to the company? One needn't be a corporate sycophant to argue that employers should be free to let employees go who are no longer needed.
The Human Development Index (HDI) is a composite statistic of life expectancy, education, and income indices used to rank countries into four tiers of human development.
The Human Development Index (HDI) measures the average achievements in a country in three basic dimensions of human development: a long and healthy life, access to knowledge and a decent standard of living.
There is no component that reflects current growth rate or expected future growth. HDI is a snapshot of a country's current situation in terms of income, health and education.
Well, for one, the U.S. has a higher HDI score than any of the countries whose cities made the Internet Top 10. Then again, I put about as much stock in the U.N. HDI data as I do the Internet Top 10.
The article original article seemed to suggest that the Dell 27" AIO system represents something "new" in terms of AIO's encroaching on desktop performance levels. That's why I pointed out the 680MX in the iMac. It's not a high-end part when compared to desktop GPUs, but it's superior to the part in the Dell system that was the subject of the article.
I've never heard of a company giving a two-week notice to an employee that's being laid off or fired...
I was laid off by IBM and worked there for a month after finding out about the layoff. Then I got something like 10 weeks severance pay on top of that. So far, I haven't worked for an employer that I've hated enough to quit without giving notice.
It's a matter of PPI and typical viewing distance. Phones are often held about a foot from your face. Computer monitors are usually two or three feet away from your face. TVs are significantly further away. Greater distance = eye is more tolerant of lower PPI. That's why the iPhone 5 is ~326 PPI, a Macbook Pro with Retina is ~220 PPI, an Apple 27" Thunderbolt Display is ~110 PPI and a 65" 1080p TV is ~35 PPI.
I wasn't saying Stars = Success. I was just pointing out that, contrary to the summary's claims, not all of those six big-budget flops featured big-name stars. Pacific Rim didn't.
#2 is the most interesting, in conjunction with #1. #2 clearly shows the decline in vaccine coverage starting in 1998, the year Wakefield's paper came out in the Lancet. Coverage dropped from 1998 to about 2002, then started climbing again before plateauing in 2004 at a level approximately equal to the coverage rate in 1990. However, #1 shows that the number of reported cases of measles from 2004-2008 was markedly less than in the 1990 time-frame. That's strange. If the coverage level is the same, why would there be 2-3x fewer cases in 2004-2008 when compared to 1990?
I consider the mental disability to be a serious health issue.
Sure. It's serious, and it's a disability, but it's not an ongoing threat to their health.
How about asking a blind or deaf person if they're not experiencing life to the fullest. Their life has additional challenges, but they can and do lead completely independent lives. The comparison really doesn't hold up.
How about ask a Down's person if they're not experiencing life to the fullest? Point being: disabilities do create limitations, but they don't prevent individuals from enjoying life and/or feeling as if they're "enjoying life to the fullest". In all honesty none of us "enjoys life to the fullest" because we're all less-abled in some ways than others. I'm fairly mathematically gifted, but I'll never fully appreciate advanced math to the same extent some folks will. I'm not tone-deaf, but I'll never experience music in the same way someone who is supremely musically gifted will. In those specific areas, compared to those extremely gifted individuals, I might as well be mentally disabled. And yet I can still lead a fulfilling life.
The assumption he's making is that the set of parents who discover their child has Down's in-utero has similar views on abortion to the general population. That is to say, 20% of that group believes abortion should be illegal in all circumstances. But if 90% of the group ends up aborting, then at least half of the 20% that believes abortion should be illegal in all circumstances ended up acting in contradiction to their stated views. The flaw is in assuming that the set of parents who discover their child has Down's in utero has similar views on abortion to the general population.
Yes and no. The effects are obviously serious, and people with Downs are more prone to heart trouble, but other than that most of them don't have any serious on-going health problems that require medical care.
A child with Down Syndrome will not only be a terrible burden on their parents...
The burden is about like having a perpetual four-year-old. My wife's brother has Down's; he lives with her parents. They certainly don't regard him as a terrible burden.
Why bring someone into the world that will never be able to experience life to the fullest?
This seems like an unreasonably high bar to set. Experiencing life as fully as possible, depending on one's limitations, is presumably preferable to not experiencing life at all. Ask a blind or deaf person.
I'm not sure I would have felt worse if he'd flipped out. I'd have felt more angry than abashed. I might have been more likely to rationalize the episode as the result of his being a hyper-aggressive dick instead of copping to my own (legitimate) failings.
The details of what I wrote aren't important; it's the town. Whatever Linus's "law" is regarding dumb-ass commits and yanking commit privileges, it can be communicated in a way that's authoritative, expresses disapproval, provides constructive criticism, and yet is not impolite. You almost never have to be rude to get your point across unless your point is to be rude.
Instead of "telling off" that person, what if he'd simply said something to the effect of, "Don't ever submit code when you're not sure it works. Moreover, don't ever submit code that you admit isn't necessary. These are pretty basic principles of kernel development, and, honestly, of software development in general. This project can't afford to have stuff like this turn into a pattern, so if it happens again I'll be forced to revoke your commit privileges. I'm dead serious about that. I'd rather it not come to that, though, so do be more careful in the future. Cheers."
This is a misconception. I've been told, politely, that I totally dropped the ball on something and that if it happened again there would be repercussions. I did not feel better about myself after having been told that. Could the person have communicated the same information while screaming and calling me names? Sure. But what's the point? If anything, that would just have been more likely to make me angry and defensive in place of introspective and motivated to improve.
I'm fine with pausing to explain. Putting "hello world" on the screen isn't worth much if you don't understand the other stuff. In an intro class you could give a cursory mile-high explanation and go into more detail later on. Glossing over the OO concepts is why you get guys in industry who write java like it's C.
Every part of the method declaration you quoted is important for a student to understand. And not just the student who is learning java.
1. "public". This speaks to the difference between public, private and package visible methods. That is to say, information hiding, which is a key concept in object oriented design.
2. "static". This speaks to the difference between class and instance methods. Again, a key concept in object oriented design.
3. "void". Return types. Or, in this case, the lack of one. You'll be hard pressed to learn how to program w/o learning about functions that return a value.
4. "main". This speaks to the need for the operating system to know where to "start" your code when it's executed.
In fact, I'd even go so far as to to say that java being verbose and requiring that these modifiers be explicitly specified is a positive in the context of it being used in a teaching context.
Does DrJava really add that much over vanilla eclipse? If I were a student, I might prefer an environment that more closely mirrors what's actually used in the workplace.
I'm tired of having to support Gingerbread.
If they can cut those positions without impacting productivity (which they apparently think they can do) then why do you object? Should they keep folks on the payroll who aren't adding any value to the company? One needn't be a corporate sycophant to argue that employers should be free to let employees go who are no longer needed.
No it's not.
From wikipedia:
From the U.N.:
There is no component that reflects current growth rate or expected future growth. HDI is a snapshot of a country's current situation in terms of income, health and education.
That's not how the HDI works. For instance, the top two are Norway and Australia. Or do maintain those two are even less highly developed than the US?
Well, for one, the U.S. has a higher HDI score than any of the countries whose cities made the Internet Top 10. Then again, I put about as much stock in the U.N. HDI data as I do the Internet Top 10.
Or borrow from your current bank but open a fake facebook account to game the system and juice your credit score.
The article original article seemed to suggest that the Dell 27" AIO system represents something "new" in terms of AIO's encroaching on desktop performance levels. That's why I pointed out the 680MX in the iMac. It's not a high-end part when compared to desktop GPUs, but it's superior to the part in the Dell system that was the subject of the article.
Case in point: It will cost you an arm and a leg, but you can spec out a 27" iMac as follows:
3.4ghz quad-core i7 w/ Turbo to 3.9ghz
32GB 1600mhz DDR3
3TB "Fusion" drive (HDD/SSD hybrid)
NVIDIA GeForce GTX 680MX 2GB GDDR5
Some cursory googling suggests the 680MX is the higher performing GPU.
I was laid off by IBM and worked there for a month after finding out about the layoff. Then I got something like 10 weeks severance pay on top of that. So far, I haven't worked for an employer that I've hated enough to quit without giving notice.
It's a matter of PPI and typical viewing distance. Phones are often held about a foot from your face. Computer monitors are usually two or three feet away from your face. TVs are significantly further away. Greater distance = eye is more tolerant of lower PPI. That's why the iPhone 5 is ~326 PPI, a Macbook Pro with Retina is ~220 PPI, an Apple 27" Thunderbolt Display is ~110 PPI and a 65" 1080p TV is ~35 PPI.
I wasn't saying Stars = Success. I was just pointing out that, contrary to the summary's claims, not all of those six big-budget flops featured big-name stars. Pacific Rim didn't.
See subject.
1. Measles notifications and deaths in England and Wales, 1940-2008
2. Annual measles notifications and vaccine coverage, England and Wales 1950-2009
3. Confirmed cases of Measles, Mumps and Rubella 1996-2012
#2 is the most interesting, in conjunction with #1. #2 clearly shows the decline in vaccine coverage starting in 1998, the year Wakefield's paper came out in the Lancet. Coverage dropped from 1998 to about 2002, then started climbing again before plateauing in 2004 at a level approximately equal to the coverage rate in 1990. However, #1 shows that the number of reported cases of measles from 2004-2008 was markedly less than in the 1990 time-frame. That's strange. If the coverage level is the same, why would there be 2-3x fewer cases in 2004-2008 when compared to 1990?
So termination is a "treatment" for a condition if it's done in utero, but not ex utero. Got it.
Sure. It's serious, and it's a disability, but it's not an ongoing threat to their health.
How about ask a Down's person if they're not experiencing life to the fullest? Point being: disabilities do create limitations, but they don't prevent individuals from enjoying life and/or feeling as if they're "enjoying life to the fullest". In all honesty none of us "enjoys life to the fullest" because we're all less-abled in some ways than others. I'm fairly mathematically gifted, but I'll never fully appreciate advanced math to the same extent some folks will. I'm not tone-deaf, but I'll never experience music in the same way someone who is supremely musically gifted will. In those specific areas, compared to those extremely gifted individuals, I might as well be mentally disabled. And yet I can still lead a fulfilling life.
By that argument there's a treatment for deafness too. My newborn's deaf? Smother him and start over. Awesome- I just cured congenital deafness!
The assumption he's making is that the set of parents who discover their child has Down's in-utero has similar views on abortion to the general population. That is to say, 20% of that group believes abortion should be illegal in all circumstances. But if 90% of the group ends up aborting, then at least half of the 20% that believes abortion should be illegal in all circumstances ended up acting in contradiction to their stated views. The flaw is in assuming that the set of parents who discover their child has Down's in utero has similar views on abortion to the general population.
Yes and no. The effects are obviously serious, and people with Downs are more prone to heart trouble, but other than that most of them don't have any serious on-going health problems that require medical care.
The burden is about like having a perpetual four-year-old. My wife's brother has Down's; he lives with her parents. They certainly don't regard him as a terrible burden.
This seems like an unreasonably high bar to set. Experiencing life as fully as possible, depending on one's limitations, is presumably preferable to not experiencing life at all. Ask a blind or deaf person.
I'm not sure I would have felt worse if he'd flipped out. I'd have felt more angry than abashed. I might have been more likely to rationalize the episode as the result of his being a hyper-aggressive dick instead of copping to my own (legitimate) failings.
The details of what I wrote aren't important; it's the town. Whatever Linus's "law" is regarding dumb-ass commits and yanking commit privileges, it can be communicated in a way that's authoritative, expresses disapproval, provides constructive criticism, and yet is not impolite. You almost never have to be rude to get your point across unless your point is to be rude.
Instead of "telling off" that person, what if he'd simply said something to the effect of, "Don't ever submit code when you're not sure it works. Moreover, don't ever submit code that you admit isn't necessary. These are pretty basic principles of kernel development, and, honestly, of software development in general. This project can't afford to have stuff like this turn into a pattern, so if it happens again I'll be forced to revoke your commit privileges. I'm dead serious about that. I'd rather it not come to that, though, so do be more careful in the future. Cheers."
This is a misconception. I've been told, politely, that I totally dropped the ball on something and that if it happened again there would be repercussions. I did not feel better about myself after having been told that. Could the person have communicated the same information while screaming and calling me names? Sure. But what's the point? If anything, that would just have been more likely to make me angry and defensive in place of introspective and motivated to improve.