Pros: Almost nobody adjusts their mirrors correctly, and they almost always leave big blind spots. The cameras can offer perfect placement for blindspot visibility. On motorcycles they can be next to useless (my elbows look great, thanks for asking) It will probably be coupled with a collision warning / lane departure system.
Neutrals: You know they are going to make them record video which can be recovered in the event of a crash.
Cons: It better be high def. It better offer enhanced (contrast improvement) night mode (IR capable) in a non night-vision ruining way (Red & black at night) It better offer some way to judge distance. The screens better be glare proof. The lens better keep itself clean.
Anyone who has a dog and a lawn could have explained this one.
When our dog takes a crap on the lawn, and it isn't cleaned up promptly, within a week there's a dead spot with a perfect ring of extra healthy grass around it.
Too many 'nutrients' at ground zero kills the grass, but around the edges where it gets diluted the grass grows like crazy.
I worked at a large multinational that was slated to be acquired by a larger multinational.
Then, mid-way through the process came the "Oh no! India wants billions in 'back taxes' due to the sale!"
The solution was that rather than merging the two companies (triggering the giant tax bill), the Indian Development Center was kept as the last remnant of the old multinational and was now considered a "wholly owned subsidiary" of the buying multinational. Apparently the lack of a formal merger of just the portion of the company based out of India negated the tax bill somehow.
So
a) This is nothing more than the standard shakedown the government of India does whenever there's a merger of giants like this. b) It can also be avoided by some rather facile legal trickery.
It strikes me as foolish both to make such huge claims of taxes owed when a merger like this occurs and to make those taxes so easy to avoid.
I adopted scrum in my org, but only in response to a product management org that refuse to do their job. We got features masquerading as requirements, we got endless tactical "the customer wants x" requests all while upper management basically was accusing the team of being lazy for not giving them everything they wanted (and more) right away.
So we adopted agile. This let upper mgmt see we were working as hard as we could and it forced PM to decide "what do you want next? What's the minimum viable set of features? Is this more important than that?"
Yes agile isn't a cure all, but it definitely helps dev remain productive in the face of laziness and stupidity elsewhere in the org.
I've also seen a ton of fake agile (we call it "Fragile") where people adopt the buzzwords of agile without considering that good agile takes a lot of work. Fragile is adopting all the bad parts of agile without any understanding of the discipline involved to do it right (track technical debt, and pay it off as you go. Sprints are no excuse to not do long-term planning / grooming of the backlog. Daily stand-ups, where you track impediments are crucial. etc,)
Success with agile only comes if you understand when it's useful (where there's a large amount of uncertainty/stupidity, somewhere in the org)
It helps mask underlying problems (the uncertainty) while still maintaining productivity. But I wouldn't fly in a plane that was designed with agile principles. Uncertainty in a "mission critical" engineering problem kills people.
Wither goes local government, wither goes the federal government.
Barring intervention from the supreme court.
Given the feckless state of our current federal legislature, this is why it's important to elect the right person to the presidency: They will pick the next batch to decide this sort of thing.
The concept isn't that the thorium somehow gives off extra heat, it's that thorium is especially good at storing heat energy.
The laser is used to pump heat into the thorium quickly. The hot thorium is then put into contact with water to generate steam, but in the process the thorium is gradually cooled.
The concept isn't that the thorium somehow gives off extra heat, it's that thorium is especially good at storing heat energy.
The laser is used to pump heat into the thorium quickly. The hot thorium is then put into contact with water to generate steam, but in the process the thorium is gradually cooled.
... If you have exceedingly long dress code standard (and because it is so long it allows for quite a lot of leeway in terms of what you actually can wear) then what you wear to work effectively becomes a uniform.
Don't lie about what you know. I.e. it's better to say "I don't know but I can find out." rather that pulling something out of your ass.
Don't complain about anything unless you can also offer a solution to the problem.
Do good work. Figure out what the company considers "good." I.e. some companies value speed of development, others value high-quality.
Never, ever take offense when someone points out a bug in your code. If there's a 'real' bug thank the person who found it, after all they are improving on your work. If it's a not a real bug work with them to figure out why they were mistaken (bad documentation? Not trained enough on what it's supposed to do?)
Social skills help. But don't be a phony.
Manage up. If you think you deserve something from your boss, and they won't give it to you, work out a plan to get it. (If you want a promotion, work out with your boss what he needs to see before he can promote you. Work out a plan with you boss to meet those goals.)
Hopefully you get the idea. Basically you should always try to improve the situation for everyone, not just yourself.
Until you reach middle-management. And then the knives come out and it's best to be a complete sociopath.
If he's going use the "ignorance" tactic, I highly recommend that the OP remove this post.
I moderate on a motorcycle forum, and we're constantly reminding folks that bragging in 'public' about how they plan on cheating their way out of a ticket / accident report / insurance claim isn't terribly bright.
Especially considering there are folks on the forum who frown on that sort of behavior and are more than willing to rat them out.
Myself included.
...how exactly did he know his neighbor had a wireless router running, unless he used some sort of wireless device (all of which produce their own EM emissions) to specifically detect the EM emissions coming from his neighbor?
And no, divining rods don't count, regardless of what Iraqi bomb squads are doing.
Dollars to donuts says they only thought they were mashing the brakes down.
In panic situations I've seen many people "lock up" or target fixate and continue to do exactly what they were doing that got them into the bad situation they were in.
So small throttle sticking leads to mild panic which leads to more throttle and more panic and...
Lather, rinse, repeat until accident and/or lawsuit.
(my ex was in HR, and basically, US law forbids your old job from saying anything negative to your new employer)
Nonsense. There's nothing to worry about in US law about honestly giving a bad assessment. Now, the person being slagged lawyers' on the other hand...
Mind you, overly litigious ex-employees aside, there are plenty of ways around this.
The phrases "I consider him to be someone I have worked with." , "I found he occasionally did his job." or "I found he could be counted on for a truthful answer sometimes." can work magic.
Collecting a paycheck to support a losing project is sign you have a wife and two kids to support
There, I fixed it for you.
Working on a doomed project while speaking out and trying to fix it is a sign of an engineer who is a good candidate for promotion. They aren't just focused on their narrow portion and care about the project as a whole.
Generally, seeing engineers quit in the middle of a cluster-fuck project is a ding against their manager. It's up to their manager to make sure the engineers have input into the project, and can actual have their voices heard. Even if the project is a minor failure, people don't mind as much if they feel they have some stake in it. It's also a sign the project can be turned around in a later release if people at least have a voice in how to fix the processes that led to failure in the first place.
Sure some engineers are malcontents who can never be made happy, but these are pretty easy to spot in an interview. They'll talk about how the project sucked, but won't have much to say about how they'd make it better.
And even within clusterfuck projects, there can be small successes. I'm sure there are some lovely components buried deep inside Vista
So a smart interviewer is going to ask questions about your involvement in the clusterfuck.
And if the interviewer doesn't. Try answering the question without being asked. Or talk about how great your subcomponent was. And if the interviewer doesn't like that. Well, do you really want to work for/with a dumb-ass?
It also depends on experience. A smart, junior engineer shouldn't be blamed at all of a project failure. A senior engineer / manager should be asked some tough questions about their involvement.
Then there's the whole "companies with a stench of failure all over everything." Basically, I look for people with short tenures at these sorts of places. I don't want to see a 10 year veteran VP candidate from any company with reputations for "climb to the top of the meatpile" back-stabbers. Or an engineer from a place with a reputation for being insular and producing sub-par code.
Finally, the question you have to ask yourself is "Is this project really a failure?"
15 years ago I left a software company after a 3 year 'Bataan Death March'-style release of what I thought was a very disappointing, bloated, and technologically lagging project.
This product enjoys around a 65% Market share and probably a billion in sales annually.
I'm honestly surprised corporations aren't simply going into countries with cheap labor and building their own "company towns" where they can bring workers for all over the world.
Back in the day plenty of companies would just build towns out of nothing, in the middle of nowhere, and move people in to work at their factory / mine / chip fab plant.
So in this day of cheap airfare and 'free' telecommunications, why haven't we seen the same idea Globalized?
Slashdot Mirror
Pros:
Almost nobody adjusts their mirrors correctly, and they almost always leave big blind spots.
The cameras can offer perfect placement for blindspot visibility.
On motorcycles they can be next to useless (my elbows look great, thanks for asking)
It will probably be coupled with a collision warning / lane departure system.
Neutrals:
You know they are going to make them record video which can be recovered in the event of a crash.
Cons:
It better be high def.
It better offer enhanced (contrast improvement) night mode (IR capable) in a non night-vision ruining way (Red & black at night)
It better offer some way to judge distance.
The screens better be glare proof.
The lens better keep itself clean.
I did the same.
Then switched to high mount bar-ends because I hated having to look down to see behind me.
Anyone who has a dog and a lawn could have explained this one.
When our dog takes a crap on the lawn, and it isn't cleaned up promptly, within a week there's a dead spot with a perfect ring of extra healthy grass around it.
Too many 'nutrients' at ground zero kills the grass, but around the edges where it gets diluted the grass grows like crazy.
I'm still going with aliens pooping, though.
I worked at a large multinational that was slated to be acquired by a larger multinational.
Then, mid-way through the process came the "Oh no! India wants billions in 'back taxes' due to the sale!"
The solution was that rather than merging the two companies (triggering the giant tax bill), the Indian Development Center was kept as the last remnant of the old multinational and was now considered a "wholly owned subsidiary" of the buying multinational. Apparently the lack of a formal merger of just the portion of the company based out of India negated the tax bill somehow.
So
a) This is nothing more than the standard shakedown the government of India does whenever there's a merger of giants like this.
b) It can also be avoided by some rather facile legal trickery.
It strikes me as foolish both to make such huge claims of taxes owed when a merger like this occurs and to make those taxes so easy to avoid.
I have fond(?) memories of lying in bed, popping pain-killers and playing Road Rash while recovering from a nasty motorcycle accident.
As long as it stays true to it's 16 bit, cartoon violence core, I'm all for it.
This is exactly how I'm preparing my Turkey this year.
Home-made sous vide machine (large crock pot hooked up to a PID precision temp controller)
Except duck fat instead of bacon and canola instead of peanut oil (daughter has a peanut allergy)
I adopted scrum in my org, but only in response to a product management org that refuse to do their job. We got features masquerading as requirements, we got endless tactical "the customer wants x" requests all while upper management basically was accusing the team of being lazy for not giving them everything they wanted (and more) right away.
So we adopted agile. This let upper mgmt see we were working as hard as we could and it forced PM to decide "what do you want next? What's the minimum viable set of features? Is this more important than that?"
Yes agile isn't a cure all, but it definitely helps dev remain productive in the face of laziness and stupidity elsewhere in the org.
I've also seen a ton of fake agile (we call it "Fragile") where people adopt the buzzwords of agile without considering that good agile takes a lot of work. Fragile is adopting all the bad parts of agile without any understanding of the discipline involved to do it right (track technical debt, and pay it off as you go. Sprints are no excuse to not do long-term planning / grooming of the backlog. Daily stand-ups, where you track impediments are crucial. etc,)
Success with agile only comes if you understand when it's useful (where there's a large amount of uncertainty/stupidity, somewhere in the org)
It helps mask underlying problems (the uncertainty) while still maintaining productivity. But I wouldn't fly in a plane that was designed with agile principles. Uncertainty in a "mission critical" engineering problem kills people.
Wither goes local government, wither goes the federal government.
Barring intervention from the supreme court.
Given the feckless state of our current federal legislature, this is why it's important to elect the right person to the presidency: They will pick the next batch to decide this sort of thing.
People who like in glass houses shouldn't throw stones.
http://www.youtube.com/watch?feature=player_embedded&v=SGxKhUuZ0Rc
Some repeated behaviors are a bell-weather of behaviors to come.
Torturing small animals seems to be a common gateway behavior for serial killers.
Bullying and/or narcissistic behavior is a common thread among criminals.
In this case severe trolling is an indicator of... what?
I'm guessing something in the sales department, politics or mass-media news show.
Sorry. "Opinion" show.
The concept isn't that the thorium somehow gives off extra heat, it's that thorium is especially good at storing heat energy.
The laser is used to pump heat into the thorium quickly. The hot thorium is then put into contact with water to generate steam, but in the process the thorium is gradually cooled.
There's no magic, radioactive process going on here folks, just a material with a really high specific heat capacity. http://en.wikipedia.org/wiki/Heat_capacity
I will add however that this seems like complete snake oil.
The concept isn't that the thorium somehow gives off extra heat, it's that thorium is especially good at storing heat energy.
The laser is used to pump heat into the thorium quickly. The hot thorium is then put into contact with water to generate steam, but in the process the thorium is gradually cooled.
There's no magic, radioactive process going on here folks, just a material with a really high specific heat capacity. http://en.wikipedia.org/wiki/Heat_capacity
... If you have exceedingly long dress code standard (and because it is so long it allows for quite a lot of leeway in terms of what you actually can wear) then what you wear to work effectively becomes a uniform.
Uniforms purchased for work are tax deductible.
Just sayin'
You'll also note that every URL on one of these mails is a redirect that has the ability to track which user and which email it originated from.
They then use this info to generate click-through reports on what type of user did what with which email.
I'll add this is very old news.
Mankind's been using animals to provide warnings, attack and/or restrain intruders and root out evil for quite some time.
Don't lie about what you know. I.e. it's better to say "I don't know but I can find out." rather that pulling something out of your ass.
Don't complain about anything unless you can also offer a solution to the problem.
Do good work. Figure out what the company considers "good." I.e. some companies value speed of development, others value high-quality.
Never, ever take offense when someone points out a bug in your code. If there's a 'real' bug thank the person who found it, after all they are improving on your work. If it's a not a real bug work with them to figure out why they were mistaken (bad documentation? Not trained enough on what it's supposed to do?)
Social skills help. But don't be a phony.
Manage up. If you think you deserve something from your boss, and they won't give it to you, work out a plan to get it. (If you want a promotion, work out with your boss what he needs to see before he can promote you. Work out a plan with you boss to meet those goals.)
Hopefully you get the idea. Basically you should always try to improve the situation for everyone, not just yourself.
Until you reach middle-management. And then the knives come out and it's best to be a complete sociopath.
"Power concedes nothing without demand" - Frederick Douglass
If he's going use the "ignorance" tactic, I highly recommend that the OP remove this post. I moderate on a motorcycle forum, and we're constantly reminding folks that bragging in 'public' about how they plan on cheating their way out of a ticket / accident report / insurance claim isn't terribly bright. Especially considering there are folks on the forum who frown on that sort of behavior and are more than willing to rat them out. Myself included.
...how exactly did he know his neighbor had a wireless router running, unless he used some sort of wireless device (all of which produce their own EM emissions) to specifically detect the EM emissions coming from his neighbor? And no, divining rods don't count, regardless of what Iraqi bomb squads are doing.
Dollars to donuts says they only thought they were mashing the brakes down. In panic situations I've seen many people "lock up" or target fixate and continue to do exactly what they were doing that got them into the bad situation they were in. So small throttle sticking leads to mild panic which leads to more throttle and more panic and... Lather, rinse, repeat until accident and/or lawsuit.
Should I write to my congressman and demand a law for the "right to repair" coffee makers?
Since you ask... Yes, you should.
(my ex was in HR, and basically, US law forbids your old job from saying anything negative to your new employer)
Nonsense. There's nothing to worry about in US law about honestly giving a bad assessment. Now, the person being slagged lawyers' on the other hand...
Mind you, overly litigious ex-employees aside, there are plenty of ways around this.
The phrases "I consider him to be someone I have worked with." , "I found he occasionally did his job." or "I found he could be counted on for a truthful answer sometimes." can work magic.
Collecting a paycheck to support a losing project is sign you have a wife and two kids to support
There, I fixed it for you.
Working on a doomed project while speaking out and trying to fix it is a sign of an engineer who is a good candidate for promotion. They aren't just focused on their narrow portion and care about the project as a whole.
Generally, seeing engineers quit in the middle of a cluster-fuck project is a ding against their manager. It's up to their manager to make sure the engineers have input into the project, and can actual have their voices heard. Even if the project is a minor failure, people don't mind as much if they feel they have some stake in it. It's also a sign the project can be turned around in a later release if people at least have a voice in how to fix the processes that led to failure in the first place.
Sure some engineers are malcontents who can never be made happy, but these are pretty easy to spot in an interview. They'll talk about how the project sucked, but won't have much to say about how they'd make it better.
And even within clusterfuck projects, there can be small successes. I'm sure there are some lovely components buried deep inside Vista
So a smart interviewer is going to ask questions about your involvement in the clusterfuck.
And if the interviewer doesn't. Try answering the question without being asked. Or talk about how great your subcomponent was. And if the interviewer doesn't like that. Well, do you really want to work for/with a dumb-ass?
It also depends on experience. A smart, junior engineer shouldn't be blamed at all of a project failure. A senior engineer / manager should be asked some tough questions about their involvement.
Then there's the whole "companies with a stench of failure all over everything." Basically, I look for people with short tenures at these sorts of places. I don't want to see a 10 year veteran VP candidate from any company with reputations for "climb to the top of the meatpile" back-stabbers. Or an engineer from a place with a reputation for being insular and producing sub-par code.
Finally, the question you have to ask yourself is "Is this project really a failure?"
15 years ago I left a software company after a 3 year 'Bataan Death March'-style release of what I thought was a very disappointing, bloated, and technologically lagging project.
This product enjoys around a 65% Market share and probably a billion in sales annually.
Whenever I have a problem with Linux, I just go to a Linux fanboy site and post "Linux SUXXORS. I can't get 'x' to work. I'm going back to windows"
Someone always seems to helpfully step up and try and prove me wrong. I mean, answer my question.
Plus I get to learn new synonyms for 'idiot'.
I'm honestly surprised corporations aren't simply going into countries with cheap labor and building their own "company towns" where they can bring workers for all over the world.
Back in the day plenty of companies would just build towns out of nothing, in the middle of nowhere, and move people in to work at their factory / mine / chip fab plant.
So in this day of cheap airfare and 'free' telecommunications, why haven't we seen the same idea Globalized?
Or maybe we are...