I worked at AFTAC in the 80's, and they've been able monitor this stuff since the 70's. http://en.wikipedia.org/wiki/Air_Force_Technical_Applications_Center
Everyone says communication is key, but what I'm not hearing is communication about expectations. You really need to know what your SO's and your own expectations are and make any compromises in advance that you can. Know that your expectations & compromises WILL change.
1. Who is expected to do chores? Which chores? Cooking, cleaning, mowing, shopping, oil changes, etc. Is one of you expecting to be able to give "HoneyDo" lists to the other? Who cleans the bathroom & to whose standards?
2. Finances. Who budgets? who pays bills? What money is common and what money is not? Does one, or both of you get an allowance of personal money? Who decides how to spend discretionary money? Do you budget vacations in advance? if ONE of you controls the budget, be careful not to allow this to become a dominance thing.
3. Asthestics. Who picks cars, couches, pictures, carpet, etc? Whose decor is it and why?
4. Physical. Do you expect your partner to stay the same shape/fitness? What happens if time/work/children make this not allowable?
5. Children. Yes, No, NEVER, Maybe. When? Who decides? Oopsy, I know we decided "Yes in 2 years but..". Upbringing. Good cop/bad cop? So very unfair to the "bad cop".
6. Private time? Friend Time? Date time? Private/personal space?
Expectations and the managing thereof are some of the most crucial ingredients in making a marriage viable. And I guarantee you both have some expectations that you don't even realize you have so you to start discussing the ones you know about, especially the ones you think are a "given".
Aha, Finally! I was worried that I'd get down to the end of the comments and have to write this one myself.
RobinH is right. Communicate. Learn to let things go. BOTH of you must realize that you cannot change the other person (much) and efforts in that direction will irritate and frustrate your SO.
Yes, but back in the late 80's I dealt with some German source code. 14 syllable variable names are ridiculous;-} (OK, they're ridiculous when people write them in English too)
1. KISS - Keep It Simple Stupid, don't be unnecessarily complex.
2. DRY - Don't Repeat Yourself, if two or three places perform essentially the same actions then that should be one function/method with the differences added and commented.
3. Make it easily readable. This means simple yet meaningful variable names, comments where anything non-obvious is done and appropriate use of encapsulation/isolation (no methods/functions that are too long, and none with only one or two actual lines of logic).
Anything else can fixed with a code beautifier/pretty printer/reasonable IDE or editor.
Yeah, and who cares if we kill the 20 something guy who was on the list for "statutory" rape because when he was 17 his 16 year-old girlfriend's parents freaked when they were caught whilst engaged in a BJ.
Advice from an Ex-mil guy with 20 Years as a SW En
on
The Living Dilbert?
·
· Score: 2, Insightful
I spent 6 yrs in the AF, got out 15 years ago, and even back then in most places the tech was obsolete. I was very lucky and was stationed in two different shops that were actaully dev shops and learned a lot about software development. Pure luck, and rare at that from what I understand. I then spent 8 or 9 years doing gov contracting for agencies around D.C. Since 2000 I've been doing commercial development in Austin, TX.
This experience has taught me alot about big organizations and small companies. Some of the gov. contracting companies I worked for were 5000. I've worked in startups and largish SW deve companies. Through all of this I have noticed a couple of things.
1. Dilbert and the PHB's do indeed continue to live and prosper. 2. Bureaucracy sneaks in insidiously via "Professional HR" people and MBA's once a company grows somewhere between 200 to 500. Mostly because "thats how other companies do it, so we should to." & because they use arbitrary rules to show that they have power. 3. A publically owned company is legally mandated to be loyal to its stock holders profits and NOTHING ELSE. This means NOT TO YOU. but they do expect you to be loyal to them without understanding that loyalty is a two way street.
What does this mean? Well, I have interpreted it to mean that the very best (and very worst too *sigh*) companies to work for are privately owned companies of between 50 to 150 employees that are not actively working to be bought out / go public.
Who says they aren't marketing to the older Gamer? My 63 year old mother seems wuite content with the games on her PS2, Gamecube and Xbox and her subscription to WoW.
Most consoles have NEVER been sold at a loss, and the PS2 made OODLES of profit from day one (enough to recoup the R&D costs within a year).
The Sega Saturn was sold at a loss and failed. The Xbox was sold at a loss but M$ could afford it. We'll see if the PS3 actually gets sold at a loss or not.
But why the #3!! did we attack Iraq in the first place? There has _never_ been any meaningful intel linking Iraq to terrorist groups, esp. Al Quaeda. They have never had any weapons capable of attacking the USA. Yes, S.H was an evil nasty dictator who killed and tortured the people of Iraq... but there are at _least_ twenty other countries in similar straits and the USA could care less about them... So waste BILLIONS of dollars, and hundreds of American lives for what ? Oil? Halliburton? Bush's ego?
I spent somewhere between 6 and 9 months, 12 hours a day, 8 hours a day on weekends, writing code for a classified project as a memeber of the US Air Force. The 6-9 month thing is because time got a little fuzzy and I didn't know exactly how long we'ld ( a team of about 24) been doing it by the time we finished. I sure didn't expect those hours when I enlisted as a computer programmer. And our morale stank...
That is called subsidization. We subsidize people in careers that aren't. It is welfare for people that could actually make a living.
Public funding is used because certain literati believe that society _needs_ this art (Or at least they like it, and think everybody should). If the market forces of supply and demand were allowed to work the _popular_ art would be funded.
Slashdot Mirror
https://en.wikipedia.org/wiki/Air_Force_Technical_Applications_Center knows how to get a LOT of data out of seismometer ...
I worked at AFTAC in the 80's, and they've been able monitor this stuff since the 70's.
http://en.wikipedia.org/wiki/Air_Force_Technical_Applications_Center
*laugh* Austin is just as ageist. Couldn't get a job last go round till I dyed the gray, then I got two offers.
This! So very much this!
Everyone says communication is key, but what I'm not hearing is communication about expectations. You really need to know what your SO's and your own expectations are and make any compromises in advance that you can. Know that your expectations & compromises WILL change.
1. Who is expected to do chores? Which chores? Cooking, cleaning, mowing, shopping, oil changes, etc. Is one of you expecting to be able to give "HoneyDo" lists to the other? Who cleans the bathroom & to whose standards?
2. Finances. Who budgets? who pays bills? What money is common and what money is not? Does one, or both of you get an allowance of personal money? Who decides how to spend discretionary money? Do you budget vacations in advance? if ONE of you controls the budget, be careful not to allow this to become a dominance thing.
3. Asthestics. Who picks cars, couches, pictures, carpet, etc? Whose decor is it and why?
4. Physical. Do you expect your partner to stay the same shape/fitness? What happens if time/work/children make this not allowable?
5. Children. Yes, No, NEVER, Maybe. When? Who decides? Oopsy, I know we decided "Yes in 2 years but ..". Upbringing. Good cop/bad cop? So very unfair to the "bad cop".
6. Private time? Friend Time? Date time? Private/personal space?
Expectations and the managing thereof are some of the most crucial ingredients in making a marriage viable. And I guarantee you both have some expectations that you don't even realize you have so you to start discussing the ones you know about, especially the ones you think are a "given".
Aha, Finally! I was worried that I'd get down to the end of the comments and have to write this one myself.
RobinH is right. Communicate. Learn to let things go. BOTH of you must realize that you cannot change the other person (much) and efforts in that direction will irritate and frustrate your SO.
Yes, but back in the late 80's I dealt with some German source code. 14 syllable variable names are ridiculous ;-} (OK, they're ridiculous when people write them in English too)
1. KISS - Keep It Simple Stupid, don't be unnecessarily complex.
2. DRY - Don't Repeat Yourself, if two or three places perform essentially the same actions then that should be one function/method with the differences added and commented.
3. Make it easily readable. This means simple yet meaningful variable names, comments where anything non-obvious is done and appropriate use of encapsulation/isolation (no methods/functions that are too long, and none with only one or two actual lines of logic).
Anything else can fixed with a code beautifier/pretty printer/reasonable IDE or editor.
Yeah, and who cares if we kill the 20 something guy who was on the list for "statutory" rape because when he was 17 his 16 year-old girlfriend's parents freaked when they were caught whilst engaged in a BJ.
I spent 6 yrs in the AF, got out 15 years ago, and even back then in most places the tech was obsolete. I was very lucky and was stationed in two different shops that were actaully dev shops and learned a lot about software development. Pure luck, and rare at that from what I understand. I then spent 8 or 9 years doing gov contracting for agencies around D.C. Since 2000 I've been doing commercial development in Austin, TX.
This experience has taught me alot about big organizations and small companies. Some of the gov. contracting companies I worked for were 5000. I've worked in startups and largish SW deve companies. Through all of this I have noticed a couple of things.
1. Dilbert and the PHB's do indeed continue to live and prosper.
2. Bureaucracy sneaks in insidiously via "Professional HR" people and MBA's once a company grows somewhere between 200 to 500. Mostly because "thats how other companies do it, so we should to." & because they use arbitrary rules to show that they have power.
3. A publically owned company is legally mandated to be loyal to its stock holders profits and NOTHING ELSE. This means NOT TO YOU. but they do expect you to be loyal to them without understanding that loyalty is a two way street.
What does this mean? Well, I have interpreted it to mean that the very best (and very worst too *sigh*) companies to work for are privately owned companies of between 50 to 150 employees that are not actively working to be bought out / go public.
Just my 2 cents.
Who says they aren't marketing to the older Gamer? My 63 year old mother seems wuite content with the games on her PS2, Gamecube and Xbox and her subscription to WoW.
And if I remember correctly that was R&D costs, not losses on console sales.
Most consoles have NEVER been sold at a loss, and the PS2 made OODLES of profit from day one (enough to recoup the R&D costs within a year).
... http://www.actsofgord.com/Proclamations/chapter02. html
The Sega Saturn was sold at a loss and failed. The Xbox was sold at a loss but M$ could afford it. We'll see if the PS3 actually gets sold at a loss or not.
Don't believe me? The numbers and such are available if you search, or just read the Gord's little article
Reasonably good (98% accuracy) voice recognition exists, but the algorithms have to be trained per voice by a math PHD ...
Various reasons ...
I think the primary ones were measles
and come sort of chickenpox/smallpox
But why the #3!! did we attack Iraq in the first place? There has _never_ been any meaningful intel linking Iraq to terrorist groups, esp. Al Quaeda. They have never had any weapons capable of attacking the USA. Yes, S.H was an evil nasty dictator who killed and tortured the people of Iraq ... but there are at _least_ twenty other countries in similar straits and the USA could care less about them ...
So waste BILLIONS of dollars, and hundreds of American lives for what ? Oil? Halliburton?
Bush's ego?
I spent somewhere between 6 and 9 months, 12 hours a day, 8 hours a day on weekends, writing code for a classified project as a memeber of the US Air Force. The 6-9 month thing is because time got a little fuzzy and I didn't know exactly how long we'ld ( a team of about 24) been doing it by the time we finished. I sure didn't expect those hours when I enlisted as a computer programmer. And our morale stank ...
I'm in austin, and am interested in what you would consider a "sane salary" for a Java developer with 18 years experience, 7+ with Java.
You actually payed attention during that 15-20 minute boot sequence? I always went and brewed the coffee or something ....
Just because a pop medium uses a term, does NOT mean it created that term.
And they missed Error 15 ... (The error is 15" from the monitor)
No, no, no. There is NO shortage of incompetent management ;-}
That is called subsidization. We subsidize people in careers that aren't. It is welfare for people that could actually make a living.
Public funding is used because certain literati believe that society _needs_ this art (Or at least they like it, and think everybody should). If the market forces of supply and demand were allowed to work the _popular_ art would be funded.
I'm a "Technical Prima Donna" and quite happy about it thank you.