These data are about low-altitude wind and surface ocean currents. Models based on those things are part of the toolkit being used as a matter of course in such searches, but unless MH370 spent months floating at the surface of the ocean, these models can't find it per se, though they can offer indirect hints.
Models of surface wind and currents were used to both predict, and trace back the possible origins of flotsam and debris from the crash that washed ashore[0][1] around the rim of the Indian Ocean in the following months and years.
As a side note, the Friendly Floatees event occurred in the Pacific, with drift around the Pacific, Arctic, and far north Atlantic oceans. MH370 was lost over the Indian Ocean.
[1] Part of my sources include personal knowledge, as I lived in Canberra and knew employees at the Australian Transport Safety Bureau during the early months of the search.
> On the one hand it looks like relying on behaviour that is correct now but may not be so in the future.
> Use a decent IDE that looks out for it if you need reminding about this class of bug.
And when your next environment/plugin/employer's setup changes or doesn't offer this warning? Or the day that getting your critical system back up ASAP leaves you no choice but to SSH in from your phone and edit your source in Nano?
Learning and practicing defensive programming as a professional programmer is like defensive driving for a taxi driver, or survival skills for a long-distance hiker. It's a part of what someone who considers themselves a serious professional should maintain.
Relying on a 'decent IDE' to manage your code quality for you is an excellent way to blunt your skills. I'm not saying we should all throw IDEs away or turn off their warnings, but to rely on them is an awful substitute for maintaining good practice. Granted, crossing every t and dotting every i is much, much harder in C than most other languages, but every compiler warning you have to hunt down and fix is another little slice of your day shaved off and gone.
Quoted above[0], "Inclination of 11.669 degrees" (from the preprint) would indicate it has greater inclination than the 8 planets, but less than some other small distant bodies[1].
Phonebooks are in alphabetical order. They are sorted into residential and business (white and yellow), then further sorted into business categories (or in some cases residential areas), and then ordered.
I disagree. I have preferred one implementation over another because it's funnier. Plus, focusing on the jokes rather than software was more or less a necessity in a fairly high-pressure startup situation.
I don't think there's much of a difference. If software devs were focused on entertainment value of their output rather than some other nonsensical metric, it might be a much better thing.
IANAL either but I agree, that is a statement of copyright which is not unusual, but there is no licence and therefore we have no right to copy & use it.
> If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking).
We are granted a license to use it on GitHub by the GitHub ToS.
This is fair, but I don't know how much the National Library of Australia has, or whether access is free. Sorry I forgot to mention my location in my previous comment.
