Well I got that one wrong for sure.

Yeah I misunderstood the requirements.

You read too much into it. When it says "input constraints" it doesn't mean you need to verify the inputs fall into that range. It means that all test case inputs to the function you create will fall into those ranges.

I don't need to verify that h hours will be greater than or equal to 0 and less than or equal to 23 when the contraints tell me the input will be 0 <= h <= 23.

This is also incorrect. Needs to take constraints into account.

You need a calculator to do 3600/100_000?

Yeah, you definitely should only submit the best possible code in 8 kyu katas, or else all your future employers will see them and find out how bad of a programmer you are.

In any respectable company you will get bashed for implementing a magic number that wasn't calculated inside of the code. Every person working on the project will have to spend additional time to understand & remember what this value corresponds to.

I don't agree. It's not best practice (despite the votes), but it's certainly not 'very bad' either. It's arguable if it's even 'bad', really, in this case.

Very bad practice, don't do this if you want a job in coding, lol.

this is fire this is extrodinary it took me a while

One of the baddest practice

From someone that is going in to coding from the fine art world, that is beautiful.

ditto

Unreal!

Cool