Skip to main content

CTW - Black Hole Ripples

First, some background.  Wednesday is "Conspiracy Theory Wednesday" around my house.  We pick a conspiracy theory and research it.  If there's documentaries, we watch it.  If there's articles online, we dig them up.  The idea of CTW is simple.  Treat the conspiracy theory as though it were fact for one day.  Try to find every way to make it fit reality.  By doing this we can get a better understanding of the angles people will try to defend it from, and then it also makes it easier to debunk the conspiracies on any other day.

So I'm going to try to start putting up my Wednesday posts as CTW posts.  It's representative of something I do 1 day every week, that's 52 days a year.  So it's a big part of who I am.  It's not exactly programming related, but it's a little bit of fun and a decent break.

Today's conspiracy is Black Hole Ripples.

Calling it a "conspiracy" isn't exactly accurate given that the link I just posted is from NASA.  But they aren't 100% proven and no one has really looked into the consequences of what they mean.

Black Hole Ripples are the energy waves that emit from a black hole as it absorbs other objects.  They are like ripples in an pond when a rock is dropped in, except there's no matter in space to ripple.  The Black Holes are creating ripples in space and time.

Deja Vu and Seeing the Future

Since space and time are physically being shifted in a ripple style pattern, we can examine lots of other possibilities.  If you consider these ripples to be like the crest and trough of an ocean wave, then you might consider that we are constantly shifting in space and time on an elliptical pattern as these waves pass over the earth.

Without looking into the "space" part of that equation, we have to note that this means that we're shifting back and forth in time.  If these waves can cross-section the earth at different angles and from different directions, then it's likely that occasionally we'll see entire groups of people having similar time shifts at the same moment.  In practice, however, we generally see individuals, not groups, who experience any sense of time having changed.  If this is the case, we must also include the possibility that some human beings are more sensitive to time than others.

Time is already affected by gravity, as we've discovered by leaving the planet.  Our clocks in our satellites are slightly faster than those on the ground.  So exploring time shifts as a result of something as massive in terms of gravity as a black hole should not seem strange.

Rogue Waves

In oceanography, a rogue wave is just a matter of waves crossing.  Basically, a wave with a long trough may overlap a wave with a short trough, and then their troughs and crests combine and make the occasional larger wave.  If enough cross just right, you might get one really massive wave.

The question is, what might happen if this were to occur in space-time?  that massive of a shift in space could do odd things to the earth itself, but what about in time?

In any case, that's CTW.  Do your research and enjoy.


  1. originally I was the one that gave this theory out. It intrigued me to no end that they say the black holes ripple out waves however will also state they have no effect. Also some people experience such déjà vu I've even seen them tell me what's going to happen and it does.

    So why not if they say a black hole can effect time why not the persons perception as well.

    This is not to say " time travel" or esp...its just somethe ripple easier then others. As to what or when and why is up for debate in our group however this theory has a lot of potential for backing as well as skeptics.

    Either way its a good solid CTW case.


Post a Comment

Popular posts from this blog

Teams and Complexity

Let's pretend you're a car mechanic (I don't know, maybe you are).  But you don't work at some shop in town, you work at a bigtime auto-maker onsite at the factory.  You help build cars from scratch.  You work with a lot of other car mechanics, and various engineers of different levels.  If we were looking at the 1910s, you might be working for Henry Ford on one of the first ever assembly lines.  Either way, you have a specific part of the car you're responsible for.  Your skills probably extend beyond that, and you might work on a different part of the car each day as your manager moves you around to keep the factory efficient.

One of your coworkers, Bob, is a superb engineer.  He is very good at building cars, far better than you, and he does it faster than everyone else.  Your boss really likes him.  You often get stuck after him in the assembly line, so you know exactly what sorts of things he does.  He's not sloppy, but he likes to do things his way.  He w…

Managing Programmers

Working with other programmers is tricky.  That said, it's nothing compared to the job of managing programmers.  One of my favorite quotes about Perl is that (paraphrased) "a Perl developer is like a rockstar.  Now imaging having a bunch of rockstars in one room together and you will understand why you don't want an entire team of Perl developers."  It's not about Perl here though. What's important to understand is that any developer worth his salt is going to be like a rockstar.  And yes, there are a lot of professional developers out there who aren't worth their salt, but that's for another post another day.  Rockstar may not be the right term here, but think of it this way.  These guys are smart.  They may not be geniuses, but there's going to be things that they know that you don't and probably never will.

I've seen it more than once and it's not going to make some Product Managers happy, but I'm going to state a fact, an eleph…

How to identify a skilled programmer during an interview

How does one identify a skilled programmer?  No company that has interviewed me could tell the difference between myself and other programmers they'd interview.  The interview process is truly a game of luck in this industry--on both sides.  Both the programmer and the company are basing their actions entirely on luck.

Companies have come up with numerous methods to attempt to discern a good programmer from a bad one.  The best tricks they have include a series of math problems, algorithms, problem solving technique tests, and even obscure programming questions, some without definitive answers.  As an example: Is there an authoritative source of information on the core principles that define object oriented programming?  I've heard everywhere from 3 to 7.  In a field of research about a synthetic concept, an authoritative answer is almost impossible to obtain.

Programmers were then forced to study to the interview.  Careercup is one of my favorite sites for this.  This almost …