e - b o y / e - g i r l

If you were taught code you more or less know how to do it. If i was taught to read a clock i more or less would know how to do it. Both subjects at zero knowledge both equate the same outcome

It's not that simple though. Code gets pretty complex, think of it this way. You're taught sums, substraction, multiplication and division on elementary school. Does that means you're capable of doing integral equations, vector calculus and physics by 7th grade? This is what I'm trying to imply. Clock reading never goes beyond it's inner and starting complexity, even if you add seconds counting into it. Coding though, even if you're taught the basics, does not means you'll be able to solve anything past X difficulty. There's a reason why there's professional developers and not professional watch readers

If you don't believe what I'm saying, check a rundown of 3 hours of basic programming, then basic math equations, then, try to solve any challenge from Project Euler without looking up the answers. Clock reading will take you at most, 30 minutes to understand, solving a Project Euler question would require you a few years of logical training.

Smh you over complicate things XD ok you are taught how to read a clock you still gotta figure out the time you cant just tell it by looking (as fast as you would reading it digital). Coding you know how it works you cant do it without having whatever it is you said you need. Happy? Same concept applies

I gave ya the basic rundown of how clocks work in your wall, it doesn't takes more than 3 seconds to guess the hour by looking at a watch. At my workplace, it usually takes me an hour to understand what previous developers were trying to achieve on X functions that I get tasked with solving, of course, depends on complexity. Sometimes it just takes me 1 minute, others, a full day