Hey mates,
this time just a short post about Center of Math’s problem of the week, which I think could be a sweet programming challenge.

The Exercise

I thought of a brute-forcing program, which calculates the different positions of the 3 hands and tests if they overlap. This challenge could be a bit difficult, but maybe some of you have fun trying it . I’m currently working the whole time on my Android RAT, so I can’t give you an example solution, but I think it shouldn’t take that long for the great members here to fill this hole ;).

Of course the solution isn’t that hard to find - just think about it -, but this challenge is a bit more math-oriented and reactivates your spirit . You can find the original post here.

I think that you have to consider the space between the marks in the clock. The key word is analog. As the second-hand advances, the minute-hand moves from one minute to the next one. As the minute-hand advances the hour-hand moves from one hour to the next one.

Therefore, 3:15:15 is not a solution to the problem. When the seconds-hand is at 15, the minutes-hands will be a quarter advanced with respect to the mark, and also the hour-handle that will be also one quarter off. Becase in three more quarters it has to be in 4.

As I said above, it’s not about finding the solution. I think 00:00:00 is very easy to see, when you just think about it, but this challenge is just for fun and not to help you finding the solution ;).

Nice challenge! As @oaktree said, it would be easier to do without code. Although it would be something good to practice if you can make a program off of information you receive from text.

I kind of got trapped by this, because I immediately thought of a program to solve the problem, without thinking how an analog clock actually works Though, there wouldn’t have been so much programming fun with just one solution. Anyway, thanks for the heads up!

Actually an analog clock works using gears that, in a sense, are imposing a minimum step on the clock hands. In a sense, it is digital deep inside . Not sure if mechanical analog clocks can go down to miliseconds, but I would say most of them don’t

Firstly, not only 00:00:00 is the correct solution. 12:00:00 works too ;).
Secondly, as @0x00pf said, an alog clock doesn’t care about milliseconds and in the original post from the Center of Math they just speak about hours, minutes and seconds, so these should be enough .