Forgot your password?

Comment: Re:i wonder.. (Score 1) 530

by skirmish666 (#45213507) Attached to: First Experimental Evidence That Time Is an Emergent Quantum Phenomenon
The velocity of A _relative_ to B is velocityA+velocityB. There's no rule in physics that says two photons travelling to a common point from opposite directions are slowed down relative to each other.
If I can see two lights located one light second away from me in opposing directions and they're both turned on simultaneously the photons that reach me will both arrive at the same time, one second after they're turned on. They're moving at light speed relative to the medium they're travelling through, not each other.

Paul Otellini: Intel Lost the iPhone Battle, But It Could Win the Mobile War 117

Posted by Unknown Lamer
from the learning-from-mistakes dept.
kenekaplan writes "In an interview with The Atlantic before stepping down as CEO of Intel, Paul Otellini reflects on his decision not to make a chip for the then yet released iPhone. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'"

$1 Billion Mission To Reach the Earth's Mantle 267

Posted by timothy
from the because-it's-the-closest-one dept.
black6host writes "Humans have reached the moon and are planning to return samples from Mars, but when it comes to exploring the land deep beneath our feet, we have only scratched the surface of our planet. This may be about to change with a $1 billion mission to drill 6 km (3.7 miles) beneath the seafloor to reach the Earth's mantle — a 3000 km-thick layer of slowly deforming rock between the crust and the core which makes up the majority of our planet — and bring back the first ever fresh samples."

Ask Slashdot: How Best To Teach Programming To Salespeople? 211

Posted by samzenpus
from the know-your-product dept.
First time accepted submitter greglaw writes "Our company makes development tools, meaning that all our customers are programmers. If you'll forgive the sweeping generalization, on the whole good programmers don't make good salespeople and vice versa. However, it's important that our salespeople understand at some level the customers' problems and how exactly we can help. The goal is not to turn the salespeople into engineers, but just to have them properly understand e.g. what the customer means when he uses the term 'function call.' Most of our customers use C/C++. Does anyone have any recommendations for how best to go about this? Online courses or text books that give an introduction to programming in C/C++ would be great, but also any more general advice on this would be much appreciated."
Open Source

Richard Stallman Falls Ill At Conference 460

Posted by samzenpus
from the outcome-uncertain dept.
itwbennett writes "Stallman, 59, was speaking at the North Campus of the Polytechnic University of Cataluna when he started to feel ill and called for a doctor. It was originally reported in the Spanish press that Stallman was hypertensive, but it is not yet known what his eventual health status was, just that he left the building later under his own power." He is apparently okay and any significant confirmed updates will be posted here.

Ask Slashdot: How To Get Non-Developers To Send Meaningful Bug Reports? 360

Posted by Soulskill
from the it's-broken-just-fix-it dept.
DemonGenius writes "I'm in the midst of a major rollout of one of our primary internal applications at work and we have a beta version available for all the staff to use. The problem here is most of the staff don't know how to send reports meaningful enough to get us devs started on solving their problems without constant back and forth correspondence that wastes both developer time and theirs. Some common examples are: screenshots of the YSOD that don't include the page URL, scaled screenshots that are unreadable, the complaint that wants to be a bug report but is still just a complaint, etc. From the user's perspective, they just send an email, but that email registers in our tracking system. Any thoughts on how to get the non-devs sending us descriptive and/or meaningful reports? Does anyone here have an efficient and user-friendly bug tracking system/policy/standard at their workplace? How does it work?"

Good salesmen and good repairmen will never go hungry. -- R.E. Schenk