At a couple of places I worked, we had something like a strategic development unit that would basically write a proof of concept and throw it over the wall to Development, and we were expected to turn it into something production-ready. This didn't necessarily work.
I am in my 60s, and see no reason why I can't continue to work for something under two more years until I retire, which by definition is as long as I want to.
I had a very good friend working on a system running on a baby IBM, and the new CTO decided to rewrite it in Java and run it on WIndows. I got to hear all about it.
I always figure a change will take, at a minimum, half a day, longer when it's a fix to code in production. If I can find the problem in two minutes, and come up with a good fix in another two, I then have to compile, test, and go through code review.
FWIW, I was laid off once when I was 48, and had difficulty getting offers. I solved the problem by dying my hair. I'm now happily employed doing interesting things at a company I like (and, given the likely pace of corporate culture change at this particular company, I should continue liking it until retirement age).
On the other hand, plenty of users will say what they want, and will be very unhappy with you if you implement it and claim it's the solution they wanted. Frequently you have to understand the actual problem, and that then you'll do a much better job of figuring out what they need than they will.
Your cite doesn't say that the 20% figure it mentions is a lie, but rather that the study the statement was based on had seriously flawed methodology, and that we really don't know. I find it entirely plausible that 20% of women may have been sexually assaulted, defining "sexual assault" as "an action that would be illegal according to the Minnesota Criminal Sexual Conduct statutes", but I have no real way of knowing what the correct figure is.
Comments should be high-level explanations. If any reasonable rewrite of a function would invalidate a comment, other than doxygen comments and similar, remove the comment. It won't be kept current, and will become misleading.
One example of a useful comment would be why a certain approach isn't being used, or a brief comment mentioning the user request that caused you to write or change the code.
I believe you're thinking of Intercal, whose control structures were based on COME FROM and COME FROM UNLESS, provided there were enough PLEASEs in the code.
Exception handling is for exceptional situations, and should be used only in cases where what happened is significantly more important than exactly where it happened, for example the inability to allocate memory.
I don't think anyone cares much about his personal opinions, as long as they remain opinions. They care about (IIRC) $100K contributions to keep depriving people of basic rights. The difference is between thought and serious action. Someone who is politically active needs to realize that there can be consequences, and by identifying themselves that strongly with a political cause can impair their ability to do other things.
What really puzzles me about attitudes like this is why. What is it to you if someone identifies as nonbinary? Why do you insist on knowing the genetic makeup, or at least the genitalia, of someone before talking about them? "They" has been in common use as a third person singular gender-indeterminate pronoun for centuries, and it seems convenient for those who don't identify as male or female.
English already had gender-neutral pronouns that work just fine, in the form of "he" and "his". It's rarely difficult to tell from the context when they are being used in a gender-neutral way.
In my experience, it's often confusing. It sounds weird when describing a member of a predominately female set (nurses, say). It brings up the idea of a male human rather than a gender-indeterminate human.
People who know how English evolved know that "he" is normally taken to be masculine in practice. It hasn't been unambiguously neutral in a long time, if ever.
The presumed acceptance that transgenderism is the new normal is obscene.
Huh? Most of the people I've known have been cisgender. I just don't see that anyone's gender besides my wife's and mine is really any of my business, and it seems only polite to address people by their preferred gender.
reaffirmed my perspective that being transgender is a mental disorder.
Or a physical disorder. The essential thing about gender dysphoria is that it's a mismatch between body and mind, and you could blame it on either. Right now, though, it's a lot easier to change someone's body to more closely match their gender than to change their gender. There's a lot of things about the mind that can come up that simply can't be changed by current medicine.
If the Academie keeps it up, Standard French will wind up being a dialect only used by the government and other such organizations. You can't freeze a language that's in everyday use by a large number of people.
What really annoyed me about Ian becoming Kathryn was that she started changing her initials everywhere in the code base, complicating the version control system history.
I've seen a few who identified as "nonbinary". I have no objection to anyone having the gender that's comfortable for them, but, dammit, I really do need a pronoun for them.
Being a married man over 60 who lives in the house he jointly owns, I assure you that I use my Windows computer for video games. Maybe you should get out more.
The man in question did keep his sex life to himself. Someone else joined one of his groups with no intention of participating and outed him.
You mentioned a woman with an unconventional sex life. What would you like to happen to her should pictures of one of her gangbangs be shown to her employer and colleagues?
Slashdot Mirror
Like DD/MM/YYYY is any better. The only good order is the ISO one, YYYY followed by MM followed by DD, optionally followed by the time.
At a couple of places I worked, we had something like a strategic development unit that would basically write a proof of concept and throw it over the wall to Development, and we were expected to turn it into something production-ready. This didn't necessarily work.
I am in my 60s, and see no reason why I can't continue to work for something under two more years until I retire, which by definition is as long as I want to.
I had a very good friend working on a system running on a baby IBM, and the new CTO decided to rewrite it in Java and run it on WIndows. I got to hear all about it.
I knew a guy who liked to keep a pile of his stock options for amusement value.
I always figure a change will take, at a minimum, half a day, longer when it's a fix to code in production. If I can find the problem in two minutes, and come up with a good fix in another two, I then have to compile, test, and go through code review.
FWIW, I was laid off once when I was 48, and had difficulty getting offers. I solved the problem by dying my hair. I'm now happily employed doing interesting things at a company I like (and, given the likely pace of corporate culture change at this particular company, I should continue liking it until retirement age).
I have encountered, IIRC, three legitimate cases of compiler error in my career, one of which was easily fixed. That's about one every 13 years or so.
On the other hand, plenty of users will say what they want, and will be very unhappy with you if you implement it and claim it's the solution they wanted. Frequently you have to understand the actual problem, and that then you'll do a much better job of figuring out what they need than they will.
Your cite doesn't say that the 20% figure it mentions is a lie, but rather that the study the statement was based on had seriously flawed methodology, and that we really don't know. I find it entirely plausible that 20% of women may have been sexually assaulted, defining "sexual assault" as "an action that would be illegal according to the Minnesota Criminal Sexual Conduct statutes", but I have no real way of knowing what the correct figure is.
Comments should be high-level explanations. If any reasonable rewrite of a function would invalidate a comment, other than doxygen comments and similar, remove the comment. It won't be kept current, and will become misleading.
One example of a useful comment would be why a certain approach isn't being used, or a brief comment mentioning the user request that caused you to write or change the code.
I believe you're thinking of Intercal, whose control structures were based on COME FROM and COME FROM UNLESS, provided there were enough PLEASEs in the code.
Exception handling is for exceptional situations, and should be used only in cases where what happened is significantly more important than exactly where it happened, for example the inability to allocate memory.
I don't think anyone cares much about his personal opinions, as long as they remain opinions. They care about (IIRC) $100K contributions to keep depriving people of basic rights. The difference is between thought and serious action. Someone who is politically active needs to realize that there can be consequences, and by identifying themselves that strongly with a political cause can impair their ability to do other things.
I'm not sure whether you're writing for or against the singjular "they". It's been used like that by ordinary people for centuries.
"He" and "she" are perfectly good pronouns when you're talking about someone you know to be male or female, respectively.
What really puzzles me about attitudes like this is why. What is it to you if someone identifies as nonbinary? Why do you insist on knowing the genetic makeup, or at least the genitalia, of someone before talking about them? "They" has been in common use as a third person singular gender-indeterminate pronoun for centuries, and it seems convenient for those who don't identify as male or female.
In my experience, it's often confusing. It sounds weird when describing a member of a predominately female set (nurses, say). It brings up the idea of a male human rather than a gender-indeterminate human.
People who know how English evolved know that "he" is normally taken to be masculine in practice. It hasn't been unambiguously neutral in a long time, if ever.
Huh? Most of the people I've known have been cisgender. I just don't see that anyone's gender besides my wife's and mine is really any of my business, and it seems only polite to address people by their preferred gender.
Or a physical disorder. The essential thing about gender dysphoria is that it's a mismatch between body and mind, and you could blame it on either. Right now, though, it's a lot easier to change someone's body to more closely match their gender than to change their gender. There's a lot of things about the mind that can come up that simply can't be changed by current medicine.
Also, DNA does make mistakes.
If the Academie keeps it up, Standard French will wind up being a dialect only used by the government and other such organizations. You can't freeze a language that's in everyday use by a large number of people.
According to a number of grammar texts, that's true. In normal usage, "he" is masculine wherever it appears.
What really annoyed me about Ian becoming Kathryn was that she started changing her initials everywhere in the code base, complicating the version control system history.
I've seen a few who identified as "nonbinary". I have no objection to anyone having the gender that's comfortable for them, but, dammit, I really do need a pronoun for them.
Being a married man over 60 who lives in the house he jointly owns, I assure you that I use my Windows computer for video games. Maybe you should get out more.
Unless you know of someone who actually did that, you're fantasizing. What sexual fantasies do you have about SJWx (however you define them)?
The man in question did keep his sex life to himself. Someone else joined one of his groups with no intention of participating and outed him.
You mentioned a woman with an unconventional sex life. What would you like to happen to her should pictures of one of her gangbangs be shown to her employer and colleagues?