3 Matching Annotations
  1. Mar 2024
    1. "The sightings always recede to the edge of what technology allows you to do," Shostak told Space.com in 2019. "The aliens are kind of keeping pace with technology."

      This is a bad bit of reasoning. That "edge of what technology allows you to do" is a horizon beyond which we have no depth perception. Anything beyond that horizon seems equally impossible. To put it more plainly:

      Group A is 1,000 years more advanced than Group C. Group B is 100 years more advanced than Group C.

      At a single glance by Group C, both A and B seem equally impossible, because everything that exists beyond the horizon of their own technological abilities just seems like magic.

      So the fact that UAP always seem just beyond the horizon of our technological abilities isn't due to the fact that UAP are constantly adapting to be just one imagined step ahead of our current abilities. It's due to Asimov's law that any sufficiently advanced technology is indistinguishable from magic. And all magic, by its very nature, seems equally magical.

    1. A spike in UFO sightings in the 1950s and 60s was caused by tests of advanced US spy planes and space technology, a Pentagon report has concluded. Officials also said there was "no evidence" that the US government had encountered alien life. Most sightings of UFOs were ordinary objects from Earth, according to the report submitted to Congress on Friday.

      There's nothing in these three comments that well-informed members of the UAP research community would necessarily disagree with.

      Certainly experimental US technology did contribute to the increase in reported sightings of UAP.

      The claim that some UAP sightings are of scientifically unexplained phenomenon does not imply that the cause is alien life, or that any government has encountered aline life.

      No one would deny that the vast majority of UAP sightings are of mundane, or at least scientifically-explicable objects or phenomena.

  2. Mar 2018
    1. Florida.voteCount and Florida.countVotes()

      There's no problem here. Florida.voteCount will actually count votes only if it needs to (say, the first time). Then, it won't count the votes again and again: it would be a flaw in the design of the class.

      On the other hand, it is this class' responsability to decide what to do when somebody needs to know the count.

      If you have Florida.voteCount and Florida.countVotes(), it means it is caller's responsability to decide when and if it must execute the actual counting or just read an already computed count.

      This logic must be inside the class, not outside. Hence I advocate for Florida.voteCount as a getter which may do the actual counting (likely only once if the status of the state (!) hasn't changed) or give the already computed count.

      A different approach would look wrong to me. (When the language hasn't the kind of syntactical sugar Eiffel has, you likely will have Florida.getVoteCount() which replace both Florida.voteCount and Florida.countVotes().